AgileSoftwareDevelopment 1

Transcription

1 Agile Software Development What is Agile Software Development Willem van den Ende Rob Westgeest XPDayBenelux 2006 AgileSoftwareDevelopment 1

2 Agile 'dictionary' A gymnast is agile A motorcyclist is agile in dutch: 'lenig' in dutch: 'Wendbaar' A supertanker is not agile, because course corrections take a long time AgileSoftwareDevelopment 2

3 Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more. See for authors and copyright AgileSoftwareDevelopment 3

4 What is it about?????? AgileSoftwareDevelopment 4

5 Seek the real goal Anticipated finish finish Start AgileSoftwareDevelopment 5

6 apply Feedback AgileSoftwareDevelopment 6

7 facilitating project management Power to the people self organisation AgileSoftwareDevelopment 7

8 deliver AgileSoftwareDevelopment 8 value

9 Getting things done AgileSoftwareDevelopment 9

10 ... Deployment Test Implementation Design Requirements t Plan Inverting the Time Axis t AgileSoftwareDevelopment 10

11 Agile instances XP Scrum DSDM (Agile) RUP Clear Crystal EVO Lean FDD AgileSoftwareDevelopment 11

12 Umbrella Commons All agile methods are (to different extents) iterative incremental customer (value) focused Differences bottom-up, start from practices (XP, Scrum) top-down, start from framework (RUP, DSDM) Instances of framework based methods can be less agile, e.g. because people follow the templates or don't customize AgileSoftwareDevelopment 12

13 Crystal Family Alistair Cockburn From Surviving OO Projects to Crystal Family of methodologies Cooperative game of invention and collaboration Adapt methodology to project Created by interviewing teams Understanding instead of discipline AgileSoftwareDevelopment 13

14 Crystal 'hardness' vs project size hardness / size Life Essential money Discretionary money Comfort AgileSoftwareDevelopment e6 e20 e40 e80 d6 d20 d40 d80 c6 c20 c40 c80

15 Crystal Clear Designed for fixed price, fixed scope, fixed deadline projects Counter under bidding risk with creative use of process three principles: Frequent deliveries Reflective Improvement Close Communication -> Osmotic Communication AgileSoftwareDevelopment 15

16 Scrum 30 day sprints define functionality and leave the team to organise it requirements stabilise during sprint Daily fifteen minute Scrums report progress plan tasks for next day AgileSoftwareDevelopment 16

17 Scrum AgileSoftwareDevelopment 17

18 Lean Software Development Toyota way principles Continuous Improvement (Hansei) Relentless Reflection AgileSoftwareDevelopment 18

19 Lean SD principles Eliminate Waste Amplify Learning Decide as Late as Possible Deliver as Fast as Possible Empower the Team Build Integrity In See the Whole AgileSoftwareDevelopment 19

20 extreme Programming 12 Basic practices not specific to XP XP applies them aggressively 5 Values to go beyond practices Wanted to see what would happen if we turned all the knobs up to 10 - Kent Beck AgileSoftwareDevelopment 20

21 XP Practices On-site Customer Planning Game 40 Hour Work Week Metaphor Simple Design Refactoring Testing Short Releases Pair Programming Coding Standards Collective Ownership AgileSoftwareDevelopment 21 Continuing Integration

22 XP - Feedback Needed to stay on track Small steps => small adjustments Implemented through Short releases / Fixed Length Iterations Continuous integration Pair Programming On-site customers Extreme Testing Discipline AgileSoftwareDevelopment 22

23 DSDM AgileSoftwareDevelopment 23

24 (Rational) Unified Process Mid nineties Three Amigo's Booch, Jacobson, Rumbaugh Iterative Incremental Risk Driven Use Case Centric AgileSoftwareDevelopment 24

25 Rup AgileSoftwareDevelopment 25

26 The Agile Umbrella XP Scrum DSDM (Agile) RUP Clear Crystal EVO Lean FDD AgileSoftwareDevelopment 26

27 Often seen Scrum like planning (see this afternoon) Standup meetings Test Driven Development (from XP) Team reflection AgileSoftwareDevelopment 27

28 Reflection chart Keep This AgileSoftwareDevelopment 28 Try This Ongoing problems

29 What is it about? Seek the real goal Embrace change Getting things done Deliver value Self organisation Feedback AgileSoftwareDevelopment 29

30 AgileSoftwareDevelopment 30

31 Pull Systems Toyota Kanban Customer Supermarket as inspiration pulls from Manufacturer pu lls fro m pulls from Supermarket Inventory Supermarket Shelf Flow where you can pull where you must Flow only when takt time is managable AgileSoftwareDevelopment 31

32 Pull Sample Manufacturer Car factory Production cell truck + kanban truck + parts + kanban AgileSoftwareDevelopment 32

33 Software Pull Sample Todo AgileSoftwareDevelopment 33 Developing Tested

34 CMM or Agile Defined process Goal is clear Way to achieve the goal is clear Underlying processes are well understood Control by force and change control Empirical process Goal seems (more or less) clear Way to achieve goal is difficult to define/predict Control by inspection and adaptation AgileSoftwareDevelopment 34

35 Agile and CMM AgileSoftwareDevelopment 35

36 Agile and CMMI AgileSoftwareDevelopment 36

37 Agile and... AgileSoftwareDevelopment 37

38 Getting started with... Just do it (Courage) Start small inside out (from programming to planning) or outside in (from customer to programming) AgileSoftwareDevelopment 38

39 Agile and Configuration Mgmt AgileSoftwareDevelopment 39