1 / 37

Agile project management in Extreme Programming projects

Agile project management in Extreme Programming projects. Carl Erickson Atomic Object LLC. Professor life. course planning team supervision evaluation research projects mentoring teaching grant writing. This talk. Agile movement in general Extreme Programming (XP) in particular

neorah
Download Presentation

Agile project management in Extreme Programming projects

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  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. This talk • Agile movement • in general • Extreme Programming (XP) • in particular • Role of PM • not mentioned in first XP book

  4. The view of some developers… We don’t need no stinkin’ project managers!

  5. My view… • managing the XP process • customer interaction facilitation • measuring and tracking • process above the project level

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

  7. 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

  8. Classic, sequential, waterfall

  9. XP Practices

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

  11. Pair work • Programming • Design • Debugging • Testing

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

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

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

  15. FEAR

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

  17. 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

  18. 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

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

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

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

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

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

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

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

  26. 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?

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

  28. Project manager role • Deep understanding of process • Representing the customer • Educating the customer • Tracking and communicating • And maybe the hardest of all…

  29. The process above XP • Out of scope for this talk • But at least as important

  30. 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

More Related