Adopting the Scaled Agile Framework: The Theory and the Practice - Dallas ALN - October 2013
1. ADOPTING THE SCALED AGILE
FRAMEWORK:
THE THEORY AND PRACTICE
EM CAMPBELL-PRETTY, GM STRATEGIC DELIVERY
@PrettyAgile
www.prettyagile.com
TELSTRA TEMPLATE 4X3 BLUE BETA | TELPPTV4
au.linkedin.com/in/ejcampbellpretty/
ejcampbellpretty@gmail.com
2. THE EDW AGILE RELEASE TRAIN
Average delivery cycle time down from 12 month to 3 months
Frequency of delivery increased from quarterly to fortnightly
Cost to deliver down 50%
95% decrease in product defects
100% projects delivered on time and on budget
Happy project sponsors
Happy teams
10. THE AGILE RELEASE TRAIN
The ART is a long-lived, self-organizing team of agile teams
that delivers solutions
• A virtual organization of 5 – 12 teams (50-100 individuals) that
plans, commits, and executes together
• Common cadence and normalized story point estimating
• Aligned to a common mission via a single program backlog
• Operates under architectural and UX guidance
• Produces valuable and evaluate-able system-level Potentially
Shippable Increments (PSI) every 8-12 weeks
Define new
functionality
Implement
Acceptance
Test
Deploy
Repeat until further notice. Project chartering not required.
11. THE BEST WAY TO START
When you find the first train, go “All In” and “All at Once”
Mon
Tue
Thu
Release
Planning
Fri
Enterprise
Scrum
Master
Quickstart
Enterprise
Product
Owner
Quickstart
Train everyone at the
same time
Same instructor,
same method
Cost effective
Align all teams to
common objectives
Commitment
Continue training
during planning
Tool training
Training:
SAFe
ScrumXP
Wed
You
Are
Agile,
Now
Orientation for
specialty roles
Open spaces
Tool training for
teams
16. SCALING THE PRODUCT OWNER
Source: Agile Portfolio and Program Management in the Scaled Agile Framework, Dean Leffingwell, Agile Melbourne Meetup, 15/02/12
20. RELEASE PLANNING
Cadence-based PSI/Release Planning meetings are the “pacemaker”
of the agile enterprise
•
•
•
•
•
Two days every 8-12 weeks
Everyone attends in person if at all possible
Product Management owns feature priorities
Development team owns story planning and high-level estimates
Architects, UX folks work as intermediaries for governance,
interfaces and dependencies
• Result: A committed set of program objectives for the next PSI
24. CONTINUOUS INTER-TEAM COORDINATION
Agile teams self-manage dependencies and resolve risks
Agile Team 1
Join other
team scrum
ceremony
Dependent
story
Agile Team 2
• Agile team members may visit
other team’s…
• Backlog grooming: to see what’s
coming next sprint, request
adjustments
• Sprint planning: request
adjustments
• Daily standups: follow up on
execution
• Team Demo: summarize current
stage
34. A LITTLE TASTE OF OUR CULTURE
http://www.prettyagile.com/2013/05/the-power-of-haka.html
35. WANT TO KNOW MORE ABOUT THE
EDW AGILE RELEASE TRAIN?
Check out my blog: www.prettyagile.com
•
•
•
•
•
•
•
A Perspective on the Scaled Agile Framework
What Happens to Project Managers When You Implement SAFe?
Book Clubs at Work – Are You Serious?
Bookshelf
Leading Through Vulnerability
The "Bubble Up" Approach to Scaling Retrospectives
The Power of Haka