This document provides guidance on iteration planning meetings from an agile perspective. It begins with an overview of typical planning elements such as vision, status, iteration theme, dates and capacity. It then notes that the level of formality can vary between teams. Alternative approaches are suggested such as skipping pre-defined elements, focusing on conversation over templates, and ensuring the meeting is fun. The document emphasizes finding the right approach for each team and considering assumptions, participants' needs, and keeping the process interesting.

1. Iteration
P lanning
With The
Captain
@theagilepirate
photo by @mdwragg

2. Where Do
Ye Stand ?

3. “ By The Book”

4. Vision & Roadmap
Current Status
Iteration Theme/Name
Prior Data
Dates
Capacity
Issues/Logistics
DOD
Backlog Extract
Tasking
Issues & Risks
Dependencies & Assumptions
“Commitment” – actually it’s Forecast!
Communications
Parking Lot
Actions
Retrospect

5. Reality ?

6. 1-3
5-10
1-5
1-5
3-10
3-10
5-15
3-15
1-20
5-10
15-60
5-25
5-25
1-5
5-10
0-15
1-5
1-15
Intro
Vision & Roadmap
Current Status
Iteration Theme/Name
Prior Data
Dates
Capacity
Issues/Logistics
DOD
Backlog Extract
Tasking
Issues & Risks
Dependencies & Assumptions
“Commitment” – actually it’s Forecast!
Communications
Parking Lot
Actions
Retrospect

7. “ By The Captain”
Arrr, well they be more guidelines than rules

8. Extras
These work for us, they might not for you
Sitting down, tomfoolery, joking 3
A Proper one! 30
90 Minutes is a long time 4
Usually more humour, chocolate, biscuits 3
Intro
Retrospective
Coffee Break
Regroup

9. Stuff We Skip Over (& why!)
Actually – we’re not so great at this right now
Already know this, we have a standup beforehand
Vision & Roadmap
Current Status
These just come up in natural conversation
Easy – it’s live (usually)
Just general focus (our backlog is *really* coarse)
Issues/Logistics
DOD
Backlog Extract
Part of the conversation again
They’re usually tasks in themselves
We just run a quick capacity check
In Hindsight this is because I don’t like doing it!
On The Board
Tasks, right?
“Was that worthwhile”
Issues & Risks
Dependencies & Assumptions
“Commitment” – actually it’s Forecast!
Communications
Parking Lot
Actions
Retrospect

10. Loads, most of the team think it’s dull 3
I like names... should use them again 2
Sprint Dates, Holidays & interrupts 5
This is critical on my project 10
Yup, that’s our main activity 25
Did We Miss Anything Important? 5
Prior Data
Iteration Theme/Name
Dates
Capacity
Tasking
Close
Stuff We Find
** VALUABLE **

11. Our
Reality

12. How Long?
30 minutes for a full retrospective
10 minutes of breaks
50 minutes of *actual * planning
Everyone knows the detail of what’s going on and why - long
before we go near a meeting room
We still miss things
We work in a very high-trust organisation
We Make sure it’s fun

13. Find The Happy Middle Ground
Your Turn

14. Time To Share

15. (Re)Considerations
Assumptions on what’s ready before the planning meeting?
Who are the participants & what are their needs?
Can you use your board as a tool ?
What data & metrics will you use?
How do you keep it fun & interesting?
Are there alternatives?
So We’ve P lanned, What happens next?

16. Thank-you
Simon Cromarty
Simon.Cromarty@red-gate.com
http://red-gate.com
@theagilepirate
Captain@theagilepirate.net
http://theagilepirate.net