should I Link, or should I sync? OSLC Webinar June-19, 11 am (ET)

Transcription

1 should I Link, or should I sync? OSLC Webinar June-19, 11 am (ET) Mats Berglund Enterprise Architect 20+ years experience in System and SW development tools for telecom R&D

2 Setting the scene Project Manager IT Support Product and Project responsible: ALM tool supply responsible: Requirements management Portfolio planning Roadmap and time plan Progress and follow-up Patrick Agile planning tools Lifecycle and reporting tools SW design (IDE) tools SCM, Build and Test tools Ingrid Loves roll-up dashboards Hates poor tool integrations Dev Team Leader Maint Team Leader Cross-functional team: System Architects SW Designers SW Testers System Testers Diana Cross-functional team: System Architects SW Designers SW Testers System Testers Maria Loves Scrum Loves Kanban Should I link or should I synch? Mats Berglund Ericsson AB Page 2

3 Common ALM Tool(s) Common Definitions of Artifacts Common Mapping Tables Common Methodology Five scenes Total Chaos Streamlined WoW Excel Managed diversity Sync Efficient flexibility Link Lifecycle Utopia Platform Should I link or should I synch? Mats Berglund Ericsson AB Page 3

4 Tool A Tool B Tool C Total Chaos Dev Team Maint Team User Interface IDE Web Native Web Logic Backlog WI #3 Test states Passed Failed Defect flow Received Corrected Throughput Test states R Y G Ticket flow Entered Investigate Resolved Work Item <Priority> Test Case <Result> Defect <Severity> Task <WIP> Tests <Color> Issue <#> <Name> <Impact> Should I link or should I synch? Mats Berglund Ericsson AB Page 4

5 Tool D Tool E Total Chaos Project & Product Manager IT Support User Interface Native Android Web Capability Weighting Req X Req Y Progress Quality Release train? Warehouse Main Requirements <Record> <Heading> <Urgency> Work Done Done A Done B Done <n> Tests Passed Passed A Passed B Passed <n> Bugs Fixed Fixed A Fixed B Fixed <n> Should I link or should I synch? Mats Berglund Ericsson AB Page 5

6 Tool E Tool A Tool B Streamlined WoW Project Manager Dev Team Maint Team User Interface User Interface Android Web IDE Web Native Progress Quality Release train excel Backlog WI #3 Test states Passed Failed Defect flow Received Corrected Throughput Backlog WI #3 Test states R Y G Warehouse Work Done Done A Done B Done <n> Tests Passed Passed A Passed B Passed <n> Bugs Fixed Fixed A Fixed B Fixed <n> Work Item <Priority> Test Case <Result> Defect <Severity> Task <WIP> Tests <Color> Should I link or should I synch? Mats Berglund Ericsson AB Page 6

7 Tool A Tool B Tool C Managed Diversity Dev Team Maint Team IDE User Interface Web Sync tool Native Web Backlog WI #3 Test states Passed Failed Defect flow Received Corrected Throughput Test states R Y G Logic Ticket flow Entered Investigate Resolved Work Item <Priority> Test Case <Result> Mapping table Defect Passed <Severity> Failed G Y R Mapping table Received Task <WIP> Corrected Entered Tests Investigate <Color> Resolved Issue <#> <Name> <Impact> Should I link or should I synch? Mats Berglund Ericsson AB Page 7

8 IT support perspective Project and team perspective Synch Pros & Cons + - Tool vendor agnostic Dashboards within favorite tool Potential common point for process enactment and reporting Potential sync-tool-vendor look-in Potentially many mapping tables Risk for multiplying capabilities Backlog Backlog R Y G Passed Failed + - Many adapters available OOTB duplication and synch risk Adapters are kept up to date License fee Should I link or should I synch? Mats Berglund Ericsson AB Page 8

9 Tool D Tool A Tool B Efficient Flexibility Proj Mgr Dev Team Maint Team User Interface User Interface Native D Android -delegate Web D Native A B -delegate B Capability Weighting Req X Req Y Capabilities & Logic Progress Quality Backlog WI #3 Release Test train states Passed Failed Defect flow Received Corrected Backlog WI #3 Test states R Y G Warehouse Main Requirements <Priority> Work Done Done A Done B Done <n> Tests Passed Work Item Passed A Passed B Passed <Priority> <n> Bugs Fixed Test Case Fixed A Fixed B Fixed <n> <Result> Defect <Severity> Task ID> <Priority> Tests <Color> Link Link Should I link or should I synch? Mats Berglund Ericsson AB Page 9

10 OSLC - Open Services For Lifecycle Collaboration Should I link or should I synch? Mats Berglund Ericsson AB Page 10

11 IT support perspective Project and team perspective Link Pros & Cons + - Tool vendor agnostic Open Standard Index reporting No data copy (single source) Rich-hoover and -delegate provides capabilities and logic from linked tool within favorite tool Limited set of OSLC enabled tools Light specification & data model Link health (over time) Context switch to user when exposed to different tool capabilities and logic + - Standard URL (REST) technology Quality & timing of OSLC adapters Easy to adapt internal tools (Lyo) Multiple tool licenses for all users Should I link or should I synch? Mats Berglund Ericsson AB Page 11

12 The ultimate Tool Lifecycle Utopia All roles User Interface Native IDE IPhone Android Web Throughput Backlog WI #3 Test states Passed Failed Defect flow Received Corrected Req X Weighting Req Y Progress Quality Release train Platform Task <WIP> Work Item <Priority> Test Case <Result> Defect <Severity> Main Requirements <Record> <Heading> <Urgency> Work Done Done A Done B Done <n> Tests Passed Passed A Passed B Passed <n> Bugs Fixed Fixed A Fixed B Fixed <n> Should I link or should I synch? Mats Berglund Ericsson AB Page 12

13 Lifecycle Reality Tuleap Jenkins EriCOLL Clear Case Titan Should I link or should I synch? Mats Berglund Ericsson AB Page 13 Note: Not complete. A snapshot of tools used at Ericsson.

14 Q&A Should I link or should I synch? Mats Berglund Ericsson AB Page 14

15