‘Scaling’ Agile
Implementing SAFe
April 7, 2015 Tuesday 3:00-4:00 p.m. 50 Church St., 3rd Floor
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Guidelines and tips
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
SAFe enables teams to plan and deliver larger-scope items in multiple work streams over longer timeframes using multiple scrum teams.
Typology: Schemes and Mind Maps
2022/2023
1 / 49
This page cannot be seen from the preview
Don't miss anything!
Related documents
Partial preview of the text
Download 'Scaling' Agile Implementing SAFe and more Schemes and Mind Maps History in PDF only on Docsity!
‘Scaling’ Agile
Implementing SAFe
April 7, 2015 Tuesday 3:00-4:00 p.m. 50 Church St., 3rd Floor
- 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
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
IAM and Agile: A History
The Five Levels of Planning Always accurate, but at varying levels of precision.
Product Vision Long-term, 12+ months Product Roadmap 12-18 months, revised quarterly Release Planning 3-6 months, revised each sprint Sprint Planning Every 2 weeks Daily Planning Every day
IAM and Agile: A History
The Five Levels of Planning Always accurate, but at varying levels of precision.
Product Vision Long-term, 12+ months Product Roadmap 12-18 months, revised quarterly Release Planning 3-6 months, revised each sprint Sprint Planning Every 2 weeks Daily Planning Every day
What Didn’t Work: Story Mapping
Product Vision Long-term, 12+ months Product Roadmap 12-18 months, revised quarterly Release Planning 3-6 months, revised each sprint Sprint Planning Every 2 weeks Daily Planning Every day
The Missing Piece
What We Tried First: Release Planning
What We Tried First: Release Planning
Introducing Scaled Agile Framework (SAFe)
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?
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