1. Copyright 2006 - David Churchville - www.extremeplanner.com XP and Agile Planning David Churchville ExtremePlanner Software www.extremeplanner.com XP Fishbowl San Diego Code Camp San Diego Code Camp

2. Copyright 2006 - David Churchville - www.extremeplanner.com Topics Why Plan? Release planning Iteration planning Daily planning Example Questions?

3. Copyright 2006 - David Churchville - www.extremeplanner.com Why do we plan? To answer questions about a project –What will this system need to do? –What are the expected benefits? –When will it be available? –What will it take to build it? But mainly: Is it worth doing?

4. Copyright 2006 - David Churchville - www.extremeplanner.com Why does planning fail? Pitfalls of Traditional Plans –Activity-based instead of feature-based “resource” allocation and 100% utilization –Work is not prioritized by value –Uncertainty in estimates is ignored –Estimates are treated as commitments

5. Copyright 2006 - David Churchville - www.extremeplanner.com Why Agile Planning? The further we are from delivery, the less accurate the plan To reduce risk, we need to learn more by delivering working software quickly Feedback (product and technical) is used to improve the accuracy of the plan

6. Copyright 2006 - David Churchville - www.extremeplanner.com Agile Planning Levels Daily Planning (stand-up meetings)

7. Copyright 2006 - David Churchville - www.extremeplanner.com Agile Planning Levels Release Planning –Primary goals: overall vision, external communication –Feature level planning –Big picture thinking –Driven by the customer/product owner

8. Copyright 2006 - David Churchville - www.extremeplanner.com Agile Planning Levels Iteration Planning –Primary goals: internal communication –Task level planning –Development team drives this from priority and risk viewpoint

9. Copyright 2006 - David Churchville - www.extremeplanner.com Agile Planning Levels Daily Planning (standup meeting) –Primary goals: internal communication –Individual planning and coordination –Avoids duplicated effort –Difficult to “go dark”

10. Copyright 2006 - David Churchville - www.extremeplanner.com Release Planning Steps Brainstorm a set of user stories Estimate relative size of stories Choose release criteria (date or feature set) Prioritize stories for release Choose a set of features

11. Copyright 2006 - David Churchville - www.extremeplanner.com Release Planning Steps Brainstorm a set of user stories –Roles and goals –As a __ I can __ so that __ –Involve the entire product team –Review as a team to normalize –OK if we don’t capture everything

12. Copyright 2006 - David Churchville - www.extremeplanner.com Release Planning Steps Estimate size of stories –Use points or ideal time –Suggest S,M,L or 1,2,4,8,16 –Educated guess or “planning poker” –Goal is to help customer prioritize

13. Copyright 2006 - David Churchville - www.extremeplanner.com Release Planning Steps Choose Release Criteria –Fixed Deadline (we need it by Q2!) –Fixed Scope (when can we have it??) Issues –Can’t pick both scope and deadline! –Either scope or duration is fuzzy

14. Copyright 2006 - David Churchville - www.extremeplanner.com Release Planning Steps Prioritize Stories for Release –Force rank stories (1..2..3…N) or… –“Buy” stories Let each person pick top N Or give each person limited points to spend Allow small budget for infrastructure

15. Copyright 2006 - David Churchville - www.extremeplanner.com Release Planning Steps Choose stories for release –For date-driven releases, calculate capacity FTEs * Workdays * EffectiveHrsPerDay 4 FTE * 30 days * 5 hours per day = 120 ideal hours –Select stories based on what fits (convert size to duration) –Note which stories are “must have”, “should have”, and “nice to have” in case of scope cuts

16. Copyright 2006 - David Churchville - www.extremeplanner.com Iteration Planning Steps Re-prioritize work (after first) Select stories for the iteration –Determine iteration capacity –Priority-based or risk-based?

17. Copyright 2006 - David Churchville - www.extremeplanner.com Iteration Planning Steps Break stories into tasks –Estimate task durations (not size) –Split or merge stories as needed –Reality check for commitments No need to assign tasks.

18. Copyright 2006 - David Churchville - www.extremeplanner.com Daily Planning Steps Standup meeting –What did I accomplish yesterday? –What do I plan to accomplish today? –What are the obstacles blocking me? Keep it short!

19. Copyright 2006 - David Churchville - www.extremeplanner.com Daily Planning Steps Add any new tasks Sign up for tasks Update estimates and status Update “information radiators”

20. Copyright 2006 - David Churchville - www.extremeplanner.com Resources - Books Agile Estimating and Planning (Cohn) Planning Extreme Programming (Beck, Fowler) Agile Project Management with Scrum (Schwaber)

21. Copyright 2006 - David Churchville - www.extremeplanner.com Resources - Tools For small, co-located teams –Index cards, whiteboards –Excel spreadsheets For distributed teams/larger teams –ExtremePlanner (extremeplanner.com) –Version One (versionone.com) –XPlanner (xplanner.org)

22. Copyright 2006 - David Churchville - www.extremeplanner.com Example Sudoku Discuss and prioritize stories for the day

23. Copyright 2006 - David Churchville - www.extremeplanner.com Thank You For a copy of this presentation –Email: codecamp@extremeplanner.comcodecamp@extremeplanner.com