the foundation for scaling agile - amazon s3 · scaling from a solid foundation is easier • with...
TRANSCRIPT
Disciplined Agile DeliveryThe Foundation for Scaling Agile
© Scott Ambler + Associates 1
Scott W. Ambler
Senior Consulting Partner
scott [at] scottambler.com
@scottwambler
Let’s explore
a few important questions….
What does it mean to scale agile?
Are organizations really scaling agile?
What foundation do you need?
How do you scale agile?
© Scott Ambler + Associates 2
What Does it Mean
to Scale Agile?
-or-
Why Context Counts
© Scott Ambler + Associates 3
Team Size
© Scott Ambler + Associates 4
Geographic Distribution
© Scott Ambler + Associates 5
Organizational
Distribution
© Scott Ambler + Associates 6
© Scott Ambler + Associates 7
Compliance
Domain
Complexity
© Scott Ambler + Associates 8
Technical
Complexity
© Scott Ambler + Associates 9
Are Organizations
Scaling Agile?
ambysoft.com/surveys/
© Scott Ambler + Associates 10
Agile Experiences with Team Size
© Scott Ambler + Associates
On your (un)successful agile projects, how many IT team members were there?
11
Source: 2012 Agile Scaling Survey
www.ambysoft.com/surveys/
© Scott Ambler + Associates
IT Project Success Rates by Team Size
50%
40%
55%
55%
61%
58%
68%
70%
69%
74%
80%
83%
Traditional
Ad-Hoc
Iterative
Agile
Small Medium Large
Source: DDJ State of the IT Union Survey, July 2010
12
Agile Experiences with Geographic Distribution
© Scott Ambler + Associates
On your (un)successful agile projects, how distributed were team members?
13
Source: 2012 Agile Scaling Survey
www.ambysoft.com/surveys/
14
48%
55%
55%
59%
65%
69%
73%
74%
72%
73%
79%
80%
Ad Hoc
Traditional
Agile
Iterative
Co-located
Near Located
Far Located
Success Rates for Geographically Distributed Development
Source: Dr Dobb’s 2008 Project Success Survey
Agile Experiences with Organizational Distribution
0% 10% 20% 30% 40% 50% 60% 70% 80%
Outsourcing
Partner organizations
Contractors/consultants
Several countries
Several divisions
Same division
Had Successes Had Failures
© Scott Ambler + Associates
Question: In which of the following situations has the organization (un)successfully applied agile techniques? (Please check all that apply)
Source: 2012 Agile Scaling Survey
www.ambysoft.com/surveys/15
Agile Experiences with Compliance
© Scott Ambler + Associates
On your (un)successful agile projects, was compliance applicable?
Note: Self imposed = CMMI, ISO, …
16
Source: 2012 Agile Scaling Survey
www.ambysoft.com/surveys/
Agile Experiences with Domain Complexity
0% 10% 20% 30% 40% 50% 60% 70% 80%
High Risk
Complex
Medium complexity
Straightforward
Pilot Projects
Had Successes Had Failures
© Scott Ambler + Associates
Question: From the point of view of the problem/business domain, at what level(s) of complexity has the organization (un)successfully applied agile
techniques? (Please check all that apply)
Source: 2012 Agile Scaling Survey
www.ambysoft.com/surveys/17
Agile Experiences with Technical Complexity
0% 10% 20% 30% 40% 50% 60% 70% 80%
Multi-platform
Single platform
Fix legacy data
Access legacy data
Fix legacy systems
System integration
Package/COTS
Stand-alone
Greenfield
Had Successes Had Failures
© Scott Ambler + Associates
Question: In which technical situations has the organization (un)successfully applied agile approaches? (Please check all that apply)
Source: 2012 Agile Scaling Survey
www.ambysoft.com/surveys/18
What Foundation Do You
Need to Scale Agile?
© Scott Ambler + Associates 19
20
Disciplined Agile Delivery (DAD)
Disciplined Agile Delivery (DAD) is a process
decision framework
The key characteristics of DAD:
– People-first
– Goal-driven
– Hybrid agile
– Learning-oriented
– Full delivery lifecycle
– Solution focused
– Risk-value lifecycle
– Enterprise aware
© Scott Ambler + Associates
Good
People
© Scott Ambler + Associates 21
Scrum LeanKanban
DAD is a Hybrid Framework
22
Unified Process Agile Modeling
Agile DataExtreme
ProgrammingSAFe
DevOps …and more
DAD leverages proven strategies from several sources,
providing a decision framework to guide your adoption and
tailoring of them in a context-driven manner.
© Scott Ambler + Associates
Enterprise
Awareness© Scott Ambler + Associates 23
A Full Delivery Lifecycle
24© Scott Ambler + Associates
DAD Lifecycle: Advanced/Lean
25© Scott Ambler + Associates
DAD Lifecycle: Continuous Delivery
© Scott Ambler + Associates 26
Disciplined Agilists Take a Goal Driven Approach
© Scott Ambler + Associates 27
Goal Issue
Advantages
Disadvantages
Considerations
* Option
Default Option*
Explore the Initial
Scope
Form the
Initial Team
Address Changing
Stakeholder Needs
Source
Team size
Team structure
Team members
Geographic distribution
Supporting the team
Availability
Co-located
Partially dispersed
Fully dispersed
Distributed subteams
Goal: Form
the Initial
Team
© Scott Ambler + Associates 28
How Do You
Scale Agile?
© Scott Ambler + Associates 29
“Scaling” Practices
© Scott Ambler + Associates 30
Consumable solutions
Development intelligence
Requirements envisioning
Architecture envisioning
API first
Test suite API
Parallel independent testing
IT intelligence
Active stakeholder participation
Continuous deployment
Release train Multiple “backlogs”
Work item lists
Continuous documentation
Continuous architecture
Work item pools
Exploring the Initial Scope
© Scott Ambler + Associates 31
Identifying the Initial Technical Strategy
© Scott Ambler + Associates 32
Move Closer to a Deployable Release
© Scott Ambler + Associates 33
Coordinate Activities
© Scott Ambler + Associates 34
© Scott Ambler + Associates 35
© Scott Ambler + Associates 36
Context Counts – Tailoring and Scaling Agile
© Scott Ambler + Associates 37
Agile
Disciplined
Agile
Delivery
Agility
at
Scale
• Construction focus
• Value driven lifecycle
• Self-organizing teams
• Prescriptive
• Project team aware
• Delivery focus
• Risk-value driven lifecycle
• Self-organization with appropriate governance
• Goal driven
• Enterprise aware
Disciplined agile delivery with one or more complexity factors:
� Large teams
� Geographically distributed teams
� Organizational distribution
� Compliance
� Domain complexity
� Technical complexity
Scaling Requires…
• A disciplined approach
– Full delivery lifecycle
– Enterprise awareness
– Goal-driven approach
• A bit more up-front thinking
– Explore the initial scope a bit deeper
– Identify the initial technical strategy in a bit more detail
• More sophisticated coordination
– Individuals and interactions
• More sophisticated governance
– The greater the risk, the greater the need for effective governance
• More sophisticated validation
– Teams at scale are typically tackling harder problems
• More sophisticated tooling
© Scott Ambler + Associates 38
Scaling From a Solid Foundation is Easier
• With a DAD-based approach, scaling becomes straightforward because a handful
of process goals take the brunt of the tailoring:
– Explore initial scope
– Identify initial technical strategy
– Move closer to a deployable release
– Coordinate activities
© Scott Ambler + Associates 39
Disciplined Agile Delivery (DAD)
Disciplined Agile Delivery:
The Foundation for Scaling Agile
© Scott Ambler + Associates 40
Scrum LeanKanban
XP Agile Modeling
And more…SAFeOutside In Dev.
Team SizeGeographic
Distribution
Compliance Domain ComplexityTechnical
Complexity
Organizational
Distribution
DAD leverages proven strategies from several sources,
providing a decision framework to guide your adoption and
tailoring of them in a context-driven manner.
Got Discipline?
© Scott Ambler + Associates 41
DisciplinedAgileConsortium.org
DisciplinedAgileDelivery.com