Effective Iteration Planning
The Agile Samurai: Chapters 9, 10, 11
Productive Task Flow
The purpose of client meeting is to review what you did.
The purpose of client meeting is to plan what you're doing next.
Backlog to Task Board Flow
This is a lot to do in one hour.
How to Meet Effectively: Focus
Good: writing scenarios and user stories, defining acceptance and user tests, sketching UI flow
Bad: reviewing details of the current app, creating detailed UI mockups, creating an app wish list, discussing technical options,
Get conversations back on track by repeatedly asking
What scenario is this for -- and is that most important?
What user test results are we try to achieve?
How to Meet Effectively: Be Realistic
Expanding a user story means defining
at least one
: a concrete example with real data, input conditions, and output results
at least one
: a user task scenario, and measure of success or failure
any changes to the user interface, all changes to user flow
At 5 minutes per item, that's 15 minutes for one user story.
Iteration Planning Progress Chart
Don't check yes until you have data (story, sketch, ...) in hand, on paper, or online.
How to Meet Effectively: Timebox
Have a big visible schedule and clock.
Same schedule can work for every meeting.
Leave 5 minutes at the end for note-taker to repeat user story development goals and priorities.
Work it out with the client.
Get a good, loud, countdown timer app.
Have note-taker be in charge.
a parking lot document
open for notes on discussions to continue later by another channel.
Thanks to Hakim El Hattab for
the slide template