why start at the program level?
TRANSCRIPT
1Leffingwell et al. © 2014 Scaled Agile, Inc.Leffingwell et al. © 2014 Scaled Agile, Inc.
Scaled Agile Framework Implementation MethodsWhy Start at the Program Level?
Drew Jemilo, CTONovember 6th, 2014
®
2Leffingwell et al. © 2014 Scaled Agile, Inc.
Where Do You Begin?
So ... You want to scale ...
You’ve selected SAFe® ...
Where do you begin?
Portfolio Level?
Program Level?
Team Level?
3Leffingwell et al. © 2014 Scaled Agile, Inc.
Should You Start at the Portfolio Level?
Requires lean-thinking leaders and an Agile PMO who understand lean economics
Can be delayed due to the complex organizational and cultural changes needed for a full enterprise transformation
Difficult to manage software “assets” in a Lean-Agile portfolio if asset development isn’t agile
Portfolio Level?
Program Level?
Team Level?
4Leffingwell et al. © 2014 Scaled Agile, Inc.
Should You Start at the Team Level?
It’s easy (of course it is!) Implementing team-by-team
typically begins with your simplest systems and stand-alone teams (a “pilot”) but do we know how to address ... • Teams with disparate
practices?
• Managing dependencies?
• Alignment and guidance? You can measure
efficacy of a process at a small scale ... But who cares?
Delays dealing with the real challenges of implementing agile at scale
Portfolio Level?
Program Level?
Team Level?
5Leffingwell et al. © 2014 Scaled Agile, Inc.
Should You Start at the Program Level?
Requires more organization than going team-by-team, but significantly less effort than a “big bang” enterprise transformation
Makes visible the real challenges of agile at scale
Bigger, better results get more attention
Gives true, fact-based measures of enterprise agility ... the ability to quickly deliver quality software incrementally in a large, complex enterprise
Portfolio Level?
Program Level?
Team Level?
7Leffingwell et al. © 2014 Scaled Agile, Inc.
Accelerate Change: A One Week Launch
When you find a Value Stream, go All In and All at Once for each Train. The one week launch is a proven adoption model.
SAFeScrumMaster
SAFe Product Owner
Mon Tue Wed Thu Fri
Train everyone at the same time Same instructor, same method Most cost effective
Align all teams to common objectives Commitment Continue training during planning
Orientation for specialty roles Open spaces Tool training for teams
Too
l train
ing
GO.AGILE.NOW.
Training: SAFe ScrumXP
Prepare
SAFe Release Planning
8Leffingwell et al. © 2014 Scaled Agile, Inc.
... Or Take the Time the Organization Needs
A launch does not need to be done in one week
SAFeScrumMaster
SAFe ProductOwner
Tool Training
Backlog Mgmt
Training
Modules assume attendees have been through
SAFe ScrumXP
Coaching&
Mentoring
Product Manager/ Product Owner
TDDWorkshop
DevOps Training
Coaching&
Mentoring
Time in weeks ... or months ...
Training: SAFe ScrumXP
SAFe Release Planning