Skip to content

Instantly share code, notes, and snippets.

@punitrathore

punitrathore/iteration-planning-meeting.md

Last active December 19, 2017 22:00
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save punitrathore/a413801a18171a6f27783521c43e2bb9 to your computer and use it in GitHub Desktop.
Save punitrathore/a413801a18171a6f27783521c43e2bb9 to your computer and use it in GitHub Desktop.
Download ZIP
Iteration Planning Meeting
Raw
iteration-planning-meeting.md

Weekly Planning Meeting

Purpose

To ensure that you have a comprehensive plan for the week, so that no energy is spent procastinating, and "thinking" about what you need to do next.

Vocabulary

  • Vision : Vision is the final goal of the project.
  • Strategy : Is a way through which the vision is realized.
  • Tactics The steps taken to achieve the strategy.
  • Minimum Viable(MVP) : The minimum list of features that the product needs before it can be shipped to the customer so that we can get feedback.
  • Iteration : The strategy we use to get to our goal is to use an iteration. An iteration is a week long period we use to divide our development schedule.
  • Iteration Planning Meeting : At the start of the week we gather as a team to figure out the week's plan of programming tasks(or issues). Tasks are taken from the "backlog" and added to the "current iteration". Tasks which are added to the current iteration are broken down into smaller tasks(if needed)
  • User Story/Issues/Tasks : They describe a certain use case of the application that is being built. This should not be more than 3 sentences long.
  • Estimation : Each task will get an estimate of how long it will take to be complete. The estimate can be 1, 2 or 3 days.
  • Retrospective : At the end of the week, the team gets together to review the iteration to see what went well, and what could be improved. Action items are captured from the discussion to ensure the feedback is implemented.

Project Tracking Board Columns

  1. Backlog : All tasks that are planned / incomplete that are needed for the project to be complete
  2. Current Iteration : Tasks that are chosen by the team to be worked on for the current week. Each of these tasks are estimated by the engineer that is going to work on them.
  3. In Progress : The tasks that are currently being worked on.
  4. In Review : Tasks which are dev complete, but are waiting to be merged by the lead developer.
  5. Completed : Tasks which have been completed and are ready to be deployed to production.

Iteration planning questions

  • What project(s) am I going to work on this week?
  • What are the features in each of the projects that I want to complete this week?
  • How many members are in my team?
  • Who is going to work on the features in the iteration?
  • How long will this task take to complete?

Additional Notes

  • During the course of the week, if new work/features is identified, create new tasks and add them to the backlog. If the new tasks are applicable to the work in the current iteration, inform the lead developmer so the task can be estimated, and added to the iteration.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment