Disciplined Agile Delivery - UNIANDES · On your (un)successful agile projects, was compliance applicable? ... Question: From the point of view of the problem/business domain, at

Disciplined Agile Delivery The 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?


What Does it Mean to Scale Agile?

-or- Why Context Counts


Team Size


Geographic Distribution


Organizational Distribution



Compliance

Domain Complexity


Technical Complexity


http://www.google.ca/url?sa=i&rct=j&q=&esrc=s&frm=1&source=images&cd=&cad=rja&docid=V-xsPtWmSr6lyM&tbnid=7rn9Xc6r5aU56M:&ved=0CAUQjRw&url=http://www.honeywellnow.com/2012/01/25/honeywells-uop-selected-to-provide-petrochemicals-production-technology-for-two-key-projects-in-south-korea/&ei=Zz9TUaG4JoeOrgGJ0oCQCg&bvm=bv.44342787,d.aWM&psig=AFQjCNEstBx9Ids4N6om6cdLNnuoe_u4AA&ust=1364496500404434

Are Organizations Scaling Agile?

ambysoft.com/surveys/


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/

Agile Experiences with Geographic Distribution


On your (un)successful agile projects, how distributed were team members?

12


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


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/ 13

Agile Experiences with Compliance


On your (un)successful agile projects, was compliance applicable?

Note: Self imposed = CMMI, ISO, …

14


Agile Experiences with Domain Complexity

0% 10% 20% 30% 40% 50% 60% 70% 80%

High Risk

Complex

Medium complexity

Straightforward

Pilot Projects



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)


15

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



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/ 16


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

17

18

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

What Foundation Do You Need to Scale Agile?


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


Good People


Scrum Lean Kanban

DAD is a Hybrid Framework

22

Unified Process Agile Modeling

Agile Data Extreme

Programming SAFe

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.


Enterprise Awareness


http://www.google.ca/url?sa=i&rct=j&q=&esrc=s&frm=1&source=images&cd=&cad=rja&docid=IN6jRGENkPZzYM&tbnid=by3JBCgqLZyinM:&ved=0CAUQjRw&url=http://slant.investorplace.com/2013/03/oracle-stock-just-got-gutted-whats-next-for-enterprise-tech/&ei=MGlQUb3fI4SC2wXmhoHwDg&bvm=bv.44158598,d.b2I&psig=AFQjCNHsKKc0xx6L0UKcCvwbQpglRsvtug&ust=1364310661101675

A Full Delivery Lifecycle

24 © Scott Ambler + Associates

DAD Lifecycle: Advanced/Lean

25 © Scott Ambler + Associates

DAD Lifecycle: Continuous Delivery


Disciplined Agilists Take a Goal Driven Approach


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


How Do You Scale Agile?


“Scaling” Practices


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


Identifying the Initial Technical Strategy


Move Closer to a Deployable Release


Coordinate Activities




Context Counts – Tailoring and Scaling Agile


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


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


Disciplined Agile Delivery (DAD)

Disciplined Agile Delivery: The Foundation for Scaling Agile


Scrum Lean Kanban

XP Agile Modeling

And more… SAFe Outside In Dev.

Team Size Geographic Distribution

Compliance Domain Complexity Technical

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?


DisciplinedAgileConsortium.org DisciplinedAgileDelivery.com

Documents

Disciplined Agile Delivery - UNIANDES · On your (un)successful agile projects, was compliance applicable? ... Question: From the point of view of the problem/business domain, at