I am going to share a case study of how we as coaches kick start a large scale agile transition and supported the product teams in the one year journey in the transition in FDA (Food & Drugs Administration) regulated organisation in healthcare industry. The product teams include members with software, electrical and mechanical background. I will share how the transition get started, what are the phases during the journey, what are the main problems we try to address and what we did to achieve significant success.
**Outlines**
- Why did the management seek external support after a successful product death march version release
- Phase 0 - Kick start
- How did we kick off the journey and facilitate the organisation structure change
- Phase 1 - Building real teams and Make very basics
- How to build self-managing team to enable cross-learning and close collaboration
- Phase 2 - Scaling Scrum and Real Teams
- What scaling ceremonies, practices, artifacts were adopted and what were the difference from single team implementation
- Involving stake holders
- Phase 3 - Get up to speed
- What infrastructure, tool and process change were adopt to support iterative and increment development
- What individual level agile practices adopted to enable frequent and stable release
- Phase 4 - Test Efficiency and Effectiveness
- What we did to address quality issue of life-critical product release
3. Fearless Journey
Surgery Team @ Healthcare Product Team
3
2.5 years
(0.5 year delay)
1 year
(1 week in advance)
1300+ bugs 0 bug
20 hours +
Build duration
2.8 seconds
Death march No Overtime
C-Arm X-Ray@Orthopedics operating room
CアームX線機@整形外科⼿術室
6. www.danielteng.com
1st Attempt (2013) - Fancy Words Agile
ファンシーワードアジャイル
6
Scrum Continuous Delivery
Specification by Example
User Story Applied
Test Driven Development
Exploratory Testing
Refactoring
Behaviour Driven Development
Design Thinking
7. 1st Attempt - Component Team based Scrum
1 回⽬の試⾏ - コンポーネント チーム ベースのスクラム
7
9. 2nd Attempts (January 2015)
Q1: Lift Off - Back to Basics
● Real feature teams
● Self-managing teams
● Facilitated Scrum activities
● User story
● Product backlog
10. www.danielteng.com
Change from Inside
10
● Process
● Scrum frameworks
● Process tools
● Structure
● Team, departments
● Report hierarchy
● Cycles of releases, sprints,
performance reviews
● Culture
● Collaborative
● Embracing failure
● Encourage cross learning
11. www.danielteng.com
Coming of Age Day 成⼈式
11
● Form teams with end to
end responsibilities
● Delegate responsibilities
of team design
● チーム設計の責任をチーム
に委譲する
● Set up team alignment
● チーム契約を設定する
● Send out signals of
change
● 変化のシグナルを送る
13. Criteria of Team Design
チーム編成の基準
● Team of 6-8
● Cross functional team
● Experience,
Knowledge and Skill
● 経験、知識とスキルセット
● Gender
● 性別
● Personality
● 個性
● Live in Suburb
● 郊外に住んている
● …
20. After Team Design Session
チームセルフデザインワークショップ後
20
MCB Control
Virtual Team
Image Proc.
Virtual Team
WKS App.
Virtual Team
Verification
Virtual Team
21. Single Product Backlog
シングル プロダクト バックログ
● Business Flexibility
● ビジネスの柔軟性
● End to end user story
● エンド ツー エンドの
ユーザー ストーリー
● Less bottleneck
● ボトルネックが少ない
Step on pedal, take a shot, and see the bones
ペダルを踏んで、ショットを撮って、⻣を⾒てください
22. Single Product Owner
シングル プロダクト オーナー
● Focuses on big picture
● 製品の全体像に焦点を当て
ています
● Focuses on business
● ビジネスにフォーカス
● Single Priority
● シングルプライオリティ
● Involve Stakeholders
● 利害関係者を巻き込む
27. 27
2nd Attempt - Journey
High Performance Teams
Scrum roles,
meetings,
artefacts
Lift Offs
Accelerating Agile Transition
Team self-
design
workshop
28. Q2: Up to Speed
● One stream development
● 10 mins build
● Basic automation as safe
net
● 基本的な⾃動化セーフ ネット
● Build information radiator
● ビルド ラジエーター
● Integrate with EE&ME、IQ
● Electrical Engineering 電気⼯学
● Mechanical Engineering 機械⼯学
● Image Quality 画質
29. Continuous Deployment
継続的デプロイ
● One stream development
● ワンストリーム開発
● Refactoring Jenkins jobs
● Jenkins ジョブの再構築
● Build automation
● ⾃動ビルド
● 20+ hrs to 2.8 secs
30. Single Dev. Stream
Check in build
Build information Radar
10 Minutes Build
11 minutes CI with build, UT, create
deploy package, send report
To be a “Slacker”
Automatic Deployment
Automatic Smoking Test
Do Not Fear Failure, Just Make the Failure Fast!
38. www.danielteng.com
38
2nd Attempt - Journey
Up to Speed
10 mins build
Checkin build
One stream
Information radiator
Continuous deploy
Automated smoke test
Involve stakeholders
Accelerating Agile Transition
High Performance Teams
Scrum roles,
meetings,
artefacts
Lift Offs
Team self-
design
workshop
39. Q3: Mastery of Engineering Practices
Q3: エンジニアリング実践の習得
● Specification by
Example
● TDD / BDD
● Refactoring
40. www.danielteng.com
40
2nd Attempt - Journey
Accelerating Agile Transition
Engineering
Specification by
example
TDD
BDD
Up to Speed
10 mins build
Checkin build
One stream
Information radiator
Continuous deploy
Automated smoke test
Involve stakeholders
High Performance Teams
Scrum roles,
meetings,
artefacts
Lift Offs
Team self-
design
workshop
41. Q4: Test Efficiency & Effectiveness
Q4: テストの効率と有効性
● Session based testing
● セッションベースのテスト
● Test case workshop
● テスト ケースの設計ワーク
ショップ
● Risk based test case
design
● リスクベースのテスト設計
44. www.danielteng.com
44
2nd Attempt - Journey
Accelerating Agile Transition
Testing
Exploratory Test
Test case design
Risk based test
management
Engineering
Specification by
example
TDD
BDD
Up to Speed
10 mins build
Checkin build
One stream
Information radiator
Continuous deploy
Automated smoke test
Involve stakeholders
High Performance Teams
Scrum roles,
meetings,
artefacts
Lift Offs
Team self-
design
workshop
45. www.danielteng.com
Outcome - November 2015 (After 11 months)
結果 - 2015年11⽉(11ヶ⽉後)
Delivered Project on Time with Good Quality
⾼品質で納期通りにプロジェクトを提供
Schedule スケジュール
Quality 品質
Effort on Fix work vs. New work
0.5 years delay vs 1 week in advance
半年遅れ VS 1週間前に終了 150% VS 40%
47. www.danielteng.com
Next Step: Adopt GOOS
次のステップ - GOOS
Given an C-Arm X-Ray is On
When Doctor step on pedal
And he takes exposure
Then he will see bones on
the screen