The Scaled Agile Framework (R) (SAFe(R) is a proven knowledge base for implementing agile practices at enterprise scale. The Framework has three levels: Team, Program, and Portfolio. Where should start implementation? In this presentation, learn why we start at the Program Level

1. Why Start at the
Program Level?
Drew Jemilo, CTO
Scaled Agile, Inc
October 15th, 2014
LeffingwelLl eeffti naglw. e©ll e2t0 a1l.4 © S 2c0a14le Sdc aAlegdil eA,g iIlen,c I.nc. 1

2. Where Do You Begin?
So...
 You want to scale...
 You’ve selected
SAFe...
 Where do you begin?
Portfolio
Level?
Program
Level?
Team
Level?
Leffingwell et al. © 2014 Scaled Agile, Inc. 2

3. 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?
Leffingwell et al. © 2014 Scaled Agile, Inc. 3

4. 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?
Leffingwell et al. © 2014 Scaled Agile, Inc. 4

5. 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?
Leffingwell et al. © 2014 Scaled Agile, Inc. 5

6. Leffingwell et al. © 2014 Scaled Agile, Inc. 6

7. 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.
Mon Tue Wed Thu Fri
SAFe
Scrum
Master
SAFe
Product
Owner
 Train everyone at
Leffingwell et al. © 2014 Scaled Agile, Inc. 7
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
Tool training
GO.
AGILE.
NOW.
Training:
SAFe ScrumXP
Prepare
SAFe Release
Planning

8. ... Or Take the Time the Organization Needs
A launch does not need to be done in one week
SAFe
Scrum
Master
SAFe
Product
Owner
Coaching
&
Mentoring
Training:
SAFe ScrumXP
SAFe Release
Planning
Leffingwell et al. © 2014 Scaled Agile, Inc. 8
Tool
Training
Backlog
Mgmt
Training
Modules assume
attendees have
been through
SAFe ScrumXP
Coaching
&
Mentoring
Product
Manager/
Product
Owner
TDD
Workshop
DevOps
Training
Time in weeks ... or months ...