Disciplined Agile Delivery The Foundation for Scaling Agile

Transcription

1 Disciplined Agile Delivery The Foundation for Scaling Agile Scott W. Ambler Senior Consulting Partner scott[at] Scott Ambler + Associates 1

2 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

3 What Does it Mean to Scale Agile? -or- Why Context Counts Scott Ambler + Associates 3

4 Team Size Scott Ambler + Associates 4

5 Geographic Distribution Scott Ambler + Associates 5

6 Organizational Distribution Scott Ambler + Associates 6

7 Compliance Scott Ambler + Associates 7

8 Domain Complexity Scott Ambler + Associates 8

9 Technical Complexity Scott Ambler + Associates 9

10 Are Organizations Scaling Agile? ambysoft.com/surveys/ Scott Ambler + Associates 10

11 Agile Experiences with Team Size On your (un)successful agile projects, how many IT team members were there? Scott Ambler + Associates Source: 2012 Agile Scaling Survey 11

12 IT Project Success Rates by Team Size Agile 55% 70% 83% Iterative 55% 68% 80% Ad-Hoc 40% 58% 74% Traditional 50% 69% 61% Small Medium Large Source: DDJ State of the IT Union Survey, July 2010 Scott Ambler + Associates 12

13 Agile Experiences with Geographic Distribution On your (un)successful agile projects, how distributed were team members? Scott Ambler + Associates Source: 2012 Agile Scaling Survey 13

14 Success Rates for Geographically Distributed Development Iterative 59% 80% 74% Agile 55% 79% 73% Co-located Near Located Traditional 55% 73% 69% Far Located Ad Hoc 48% 72% 65% Source: Dr Dobb s 2008 Project Success Survey 14

15 Agile Experiences with Organizational Distribution Question: In which of the following situations has the organization (un)successfully applied agile techniques? (Please check all that apply) Same division Several divisions Several countries Contractors/consultants Partner organizations Outsourcing 0% 10% 20% 30% 40% 50% 60% 70% 80% Had Successes Scott Ambler + Associates Had Failures Source: 2012 Agile Scaling Survey 15

16 Agile Experiences with Compliance On your (un)successful agile projects, was compliance applicable? Note: Self imposed = CMMI, ISO, Scott Ambler + Associates Source: 2012 Agile Scaling Survey 16

17 Agile Experiences with Domain Complexity 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) Pilot Projects Straightforward Medium complexity Complex High Risk 0% 10% 20% 30% 40% 50% 60% 70% 80% Had Successes Scott Ambler + Associates Had Failures Source: 2012 Agile Scaling Survey 17

18 Agile Experiences with Technical Complexity Question: In which technical situations has the organization (un)successfully applied agile approaches? (Please check all that apply) Greenfield Stand-alone Package/COTS System integration Fix legacy systems Access legacy data Fix legacy data Single platform Multi-platform 0% 10% 20% 30% 40% 50% 60% 70% 80% Had Successes Had Failures Scott Ambler + Associates Source: 2012 Agile Scaling Survey 18

19 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 20

21 Good People Scott Ambler + Associates 21

22 DAD is a Hybrid Framework SAFe DevOps and more Extreme Agile Data Programming Unified Process Agile Modeling Scrum Kanban Lean 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 22

23 Enterprise Awareness Scott Ambler + Associates 23

24 A Full Delivery Lifecycle Scott Ambler + Associates 24

25 DAD Lifecycle: Advanced/Lean Scott Ambler + Associates 25

26 DAD Lifecycle: Continuous Delivery Scott Ambler + Associates 26

27 Disciplined Agilists Take a Goal Driven Approach Goal * Issue * Option Default Option Advantages Disadvantages Considerations 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 Scott Ambler + Associates 27

28 Goal: Form the Initial Team Scott Ambler + Associates 28

29 How Do You Scale Agile? Scott Ambler + Associates 29

30 IT intelligence Release train Development intelligence Multiple backlogs API first Continuous documentation Consumable solutions Requirements envisioning Continuous architecture Scaling Practices Continuous deployment Work item lists Test suite API Active stakeholder participation Parallel independent testing Work item pools Architecture envisioning Scott Ambler + Associates 30

31 Exploring the Initial Scope Scott Ambler + Associates 31

32 Identifying the Initial Technical Strategy Scott Ambler + Associates 32

33 Move Closer to a Deployable Release Scott Ambler + Associates 33

34 Coordinate Activities Scott Ambler + Associates 34

35 Scott Ambler + Associates 35

36 Scott Ambler + Associates 36

37 Context Counts Tailoring and Scaling Agile Agility at Scale Disciplined Agile Delivery Agile Disciplined agile delivery with one or more complexity factors: Large teams Geographically distributed teams Organizational distribution Compliance Domain complexity Technical complexity Delivery focus Risk-value driven lifecycle Self-organization with appropriate governance Goal driven Enterprise aware Construction focus Value driven lifecycle Self-organizing teams Prescriptive Project team aware Scott Ambler + Associates 37

38 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

39 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

40 Disciplined Agile Delivery: The Foundation for Scaling Agile Compliance Geographic Distribution Outside In Dev. Domain Complexity Team Size SAFe Technical Complexity Organizational Distribution And more XP Agile Modeling Scrum Kanban Lean Disciplined Agile Delivery (DAD) 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 40

41 Got Discipline? DisciplinedAgileConsortium.org DisciplinedAgileDelivery.com Scott Ambler + Associates 41