Sprint Planning

At the beginning of each sprint, the team is responsible for working with the product owner to determine a sprint goal and committing to deliver working software that delivers functionality described in a set of PBIs.

You sprint planning document will likely be quite short. You should create a wiki page that includes:

• Sprint goal - A short description of what the team plans to achieve by the end of the sprint
• A priority-ordered list of PBIs that the team is committing to complete by the end of the sprint. With each PBI you should include:
  • A brief description of the business value gained by completing the PBI (~10 words)
  • The number of story points associated with the PBI
  • A link to the PBI (GitLab issue)
• Each committed PBI should have a list of tasks required to complete the PBI. Characteristics of well chosen tasks include:
  • Is obvious when the task is complete
  • Requires 2 - 5 hours to complete
  • Is not (or only loosely) coupled with other tasks
  • Is the responsibility of only one team member

Once the sprint is completed, a label should be added next to each PBI to indicate whether or not it was completed during the sprint, and a "total number of story points completed" should be added to indicate the velocity of the sprint.