Upload
gabriella-lynch
View
217
Download
0
Tags:
Embed Size (px)
Citation preview
should I Link, or should I sync?OSLC Webinar June-19, 2013 @ 11 am (ET)
Open Services for lifecycle integartion (OSLC) provides a lightweight, tool agnostic and vendor independent set of specifications enabling tools to live in an ecosystem.
But what integration strategy should I use? Is loosely coupled linked data enough? What if I synchronized, would it be impossible to maintain? What about dashboards and reports having so many data sources? Perhaps a single tool would do the trick anyhow?
Come and listen to Ericssons ”current best thinking” on the subject.
Mats BerglundEnterprise Architect20+ years experience in System and SW development tools for telecom R&D
Should I link or should I synch? | Mats Berglund | © Ericsson AB 2013 | 2013-06-18 | Page 2
Dev Team Leader
Cross-functional team:› System Architects› SW Designers› SW Testers› System Testers
Loves Scrum
Maint Team Leader
Cross-functional team:› System Architects› SW Designers› SW Testers› System Testers
Loves Kanban
IT Support
ALM tool supply responsible:› Agile planning tools› Lifecycle and reporting tools› SW design (IDE) tools› SCM, Build and Test tools
Hates poor tool integrations
Setting the scene
Project Manager
Product and Project responsible:› Requirements management› Portfolio planning› Roadmap and time plan› Progress and follow-up
Loves roll-up dashboards
PatrickIngrid
MariaDiana
Should I link or should I synch? | Mats Berglund | © Ericsson AB 2013 | 2013-06-18 | Page 3
Common ALM Tool(s)
Common Definitions of Artifacts
Common Mapping Tables
Common Methodology
Total Chaos Streamlined WoW Excel Managed diversity Sync Efficient flexibility Link Lifecycle Utopia Platform
Five scenes
Should I link or should I synch? | Mats Berglund | © Ericsson AB 2013 | 2013-06-18 | Page 4
Total Chaos
Maint Team
Too
l B
Data
<Ref>
<Title>
<WIP>
Task
<Ref>
<Title>
<Color>
Tests
Capabilities & Logic
5
Throughput
R
Y
Test states
UINative UI
3 6 4
G
Too
l C
Data
<#>
<Name>
<Impact>
Issue
Logic
Entered
Resolved
Ticket flow
UIWebUI
Investigate
Dev Team
Too
l A
Data
<ID>
<Slogan>
<Priority>
Work Item
<ID>
<Slogan>
<Result>
Test Case
<ID>
<Slogan>
<Severity>
Defect
Capabilities & Logic
WI #1
WI #2
WI #3
Backlog
WI #n
Passed
Failed
Received
Corrected
Test states Defect flow
User InterfaceWeb UIIDE UI
Should I link or should I synch? | Mats Berglund | © Ericsson AB 2013 | 2013-06-18 | Page 5
Total Chaos
Project & Product Manager
Too
l E
Data Warehouse
Done A
Done B
Done <n>
Work Done
Passed A
Tests Passed
Fixed A
Fixed B
Fixed <n>
Bugs Fixed
Capabilities & Logic
User InterfaceWebUI
AndroidUI
Too
l D
Data
<Record>
<Heading>
<Urgency>
Main Requirements
CapabilityWeighting
UINative
UI
Req X Req Y
Progress Release trainQuality
Passed BPassed <n>
IT Support
?Scrum Kanban
Passed GreenRequire
ment
Epic
Tick
et D
efe
ct
12
a
b
cx y z
q
Should I link or should I synch? | Mats Berglund | © Ericsson AB 2013 | 2013-06-18 | Page 6
Streamlined WoW
Project Manager
Too
l E
Data Warehouse
Done A
Done B
Done <n>
Work Done
Passed A
Tests Passed
Fixed A
Fixed B
Fixed <n>
Bugs Fixed
Capabilities & Logic
User InterfaceWebUI
AndroidUI
Progress Release trainQuality
Passed BPassed <n>
Dev Team
Too
l A
Data
<ID>
<Slogan>
<Priority>
Work Item
<ID>
<Slogan>
<Result>
Test Case
<ID>
<Slogan>
<Severity>
Defect
Capabilities & Logic
WI #1
WI #2
WI #3
Backlog
WI #n
Passed
Failed
Received
Corrected
Test states Defect flow
User InterfaceWeb UIIDE UI
Maint Team
Too
l B
Data
<Ref>
<Title>
<WIP>
Task
<Ref>
<Title>
<Color>
Tests
Capabilities & Logic
5
Throughput
R
Y
Test states
UINative UI
3 6 4
G
WI #1
WI #2
WI #3
WI #n
Backlog
excel
Should I link or should I synch? | Mats Berglund | © Ericsson AB 2013 | 2013-06-18 | Page 7
Maint Team
Too
l B
Data
<Ref>
<Title>
<WIP>
Task
<Ref>
<Title>
<Color>
Tests
Capabilities & Logic
5
Throughput
R
Y
Test states
UINative UI
3 6 4
G
Too
l C
Data
<#>
<Name>
<Impact>
Issue
Logic
Entered
Resolved
Ticket flow
UIWebUI
Investigate
Dev Team
Too
l A
Data
<ID>
<Slogan>
<Priority>
Work Item
<ID>
<Slogan>
<Result>
Test Case
<ID>
<Slogan>
<Severity>
Defect
Capabilities & Logic
WI #1
WI #2
WI #3
Backlog
WI #n
Passed
Failed
Received
Corrected
Test states Defect flow
User InterfaceWeb UIIDE UI
Mapping table
Passed
Failed R
Y
G
Mapping table
Received
Corrected
Entered
Investigate
Resolved
Sync tool
Managed Diversity
Should I link or should I synch? | Mats Berglund | © Ericsson AB 2013 | 2013-06-18 | Page 8
+ -Tool vendor agnostic Potential sync-tool-vendor look-in
Dashboards within favorite tool Potentially many mapping tables
Potential commonpoint for process enactment
and reporting
Risk for multiplying capabilities
Synch Pros & Cons
+ -Many adapters available OOTB Data duplication and synch risk
Adapters are kept up to date License fee
R
Y
G Passed
FailedWI #1
WI #2
Backlog
WI #n
WI #1
WI #2
Backlog
WI #n
Pro
ject
and
tea
m p
ersp
ectiv
eIT
sup
port
per
spec
tive
Should I link or should I synch? | Mats Berglund | © Ericsson AB 2013 | 2013-06-18 | Page 9
Proj Mgr
Too
l D
Data
<ID>
<Slogan>
<Priority>
Main Requirements
CapabilityWeighting
UINative UI
Req X Req Y
Data Warehouse
Done A
Done B
Done <n>
Work Done
Passed A
Tests Passed
Fixed A
Fixed B
Fixed <n>
Bugs Fixed
Capabilities & Logic
User InterfaceWebUI
AndroidUI
Progress Release trainQuality
Passed BPassed <n>
Dev Team
Too
l A
Data
<ID>
<Slogan>
<Priority>
Work Item
<ID>
<Slogan>
<Result>
Test Case
<ID>
<Slogan>
<Severity>
Defect
Capabilities & Logic
WI #1
WI #2
WI #3
Backlog
WI #n
Passed
Failed
Received
Corrected
Test states Defect flow
User InterfaceWeb UI
Maint Team
Too
l B
Data
ID>
<Slogan>
<Priority>
Task
<Ref>
<Title>
<Color>
Tests
Capabilities & LogicBacklog
R
Y
Test states
UINative UI
G
Too
l C
WI #1
WI #2
WI #3
WI #n
UI A UI B UI-delegate UI BUI DUI-delegate
Link Link
Efficient Flexibility
UI D
Should I link or should I synch? | Mats Berglund | © Ericsson AB 2013 | 2013-06-18 | Page 10
OSLC - Open Services For Lifecycle Collaboration
Should I link or should I synch? | Mats Berglund | © Ericsson AB 2013 | 2013-06-18 | Page 11
+ -Tool vendor agnostic Limited set of OSLC enabled tools
Open Standard Index reporting Light specification & data model
No data copy (single source) Link health (over time)
Rich-hoover and UI-delegate provides capabilities and logic from
linked tool within favorite tool
Context switch to user when exposed to different tool
capabilities and logic
Link Pros & Cons
+ -Standard URL (REST) technology Quality & timing of OSLC adapters
Easy to adapt internal tools (Lyo) Multiple tool licenses for all users
Pro
ject
and
tea
m p
ersp
ectiv
eIT
sup
port
per
spec
tive
Should I link or should I synch? | Mats Berglund | © Ericsson AB 2013 | 2013-06-18 | Page 12
Lifecycle Utopia
All roles
Th
e u
ltim
ate
To
ol
Data
Done A
Done B
Done <n>
Work Done
Passed A
Tests Passed
Fixed A
Fixed B
Fixed <n>
Bugs Fixed
Capabilities & Logic
User InterfaceWebUI
AndroidUI
<Record>
<Heading>
<Urgency>
Main Requirements
Weighting
Req X Req Y
Progress Release trainQuality
Passed BPassed <n>
IPhoneUI
IDEUI
NativeUI
<ID>
<Slogan>
<Priority>
Work Item
<ID>
<Slogan>
<Result>
Test Case
<ID>
<Slogan>
<Severity>
Defect
WI #1
WI #2
WI #3
Backlog
WI #n
Passed
Failed
Received
Corrected
Test states Defect flow
<Ref>
<Title>
<WIP>
Task
5
Throughput
3 6 4
Platform
Should I link or should I synch? | Mats Berglund | © Ericsson AB 2013 | 2013-06-18 | Page 13
Lifecycle Reality
Jenkins
Tuleap
EriCOLLTitanClear Case
Note: Not complete. A snapshot of tools used at Ericsson.
Should I link or should I synch? | Mats Berglund | © Ericsson AB 2013 | 2013-06-18 | Page 14
Q&A