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 LeaderCross-functional team:› System Architects› SW Designers› SW Testers› System Testers

Loves Scrum

Maint Team LeaderCross-functional team:› System Architects› SW Designers› SW Testers› System Testers

Loves Kanban

IT SupportALM 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 sceneProject ManagerProduct 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 ChaosMaint Team

Tool

B

Data

<Ref><Title><WIP>

Task<Ref><Title><Color>

Tests

Capabilities & Logic

5

Throughput

R

Y

Test states

UINative UI

3 6 4

G

Tool

C

Data

<#><Name><Impact>

Issue

Logic

Entered

Resolved

Ticket flow

UIWebUI

Investigate

Dev Team

Tool

A

Data

<ID><Slogan><Priority>

Work Item<ID>

<Slogan><Result>

Test Case<ID>

<Slogan><Severity>

Defect

Capabilities & Logic

WI #1WI #2WI #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

Tool

E

Data Warehouse

Done ADone B

Done <n>

Work DonePassed A

Tests PassedFixed AFixed B

Fixed <n>

Bugs Fixed

Capabilities & Logic

User InterfaceWebUI

AndroidUI

Tool

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 GreenRequirem

ent Epic

Ticke

t D

efec

t

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

Tool

E

Data Warehouse

Done ADone B

Done <n>

Work DonePassed A

Tests PassedFixed AFixed B

Fixed <n>

Bugs Fixed

Capabilities & Logic

User InterfaceWebUI

AndroidUI

Progress Release trainQuality

Passed BPassed <n>

Dev Team

Tool

A

Data

<ID><Slogan><Priority>

Work Item<ID>

<Slogan><Result>

Test Case<ID>

<Slogan><Severity>

Defect

Capabilities & Logic

WI #1WI #2WI #3

Backlog

WI #n

Passed

Failed

Received

Corrected

Test states Defect flow

User InterfaceWeb UIIDE UI

Maint Team

Tool

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 #1WI #2WI #3WI #n

Backlog

excel

Should I link or should I synch? | Mats Berglund | © Ericsson AB 2013 | 2013-06-18 | Page 7

Maint Team

Tool

B

Data

<Ref><Title><WIP>

Task<Ref><Title><Color>

Tests

Capabilities & Logic

5

Throughput

R

Y

Test states

UINative UI

3 6 4

G

Tool

C

Data

<#><Name><Impact>

Issue

Logic

Entered

Resolved

Ticket flow

UIWebUI

Investigate

Dev Team

Tool

A

Data

<ID><Slogan><Priority>

Work Item<ID>

<Slogan><Result>

Test Case<ID>

<Slogan><Severity>

Defect

Capabilities & Logic

WI #1WI #2WI #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 tablesPotential common

point for process enactment and reporting

Risk for multiplying capabilities

Synch Pros & Cons

+ -Many adapters available OOTB Data duplication and synch riskAdapters are kept up to date License fee

R

Y

G Passed

FailedWI #1WI #2

Backlog

WI #n

WI #1WI #2

Backlog

WI #n

Pro

ject

and

team

per

spec

tive

IT s

uppo

rt pe

rspe

ctiv

e

Should I link or should I synch? | Mats Berglund | © Ericsson AB 2013 | 2013-06-18 | Page 9

Proj Mgr

Tool

D

Data

<ID><Slogan><Priority>

Main Requirements

CapabilityWeighting

UINative UI

Req X Req Y

Data Warehouse

Done ADone B

Done <n>

Work DonePassed A

Tests PassedFixed AFixed B

Fixed <n>

Bugs Fixed

Capabilities & Logic

User InterfaceWebUI

AndroidUI

Progress Release trainQuality

Passed BPassed <n>

Dev Team

Tool

A

Data

<ID><Slogan><Priority>

Work Item<ID>

<Slogan><Result>

Test Case<ID>

<Slogan><Severity>

Defect

Capabilities & Logic

WI #1WI #2WI #3

Backlog

WI #n

Passed

Failed

Received

Corrected

Test states Defect flow

User InterfaceWeb UI

Maint Team

Tool

B

Data

ID><Slogan><Priority>

Task<Ref><Title><Color>

Tests

Capabilities & LogicBacklog

R

Y

Test states

UINative UI

G

Tool

C

WI #1WI #2WI #3WI #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 adaptersEasy to adapt internal tools (Lyo) Multiple tool licenses for all users

Pro

ject

and

team

per

spec

tive

IT s

uppo

rt pe

rspe

ctiv

e

Should I link or should I synch? | Mats Berglund | © Ericsson AB 2013 | 2013-06-18 | Page 12

Lifecycle Utopia All roles

The

ultim

ate

Tool

Data

Done ADone B

Done <n>

Work DonePassed A

Tests PassedFixed AFixed 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 #1WI #2WI #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