scaling' agile implementing safe
TRANSCRIPT
![Page 1: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/1.jpg)
‘Scaling’ AgileImplementing SAFe
April 7, 2015 Tuesday 3:00-4:00 p.m. 50 Church St., 3rd Floor
![Page 2: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/2.jpg)
• Experience with Adopting Agile at HUIT • IAM and Agile: A History
• Why Scaled Agile Framework (SAFe)?
• SAFe Basics
• Implementing SAFe: IAM and Cloud & DevOps• Program Increment Planning
• Breaking Down Work: Business Objective to User Story Task
• Takeaways and Lessons Learned
Agenda
2
![Page 3: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/3.jpg)
A look back in time…
Step 1: Attend HUIT-sponsored Agile training• Learn the terminology and practice the basics
Step 2: Implement Agile for existing teams (adopted by IAM 11/12)
• Create cross-functional scrum teams
• Adopt scrum and iterative development cadence:
• Two-week sprints
• Daily standups
• Requirements in sprint-sized user stories, maintained in a backlog
IAM and Agile: A History
3
![Page 4: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/4.jpg)
We liked being Agile!
Our transition to Agile methodology got a positive reaction both inside and outside the program team:
• We worked faster
• We delivered completed work more frequently
• We were able to manage changing priorities effectively
IAM and Agile: A History
4
![Page 5: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/5.jpg)
IAM and Agile: A History
*
5
The Five Levels of PlanningAlways accurate, but at varying levels of precision.
Product VisionLong-term, 12+ months
Product Roadmap12-18 months, revised quarterly
Release Planning3-6 months, revised each sprint
Sprint PlanningEvery 2 weeks
Daily PlanningEvery day
![Page 6: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/6.jpg)
We liked being Agile … but ...
We struggled to effectively plan beyond one sprint at a time:
• Larger deliverables were difficult to decompose
• Delivery dates for major releases were hard to validate
• Cross-team delivery of new features was rare and frustrating
Something had to change.
IAM and Agile: A History
6
![Page 7: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/7.jpg)
IAM and Agile: A History
*
7
The Five Levels of PlanningAlways accurate, but at varying levels of precision.
Product VisionLong-term, 12+ months
Product Roadmap12-18 months, revised quarterly
Release Planning3-6 months, revised each sprint
Sprint PlanningEvery 2 weeks
Daily PlanningEvery day
![Page 8: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/8.jpg)
What Didn’t Work: Story Mapping
8
![Page 9: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/9.jpg)
At Last — the Program Plan!
9
![Page 10: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/10.jpg)
Product VisionLong-term, 12+ months
Product Roadmap12-18 months, revised quarterly
Release Planning3-6 months, revised each sprint
Sprint PlanningEvery 2 weeks
Daily PlanningEvery day
The Missing Piece
10
![Page 11: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/11.jpg)
What We Tried First: Release Planning
11
![Page 12: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/12.jpg)
What We Tried First: Release Planning
12
![Page 13: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/13.jpg)
What We Tried First: Release Planning
13
![Page 14: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/14.jpg)
Introducing Scaled Agile Framework (SAFe)
14
![Page 15: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/15.jpg)
A group of Agile teams (ART) brought together to deliver value• Team of 5-12 Agile teams (50-125 people total) planning,
committing, and executing together within a fixed period of time
ART teams work with a common backlog of features• One common backlog of program priorities and objectives• Common architectural and design principles
Agile Release Train Engineer coordinates work (hint: usually a PM)• “Scrum of Scrums”
• Continuous inter-team coordination and status reporting
All “cargo” goes on the train• Architecture, documentation, and supporting deliverables are the
responsibility of the ART
15
SAFe: Key Program-Level Concepts
![Page 16: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/16.jpg)
Scaled Agile gives us a framework for extending our process to ...
Larger-scope items in parallel work streams:• Provides a middle layer of scope items between story (very small)
and release (very large)• Requirements are described as minimally as possible
Over longer time increments:• A “program increment” cadence proceeds in parallel with sprint
cadence, enabling a quarterly long-view planning process
Across multiple delivery teams:• Program increments are defined for the team as a whole rather than
individual scrum teams
Why Scaled Agile?
16
![Page 17: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/17.jpg)
And we are still adhering to Agile principles!
Sprint practices and ceremonies are scaled:
• Backlog of scope items (features) is maintained and prioritized
• Team commits to delivering a set number of scope items in a time-boxed increment
• Team works collaboratively to deliver scope items throughout the increment
• At the end of the increment, we take time to reflect and adjust its process, enabling future success
Why Scaled Agile?
17
![Page 18: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/18.jpg)
The key SAFe practice used by IAM and Cloud & DevOps is centered around the program increment (PI):
• Six sprints in length, time-boxed
• Scope items are described as business objectives and features
• Commitments are made on a quarterly basis by the IAM team as a whole...
• ...at quarterly full-day off-site program increment planning meetings
IAM’s Implementation of SAFe
18
![Page 19: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/19.jpg)
IAM’s Implementation of SAFe
19
![Page 20: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/20.jpg)
IAM’s Implementation of SAFe
20
![Page 21: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/21.jpg)
Increment planning meetings are quarterly team activities that replicate sprint-level activities on a larger scale.
• Retro the prior increment
• Introduce the proposed scope of the new increment
• Team validates scope:
• Size high-level stories
• Schedule high-level stories into sprint-by-sprint plans
• Identify dependencies and risks that need follow-up work
• Make a commitment
IAM’s Implementation of SAFe
21
![Page 22: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/22.jpg)
IAM’s Implementation of SAFe
22
![Page 23: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/23.jpg)
IAM’s Implementation of SAFe
23
![Page 24: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/24.jpg)
IAM’s Implementation of SAFe
24
Product VisionLong-term, 12+ months
Product Roadmap12-18 months, revised quarterly
Release Planning3-6 months, revised each sprint
Sprint PlanningEvery 2 weeks
Daily PlanningEvery day
![Page 25: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/25.jpg)
IAM’s Implementation of SAFe
25
Product VisionLong-term, 12+ months
![Page 26: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/26.jpg)
IAM’s Implementation of SAFe
26
Product Roadmap12-18 months, revised quarterly
![Page 27: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/27.jpg)
IAM’s Implementation of SAFe
27
Release Planning3-6 months, revised each sprint
![Page 28: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/28.jpg)
IAM’s Implementation of SAFe
28
Sprint PlanningEvery 2 weeks
![Page 29: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/29.jpg)
IAM’s Implementation of SAFe
29
Daily PlanningEvery day
![Page 30: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/30.jpg)
IAM’s Implementation of SAFe
30
![Page 31: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/31.jpg)
IAM’s Implementation of SAFe
31
![Page 32: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/32.jpg)
IAM’s Implementation of SAFe
32
![Page 33: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/33.jpg)
IAM’s Implementation of SAFe
33
![Page 34: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/34.jpg)
IAM’s Implementation of SAFe
34
![Page 35: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/35.jpg)
IAM’s Implementation of SAFe
35
![Page 36: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/36.jpg)
IAM’s Implementation of SAFe
36
![Page 37: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/37.jpg)
IAM’s Implementation of SAFe
37
![Page 38: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/38.jpg)
IAM’s Implementation of SAFe
38
![Page 39: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/39.jpg)
IAM’s Implementation of SAFe
39
![Page 40: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/40.jpg)
IAM’s Implementation of SAFe
40
![Page 41: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/41.jpg)
Another Example: Cloud & DevOps
What if you don’t have a program plan? Can you still get value out of scaled Agile practices?
41
![Page 42: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/42.jpg)
Cloud & DevOps Implementation of SAFe
42
Product VisionLong-term, 12+ months
Move 75% of apps to external cloud providers in 3 years
In progress!CloudOps and DevOps will have long-term vision statements and roadmaps.
For now, the closest thing to a vision:
![Page 43: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/43.jpg)
Program Increment Planning
We conducted a cross-functional team planning session to identify the Agile release teams that deliver value for the program.• In PI-1, the team measures value by minimal viable product (MVP)
needed to start cloud migrations• Includes Network, Security, Infrastructure, Cloud & DevOps teams
43
![Page 44: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/44.jpg)
Cloud & DevOps Implementation of SAFe
44
Product Roadmap12-18 months, revised quarterly
![Page 45: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/45.jpg)
Cloud & DevOps Implementation of SAFe
45
Release Planning3-6 months, revised each sprint
![Page 46: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/46.jpg)
Cloud & DevOps Implementation of SAFe
46
Sprint PlanningEvery 2 weeks
![Page 47: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/47.jpg)
Cloud & DevOps Implementation of SAFe
47
Daily PlanningEvery day
![Page 48: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/48.jpg)
Takeaways and Lessons Learned
48
SAFe enables teams to plan and deliver larger-scope items in multiple work streams over longer timeframes using multiple scrum teams.
• Establish a cadence using time-boxed, repeated activities that span multiple sprints
• Higher levels of planning require less detail and fidelity
• Create traceability methods that demonstrate how each task relates back to the high-level goals of a program increment
• Be faithful to Agile principles:
• Adaptability and openness to change
• Finished work is most important outcome
• Never skip the retrospective!
![Page 49: Scaling' Agile Implementing SAFe](https://reader036.vdocuments.net/reader036/viewer/2022081622/613cb30da3339922f86ed933/html5/thumbnails/49.jpg)
Thank you!