Iteration Planing Meeting Process

Pre-meeting actions

• Review existing pending, estimated, open, and trouble tickets -- PMs
• Close all stories for which assets have been completed -- PMs
• Go over all stories that are committed to the current iteration
• Clone any story that has not been completed yet, and link the cloned story to the existing one
  • Change the status of the newly cloned story to "Ready for Estimation"
• If a story is still in the "Committed to an iteration" status, change its status to "Estimated" so that it can potentially be committed to the next iteration
• Write new stories or feasible ideas for the next itertion.

First Meeting:

• Calculate total points completed for current iteration.
• Go over any newly created stories and revise them if necessary so that they can be estimated
  • Any story that needs to be estimated for the next iteration needs to be but in the "Ready for Estimation" status
     

Second Meeting:

• Go over all stories that are in the "Ready for Estimation" status and estimate them
  • If the story description does not have enough information so that it can be estimated, change its status to "Open" (<--?), so that it can be revised. Also add an appropriate comment, why it needs revision
  • After estimating a story, change its status to "Estimated"

Third Meeting:

• Calculate the total story points from the past iteration, by adding up the points from all the Stories, whose status is "The End".
• Go over all the stories that are in the "Estimated" state.
• Commit Stories to the next iteration considering priorities, number of story points, etc.
  • If a story gets committed to the next iteration, change its status to "Committed to an iteration"