introduction to disciplined agile delivery (dad) · disciplined agile delivery (dad) is a process...

Introduction to

Disciplined Agile

Delivery (DAD)

Today’s Workshop

• Workshop strategy• Introduction to Disciplined Agile Delivery (DAD)• Topic Identification• Delivering the Workshop Agilely• Wrap Up

© Disciplined Agile Consortium 2

Workshop Strategy

© Disciplined Agile Consortium 3

Identifying Questions

© Disciplined Agile Consortium 4

• Each workshop participant should have some sticky notes

• The instructor is just about to present an overview of DAD

• As the instructor does so, you are likely going to identify questions or issues that you would like to see addressed in detail today

• Write a single question/issue per sticky note

• We’ll be using the sticky notes later

© Disciplined Agile Consortium 5

Example topics:– Funding– Estimation– Architecture– Metrics– Governance– Change management– Adopting DAD– Outsourcing– Risk management– Organizing DAD teams– …

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

© Disciplined Agile Consortium 6

Scrum

Extreme Programming

LeanKanban

DAD is a Hybrid Framework

© Disciplined Agile Consortium 7

Unified Process Agile Modeling

Agile Data“Traditional”Outside In Dev.

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.

SAFe

A High Level Lifecycle

© Disciplined Agile Consortium 8

Scrum Construction Lifecycle

© Disciplined Agile Consortium 9

A good start…

A Scrum Delivery Lifecycle

© Disciplined Agile Consortium 10

…but this is how agile teams actually work…

Unbranded Agile Delivery Lifecycle

© Disciplined Agile Consortium 11

…and it’s time to abandon the branding.

Governed Delivery Lifecycle

© Disciplined Agile Consortium 12

Disciplined agile teams are guided by senior management…

Disciplined Agile Delivery: Basic Lifecycle

© Disciplined Agile Consortium 13

…and realize they work in an organizational ecosystem.

Disciplined Agile Delivery: Lean Lifecycle

© Disciplined Agile Consortium 14

DAD doesn’t prescribe a single lifecycle…

The Phases Disappear Over Time

© Disciplined Agile Consortium 15

First release: Inception Construction Transition

Second release: I Construction T

Third release: I Construction T

Nth+ releases: C CT C C TT T

.

.

.

…and promotes continuous learning and improvement.

Disciplined Agile Delivery: Lean Continuous Delivery Lifecycle

© Disciplined Agile Consortium 16

A goodend goal

DAD Teams Are Enterprise Aware

Disciplined agilists:• Work closely with

enterprise groups• Follow existing

roadmap(s) where appropriate

• Leverage existing assets

• Enhance existing assets

© Disciplined Agile Consortium 17

IndependentTester

Disciplined Agile Delivery (DAD) Roles

© Disciplined Agile Consortium 18

Team Lead TeamMember

StakeholderProductOwner

ArchitectureOwner

Specialist DomainExpert

TechnicalExpert

Integrator

PrimaryRoles

SecondaryRoles

(for scaling)

Some “Radical” Agile Ideas• Do the simplest thing possible and no more• Changing requirements are a good thing• Teams should have all the skills and knowledge

required to get the job done• Less is often more – Keep all artifacts as

lightweight as possible• Capture detailed requirements and designs as

executable tests, not written documents or models• Collaboration is critical to your success• Test often and early, and better yet test first• Non-solo development is more effective than

people working alone• Too much up front modeling and planning

increases project risk• Learn from your experiences, and evolve your

strategy as the project progresses• Stakeholders have greater visibility into an agile

project and greater opportunities to guide the team

© Disciplined Agile Consortium 19

Critical Agile Practices

• Continuous documentation• Non-solo work• Iteration burndown charts• Change management• Configuration management• Architectural spikes• Test-driven development (TDD)• Continuous integration (CI)• Continuous deployment (CD)• Look-ahead planning• Look-ahead modeling• Parallel independent testing• Reviews• Retrospectives

20© Disciplined Agile Consortium

DevOps Through the DAD Lifecycle

© Disciplined Agile Consortium 21

Inception Construction Transition

O&S = Operations & Support

Initial release planning includes

deployment

O&S staff stakeholders throughout

construction

Transition planning

throughout construction

O&S staff key decision makers

regarding production readiness

Support staff observes

stakeholder satisfaction levels

Deployment into production

Dev team implements

O&S oriented requirements

O&S staff stakeholders in initial modeling

sessions

DAD is Goal-Driven, Not Prescriptive

© Disciplined Agile Consortium 22

Strategies for Capturing Requirements Detail

• BRUF (detailed specifications)• Requirements envisioning (lightweight specifications)• Goals driven• No modeling at all

© Disciplined Agile Consortium 23

Strategies for Change Management

© Disciplined Agile Consortium 24

Formal Change Management

Strategies for Functional Requirements

© Disciplined Agile Consortium 25

Strategies for Initial Estimating

• Formal point counting• Planning poker (wide-band delphi)• Similar sized items• Educated guess by the team• Educated guess by an experienced

individual• Cost/schedule set by the stakeholders

© Disciplined Agile Consortium 26

Strategies for Funding Projects

© Disciplined Agile Consortium 27

Fixed price/cost

Stage-gatefunding

Time andmaterials (T&M)

Continuous/Drip

Low T&Mplus delivery

bonuses

Disciplined Agilists Take a Goal Driven Approach

© Disciplined Agile Consortium 28

ProcessGoal

ProcessFactor

AdvantagesDisadvantagesConsiderations

* OptionDefault Option

*

Explore the Initial Scope

Form theInitial Team

Address Changing

Stakeholder Needs

SourceTeam sizeTeam structureTeam membersGeographic distributionSupporting the teamAvailability

Co-locatedPartially dispersedFully dispersedDistributed subteams

Indicates a preference for the options towards the top

© Disciplined Agile Consortium 29

Goal – Secure Funding

30© Disciplined Agile Consortium

Goal – Secure Funding (cont.)

31© Disciplined Agile Consortium

© Disciplined Agile Consortium 32

33© Disciplined Agile Consortium

Context Counts – Tailoring and Scaling Agile

© Disciplined Agile Consortium 34

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 scaling factors:� Large teams� Geographically distributed teams� Compliance� Domain complexity� Technical complexity� Organizational distribution

Governance is Built Into DAD

• Governance strategies built into DAD:– Risk-value lifecycle– Light-weight milestone reviews– “Standard” opportunities for increased visibility and to steer the team

provided by agile– Enterprise awareness– Robust stakeholder definition

© Disciplined Agile Consortium 35

Workshop Tailoring

© Disciplined Agile Consortium 36

Tailoring this Workshop

© Disciplined Agile Consortium 37

1. Share Potential Questions– Everyone should have some questions/issues

they would like to see addressed– Come to the task board, announce each

question one at a time, put it on the task board

2. Affinity Grouping– The instructor will group the questions into topics

3. Estimate– The instructor will estimate the amount of time to

deliver each topic

4. Prioritize– As a group we need to prioritize the topics

5. Deliver

© Disciplined Agile Consortium 38

© Disciplined Agile Consortium 39

What Does it Mean to Be Disciplined?

• In general, it requires discipline to follow many agile practices and philosophies

• But, it also requires discipline to:– Reduce the feedback cycle– Learn continuously– Deliver solutions incrementally– Be goal driven– Enterprise aware– Streamline Inception and

Transition efforts– Adopt agile governance

strategies

© Disciplined Agile Consortium 40

Disciplined Agile Delivery (DAD)

Disciplined Agile Delivery:The Foundation for Scaling Agile

© Disciplined Agile Consortium 41

Scrum LeanKanban

XP Agile Modeling

And more…SAFeOutside In Dev.

Team SizeGeographicDistribution

Compliance Domain ComplexityTechnical

Complexity

OrganizationalDistribution

DAD leverages proven strategies from several sources,providing a decision framework to guide your adoption and

tailoring of them in a context-driven manner.

A Disciplined Ending….

Please…– Take the opportunity to thank your teammates – we all learned together– Fill out the workshop evaluation form(s)– Turn in the evaluation(s) to the instructor

© Disciplined Agile Consortium 42

Got Discipline?

© Disciplined Agile Consortium 43

DisciplinedAgileConsortium.orgDisciplinedAgileDelivery.com

Disciplined Agile DeliveryDisciplined Agile Delivery

Thank You!scott[at] scottambler.com

@scottwambler

AgileModeling.comAgileData.orgAmbysoft.com

DisciplinedAgileConsortium.orgDisciplinedAgileDelivery.com

ScottAmbler.com

Disciplined Agile DeliveryDisciplined Agile Delivery

© Disciplined Agile Consortium 44

Recommended Resources

© Disciplined Agile Consortium45