agile dc 2013 - comparing scaled agile framework (safe) with disciplined agile delivery (dad)

Agilex www.agilex.com

Comparing Scaled Agile Approaches: Scaled Agile Framework (SAFe) &Disciplined Agile Delivery (DAD)

Rodney Bodamer - Agile Coach, SAFe SPC, CSPGreg Pfister - VP Agile Practices, SAFe SPC, CSP

Presented by:


Assumptions – Agile Foundations


Key Characteristics of Agile Delivery

Agile Principles and ValuesAgile Manifesto Values & Principles (DAD and SAFe)Transparency, Program Execution, Code Quality, Alignment (SAFe)

Source: National Audit Office review of literature


What do we mean by scaling?


Large Scale Agile Program Teams

4+ Service and Support Teams

Prod

uct M

anag

emen

t

Rele

ase

Man

agem

ent

Dev

Ops

Tea

m

Arch

itect

ure

Team

10+ Delivery Teams


Scaled Agile Framework (SAFe) “Big Picture”

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


Scaled Agile Framework (SAFe) – 3 Levels

7


Scale to the Portfolio Level

Roles/Teams

• Enterprise Architect

• Epic Owner• Program Portfolio

Management

Events

• Strategic Investment Planning

• Kanban Portfolio (Epic) Planning

Artifacts

• Investment Themes

• Business and Architecture Epics

• Portfolio Backlog• Portfolio Vision• Metrics


Scale to the Program Level

Roles/Teams

• Product Management• Release Management• System Team• DevOps• Business Owners• System Architect• Release Train Engineer• UX Architect

Events

• PSI/Release Planning• System Demo• Inspect & Adapt

Workshop

Artifacts

• Product Roadmap• Vision• Program Backlog• Team Backlog• NFRs• Architecture Runway• Business and

Architecture Features• PSI Objectives• Metrics


Agile Team Level

Roles/Teams

• Agile Teams• Product Owner• Scrum/Agile

Master

Events

• Sprint Planning• Backlog Grooming• Daily Stand-up• Sprint Demo• Sprint

Retrospective• HIP Sprints

Artifacts

• Team Backlog (incl. NFRs)

• Team PSI Objective• Sprint Goals• Working Software• Spikes• Metrics


Disciplined Agile Delivery (DAD) Delivery Process

“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


Disciplined Agile Delivery (DAD) “Big Picture”



DAD Inception

• 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

iINCEPTION

Goals for Inception Phase



DAD Construction

• 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- ITERATIVEc


DAD Construction

• 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- INTEGRATEDc


DAD Transition

• Ensure the solution is production ready

• Ensure the stakeholders are prepared to receive the solution

• Deploy the solution into production

TRANSITIONt

Goals for Transition Phase


DAD Scaling Factors and Governance

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


• 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)

Sample Government Deliverables and SAFe Alignments


Inceptioni

c ti

c Construction t Transition

c ti


Inceptioni c Construction t Transition

Identify, prioritize, select and fund projects

i



ii

INCEPTION



iINCEPTION



CONSTRUCTIONc


Inceptioni c Construction t Transitionc

CONSTRUCTIONc



CONSTRUCTIONc



t

TRANSITIONt


Inception c Construction t Transition

TRANSITIONt

i

t



t

TRANSITIONt



TRANSITIONt



t

TRANSITIONt


SAFe Key Takeaways

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


DAD Key Takeaways

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


DevOps


Questions

41Agilex www.agilex.com