Iteration Planning Workflow

Scope: To be read by all project managers, i.e., who participate in iteration planning.

Executors: Project managers

Goal: Ensure that right amount of clear and important issues are assigned to each contributor for the next iteration and to decrease time spent on iteration planning in meetings.

Workflow

• This should be done by @Liza before the meeting (by Friday):
  • Look through each contributor and assess, if they currently have too much/too little assigned issues, based on their working hours and capacity. Compare previous iterations and their outcomes, as well as time marked on calendar.
    • In case of too many assigned issues:
      • look through their issues and remove tasks with low priority or that are not time-critical.
    • In case of too few assigned issues:
      • look through the issue pool and assign them new issues from the backlog (starting from status::ready).
• For Issues marked for the current iteration @Liza does:
  • For issues with progress:
    • The assignee has given a short update on the current status as a comment.
    • In case this is not done by Friday:
      • The project manager will reach out to the respective contributors and remind them to do so.
  • For issues without progress:
    • Read through and ensure, that the description is clear and sufficient to start working on it.
    • Ping the assignee to make sure they are aware of the issue and ask if they have any questions or need help.
  • For issues in review:
    • Look over the MR and remind the reviewers to review it.
• In the meeting a short discussion should be held to address any concerns. Further can be read in the meeting workflow.