1. Planning Meeting
A hands-on guide to running an Agile
Planning Meeting

2. Complexity
Pieces Systems
PRD/MRD Stories Hypothesis
Experts
Logistics Generalists Emergent
Specialists Stochastic Stakeholders
Deterministic
Reflection
Gantt Charts
Feedback Loops
Up-front Design Patterns Fractal
Technical Dynamic Social
Complexity Complexity Complexity
When software is socially complex.
(There isn’t a right or wrong way.)

3. Cone of uncertainty
“statistically predictable levels of project estimate uncertainty at each
stage of the project”
[Courtesy Jeff Atwood & Steve McConnell]
http://www.codinghorror.com/blog/2006/06/the-mysterious-cone-of-uncertainty.html

4. Relative Estimation
Breed Height (cm) Relative
Terrier
Bulldog
Labrador
Saint Bernard
Poodle
Great Dane
German Shephard

5. Fractal Rhythm
Release
(Epics & Themes)
Iteration
(Stories)
Day
(Tasks)
We are
here

6. Stories vs Tasks
• stories have value to stakeholders
• seek feedback and test hypothesis
• work as one
• delivered in full (binary)
• tasks may not and will expand to fill
time

7. Release / Launch
Prioritized Backlog (200sp)
1. Lorem ipsum dolor sit amet (36pts)
2. Consectetur adipisicing elit (30pts)
3. ed do eiusmod tempor incididunt ut
labore et dolore magna aliqua (32pts)
4. Enim ad minim veniam, quis nostrud
exercitation (24pts)
5. llamco laboris nisi ut aliquip ex ea
commodo consequat. (24pts)
6. Duis aute irure dolor in reprehenderit in
voluptate velit esse cillum dolore eu fugiat
nulla pariatur. (32pts) Velocity = 45 sp / itr
6. Excepteur sint occaecat cupidatat non
proident, sunt in culpa qui officia deserunt
mollit anim id est laborum. (22pts) 200 / 45 ≈ 5
Iterations Remaining
48pts 35pts 52pts
ship ship ship
plan plan plan
Iterations = Story Points / Velocity

8. Cards facilitate
[Courtesy: http://www.infoq.com/articles/agile-kanban-boards]

9. Shared spaces
[Courtesy: http://www.infoq.com/articles/agile-kanban-boards]

10. Running planning
meeting

11. 1. Pre-meeting
Engage stakeholders and prepare
• collect cards for new stories
• reprioritize stories with product
owner
• update velocity and charts
• solicit feedback from stakeholders
• hold retrospective; add cards

12. 2. Hold Meeting
Estimate and pick stories for next
iteration (< 2 hrs)
• Planning poker — involve team, not
“experts” — on new stories
• Pick stories for next iteration
• Clarify stories with Product Owner
• Don’t assign stories or re-estimate
Planning poker: http://planningpoker.com/detail.html

13. Post-meeting, daily
routine
• work stories in priority order
• clarify story with product owner, seek
feedback
• document behavior with tests
• deploy/ship working software
• leave no in-progress work

14. Thanks!
Soren Harner
http://permaling.com