Scrum Gathering 2012 Shanghai_领导力与组织转型：scrum in china the hard way (oliver...

7 June 2012 Oliver Schreck, Qu Jie 1/10

Scrum in China - The Hard Way - Fast Pace Growing - Regulated Environment

Scrum Gathering 7th June 2012

Outline United Imaging Healthcare

Our Challenges

Our Scrum Process •  Product Backlog •  Sprint Planning •  Sprint •  Sprint Review •  Sprint Retrospective •  Scrum Roles

Conclusion

7 June 2012 Oliver Schreck, Qu Jie 2

Oliver Schreck Background •  Material Science, University Erlangen Job •  CTO SW, United Imaging •  Over 18 years software development, 5 in China •  SW-developer, project lead, department lead,

strategic business development Agile •  Agile practitioner since 2001 •  Agile Transition at Siemens Healthcare •  Scrum Coach •  Scrum the Hard Way (since 2011)


曲杰

学历 •  1999年毕业于西北工业大学通信工程专业

工作经历 •  13年软件开发与管理经验 •  中国医学装备协会IHE测试督察 •  上海联影医疗科技有限公司研发经理

敏捷开发经历 •  敏捷开发的实践者(2011年) •  联影敏捷开发的培训师


Business Model Eight Business Units, One Corporate research Center (3 R&D Centers)

MR BU CT BU MI BU XR BU

SW BU MH BU US BU RT BU

United Imaging Healthcare

BU CRC

Shanghai

UIH-SARI Advanced Medical

Equipment Technology

Research Centre

Shenzhen

UIH-SIAT Advanced Medical

Equipment R&D Centre

Beijing

Advanced Medical

Equipment R&D Centre

Business strategy

Goal of SW business unit

Provide a software framework to enable the development of

medical devices.


Regulations for Medical software development •  SFDA - GB/T 16260.1~4-2006, GB/T 25000.1-2010,GB/

T 25000.51-2010, YY/T 0664-2008 •  FDA - Food and Drug Administration – CFR 21 Part 11 &

Part 820 •  MDD - European Medical Device Directive 93/42/EEC •  ISO 13485:2003 + AC 2007 - Medical Devices - Quality

Management System •  IEC 62304 :2006 - Medical Device Software – Software

Life cycle Processes •  ISO 14971:2007 - Medical Devices - Application of risk

management to medical devices •  EN 60601-1-4 - Medical electrical equipment – Part 1-4:

General requirements for safety •  HE75:2009 - "Human Factors Engineering - Design of

Medical Devices”


Company growth Management focus •  100 employees à ~1000 interviews

… and still growing


0

20

40

60

80

100

120

Jan

11

Feb

11

Mär

11

Apr

11

Mai

11

Jun

11

Jul 1

1 A

ug 1

1 S

ep 1

1 O

kt 1

1 N

ov 1

1 D

ez 1

1 Ja

n 12

Fe

b 12

M

är 1

2 A

pr 1

2 M

ai 1

2

Software - BU

0

100

200

300

400

500

600

700

800

Jan

11

Feb

11

Mär

11

Apr

11

Mai

11

Jun

11

Jul 1

1 A

ug 1

1 S

ep 1

1 O

kt 1

1 N

ov 1

1 D

ez 1

1 Ja

n 12

Fe

b 12

M

är 1

2 A

pr 1

2 M

ai 1

2

United Imaging

People challenges

Many new graduates •  No or low experience •  Different backgrounds •  No Agile experience •  Some not even

programming

àTraining, training, … àMentor to guide

Few experienced developers •  Different backgrounds •  Mostly no medical

experience •  Waterfall addicted •  “Own” development

practices

àTraining, training, … àAgile coaching


Many challenges New 6 companies

–  At the same time

New products –  Medical regulated environment

New people –  Many, many every month

New tools –  Team Foundation Sever

New process –  Scrum


Build a plane in the air …

7 June 2012 Oliver Schreck, Qu Jie 11 7 June 2012 Oliver Schreck, Qu Jie 11

… in 2 years

Our approach


Scrum for medical devices?


Requirement Specification

System Functional Specifications

Functional Specifications (subsystem)

Design Specification Unit Tests

SubsystemIntegration Test

SystemIntegration Test

System Test

Time line

Decomposition and Definition In

tegr

ation

and

Rec

ompo

sition

System Validation

System Verification

Subsystem Verification

Unit Test Plan

SW - Development

Backlogs






System Test

Time line


tegr

ation

and

Rec

ompo

sition

Dev. + IT

SIT

Product Backlog Release Plan

Sprint Backlog

Requirements / Feedback from

customer

Sprint






System Test

Time line


tegr

ation

and

Rec

ompo

sition

Dev. + IT

SIT


Sprint BacklogProduct Delivery


customer

Continuous Feedback






System Test

Time line


tegr

ation

and

Rec

ompo

sition

Dev. + IT Dev. + IT

System Integration Test




customer

W-model






System Test

Time line


tegr

ation

and

Rec

ompo

sition

Dev. + IT Dev. + IT Dev. + IT Dev. + IT Dev. + IT

System Integration Test




customer

The Product Backlog


Product Backlog Learning how the product should look like 6 BU’s starting at “nearly” the same time •  FIFO

Unclear requirements •  Alignment of requirements •  Cross BU Clinical group

Always changing requirements •  Cross BU Architecture team

Low medical experienced member at BU’s •  Engage Medical doctors


The Sprint Backlog


Sprint Backlog

Teams too ambitious à Trace velocity of

team

Timeline pressure à No solution

Quality problems à see next slides


The Sprint


Sprint Fail fast •  2 week sprints •  One main branch

–  Interface branches –  Release branches

Continuous integration •  Gated builds, on checkin

–  Code review –  Automatic unit test –  Done criteria

•  Every hour complete package builds –  Automatic integration test

•  Automatic release packaging •  Integration machines


“Zero” – bug policy

24

August 2011 – May 2012

Limit max. number of open bugs à Highest priority is fixing bugs

Daily review of bugs by change board

à Fast feedback towards development Wish bugs will create new requirements

à Prioritize wishes together with features at Sprint Planning

Oliver Schreck, Qu Jie 7 June 2012

Ensuring quality Failed package builds •  Defined interface change process •  “Pull the line” – fix asap.

Unstable main line •  Pre-Integration test •  Integration machines •  Automated regression tests

Process definition under development •  Root cause analysis •  Inspect and adapt


The Product Increment


Sprint Review


Reality check •  Internal Review •  BU’s review

Continuous feedback from BU’s •  Slow feedback from BU’s

à Set up cross BU Test Board

Sprint Retrospectives


Inspect & adapt •  Root cause analysis

–  Involve all members –  Identify actions – Assign responsible – Check during next

Sprint

Scrum Roles – Product Owner

Product Owner •  Multiple Teams one

Product Owner Responsibilities •  Cross BU

coordination •  Product board •  Release plan


Product Owner A

Product Owner B

Product Owner A

Product Manager

Scrum Roles – Scrum Master

Scrum •  Organizes daily scrum •  Shield the team

– Refuse late requirements Scrum-But •  Coordinates the team •  Act as a “Team leader” •  Un-experienced with Scrum


Scrum Roles – Scrum Team Developer •  Implementation •  Code review •  Unit Test

Tester •  Daily feature test •  Regression test

Architect •  Ensure code quality

by reviews •  Review of concepts •  Coordination across

Scrum Teams •  Coordination across

BU’s 7 June 2012 Oliver Schreck, Qu Jie 31

How to coordinate all this?

Scrum of Scrums •  Cross Scrum Integration •  One Release Plan •  One Sprint Interval •  One Sprint Planning •  One Sprint Review •  One Project Lead


Project Leader

Conclusion


New 6 companies, new products •  We have a running “product” now •  Released internally every 2 weeks to 6 BU’s New people •  Many new ideas •  Many challenges

New tools •  One company, one tool (Team Foundation Sever) •  One database for all data (requirements, code, test, documents) •  Easy knowledge sharing

New process - Scrum •  Fast learning curve for team member •  Fast feedback between teams and BU’s •  Encourage to speak out problems •  Gives chances to prove himself •  Fast integration •  Fast feedback •  Stabilize Code

Still building…

7 June 2012 Oliver Schreck, Qu Jie 34 7 June 2012 Oliver Schreck, Qu Jie 34


If (unclear == true) then ask_us();

Thank you! by

Oliver Schreck & QU Jie

7 June 2012 Oliver Schreck, Qu Jie 36/10

Thank you by

[email protected] [email protected]

Scrum Gathering 2012 Shanghai_领导力与组织转型：scrum in china the hard way (oliver...

Technology

Transcript of Scrum Gathering 2012 Shanghai_领导力与组织转型：scrum in china the hard way (oliver...