Building upon well established Scrum, XP, and lean software development methods, agile scaling frameworks such as Dean Leffingwell's Scaled Agile Framework (SAFe) and Scott Ambler's Disciplined Agile Delivery (DAD) address large, complex software delivery initiatives through their full delivery lifecycle from project initiation to production. These frameworks have received significant interest in both federal government and private industries, recognizing the need for continued team-based iterative and incremental adaptive approaches to software development, balanced with scaling processes and factors at the Program and Portfolio levels and organizational governance models and guidance for large enterprise engagements. This session will provide a brief overview of these two agile scaling models, address the benefits of what both are trying to accomplish, and compare and contrast specific similarities and differences.
6. Agilex www.agilex.com
ScaledAgile Framework(SAFe)“BigPicture”
Well defined and proven
knowledge base for implementing
agile practices at enterprise scale
Scales successfully to large
numbers of practitioners and
teams
Building off of Scrum, XP, and Lean
agile development approaches
Synchronizes alignment,
collaboration and delivery
Elaborated in books: Agile
Software Requirements (2011) and
Scaling Software Agility (2007)
®
“Big Picture” highlights the individual
roles, teams, activities and artifacts
necessary to scale agile from the team
to program to the enterprise level
Source: Scaledagileframework.com
11. Agilex www.agilex.com
DisciplinedAgileDelivery(DAD)DeliveryProcess
“DAD is a goal-driven process framework
that is people-first, learning-oriented
hybrid agile approach to IT solution
delivery. It has a risk-value lifecycle,
goal-driven and scalable”
Hybrid, end-to-end agile delivery
lifecycle with tailoring strategies
Building off of Scrum, XP, and
Lean agile development
approaches and methods
Scalable, people first, learning
oriented, agile, goal-driven,
enterprise aware, risk and value
driven
Guidelines for governing
enterprise teams in an agile
manner
Elaborated in the book:
Disciplined Agile Delivery (2012
Source: Disciplined Agile Delivery, Ambler
13. Agilex www.agilex.com
DADInception
• Form initial Teams
• Identify the vision for the
project and get approved
• Align with enterprise
direction
• Identify initial technical
strategy, requirements, and
release plan
• Set up work environment
• Secure funding
• Identify risks
i
INCEPTION
Goals for
Inception Phase
Source: Disciplined Agile Delivery, Ambler
14. Agilex www.agilex.com
DADConstruction
• Produce a potentially
consumable solution
• Address changing stakeholder
needs
• Move closer to deployable
release
• Maintain or improve upon
existing levels of quality
• Prove architecture early
Goals for
Construction Phase
CONSTRUCTION- ITERATIVE
c
15. Agilex www.agilex.com
DADConstruction
• Produce a potentially
consumable solution
• Address changing stakeholder
needs
• Move closer to deployable
release
• Maintain or improve upon
existing levels of quality
• Prove architecture early
Goals for
Construction Phase
CONSTRUCTION- INTEGRATED
c
16. Agilex www.agilex.com
DADTransition
• Ensure the solution is
production ready
• Ensure the stakeholders
are prepared to receive
the solution
• Deploy the solution into
production
TRANSITION
t
Goals for
Transition Phase
17. Agilex www.agilex.com
DADScalingFactorsandGovernance
DAD Scaling Factors DAD Governance Strategies
• Scaled IT projects are governed in
some way
• DAD supports different
governance types
• Scope and breadth of governance
adapts with work environment
• Leverage existing corporate assets
to address issues that optimize
performance
• Push decisions to local level
wherever possible
Team Size
Geographic Distribution
Organizational Distribution
Compliance
Domain Complexity
Technical Complexity
2
Co-located
Single Division
None
Straightforward
Straightforward
1000s
Global
Outsourcing
Life Critical
Very Complex
Very Complex
Copyright 2013 Scott Ambler + Associates
18. Agilex www.agilex.com
• Legislation
• Budget
• Policy
• Directives
• Architectural Standards
• Data Exchange Standards
• Hosting Strategies
• Security Standards
SAFe roles with software development lifecycle
documentation responsibilities
Program Portfolio Mgmt
• Quad Chart (MS 0)
• IPT Charter (MS 0)
• BRD (MS 0)
• Project Charter (MS 0)
• Acquisition Strategy (MS 0)
Product and Release
Management
• PMP (MS 1)
• Transition Plan (MS 1)
• Risk Register / Log (MS 1)
• Outcome Stmt (MS 1)
• Version Descrip Doc (MS 2)
• Deployment Plan (MS 2)
• Lessons Learned (MS 3)
Shared Resources
• Operational Accept Plan (MS 1)
• Accept Criteria Plan (MS 1)
• Reqs Specification Doc (MS 1)
• Sys Security Plan (MS 2)
• Production Ops Manual (MS 2)
• Security Guide (MS 2)
• 508 Certification (MS 2)
• ATO (MS 2)
• Privacy Impact Assess (MS 2)
• User Guide (MS 2)
• SLA (MS 2)
System Architect
• System Design Doc (MS 1)
System Team
• Test Evaluation (MS 2)
• Master Test Plan (MS 2)
SampleGovernmentDeliverablesandSAFeAlignments
38. Agilex www.agilex.com
SAFe KeyTakeaways
SAFe “Pros”
Proven, well documented, and flexible
framework; lean underpinnings
People-centric view on agile delivery
with clear roles, artifacts, events
Holistic, 3-tier view of value stream
including Portfolio level
Strong Code Quality (Agile Engineering
and DevOps) focus
Established scaling framework in
marketplace
Constant refinement of SAFe knowledge
base
SAFe “Cons”
Prescriptive
Heavy weight
Certification-centric
39. Agilex www.agilex.com
DADKeyTakeaways
DAD “Pros”
Hybrid framework having foundation in
proven lean & agile approaches
Phases with milestones emphasize reality
of large-scale agile delivery lifecycle
Flexibility with strong emphasis on agile
adoption tailoring
Strong technical architecture / engineering
focus
Governance clarity for program / product
management
DAD “Cons”
Unknown marketplace adoption
Limited broad-based training certification
and knowledge-base refinement
Lack of prescriptiveness requiring agile
consultants