Agile project management in Extreme Programming projects. Carl Erickson Atomic Object LLC

Transcription

1 Agile project management in Extreme Programming projects Carl Erickson Atomic Object LLC

2 Professor life course planning team supervision evaluation research projects mentoring teaching grant writing

3

4 This talk Agile movement in general Extreme Programming (XP) in particular Role of PM not mentioned in first XP book

5 The view of some developers We don t need no stinkin project managers!

6 My view managing the XP process customer interaction facilitation measuring and tracking process above the project level

7 Why XP? Status quo: dismal NIST study human element Logical reaction, failed approach the heavyweight processes 1968 software crisis $60 billion each year formal communication, artifacts mean/end inversion top down eliminate messy human element

8

9 Agile methodologies Contrast to the heavyweights just enough means versus ends developer driven source code über alles Iterative versus sequential process to make great software what ultimately matters

10 Classic, sequential, waterfall

11

12 XP Practices

13 Testing Concurrent, test-driven versus sequential, separate Much more than defect removal specification design documentation

14

15 Pair work Programming Design Debugging Testing

16 Team work Life on the kibutz collective ownership No big bangs frequent integration Esperanto paradise coding standards

17 Customer relationship The borg whole team One slice at a time small, frequent releases Who, what, when, why planning game

18 Planning The hardest problems are not technical involve people at least proportional to team size A lot of behavior is driven by

19 FEAR

20 Legitimate customer fears Won't get what they ask for Will ask for the wrong things Pay too much for too little Won't see a meaningful plan Won't know where the project really stands Won't be able to react to changes in the business

21 Legitimate developer fears Will be told to do more than they know how to Will be told to do silly things Will have hard problems to solve without help Will be given responsibility, but no authority Won't be given clear descriptions of what is needed Will have to sacrifice quality to a deadline Won't have enough time to succeed

22 Planning addresses fear Is not anti-change spray stuff happens Embracing change always work on most important thing coordinate people understand the consequences of change Unacknowledged fears

23 The XP planning game Two aspects you re never done it takes two to plan Time cycles/phases/scale Releases Iterations Standups Pairing

24 Releases Pairing Standup Iteration Release Driven by the business Time scale months Unit of work the story Means of organization the story board + hours days weeks months

25 Iterations Pairing Standup Iteration Release Highest priority stories Time scale weeks Goal: tested, working system whole, but not feature complete risk reduction Short enough to estimate hours days weeks months

26 Estimation Pairing Standup Iteration Release Very hard lots of complicated models simplest best? Do, learn, improve for developers Publish, track for customers hours days weeks months

27

28

29 End of iteration Pairing Standup Iteration Release Acceptance tests by the customer Demo time! for customers for developers New stories hours days weeks months

30 Time scale days Borg brain synch Release progress plan for the day roadblocks Iteration Sharing Standup Pairing Standups hours days weeks months

31 Pairing Pairing Standup Iteration Release In the trenches Time scale hours Unit of work the task Means of organization the task board, facilities hours days weeks months

32

33 Summary Agile is spreading quickly grounded on known-effective practices anti-lessons from 30 years of failures working with developer best instincts This is good news should your children study IT?

34 Local competitiveness low quality, inflexible, expensive low quality, inflexible, cheap high quality, flexible, good value

35 Project manager role Deep understanding of process Representing the customer Educating the customer Tracking and communicating And maybe the hardest of all

36 The process above XP Out of scope for this talk But at least as important

37 References Planning Extreme Programming Kent Beck, Martin Fowler Addison-Wesley Extremeprogramming.org One of many now, but a good first start with some details. Johanna Rothman (jrothman.com) Author, speaker, consultant. Cool ideas on project management, appreciation of agile methodologies. Atomic Object (atomicobject.com) These notes, extended talk on XP