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.

• 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:
  • The PBI number (e.g., 0004). This should link to the PBI
  • The number of story points associated with the PBI
  • The TL;DR from the PBI

Note: You will need to move the PBIs and any tasks associated with the PBIs to the .issues/open subdirectory. You may also need to refine the task list for each PBI for the sprint.

• Each PBI in the sprint 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 - 4 hours to complete
  • Is not (or only loosely) coupled with other tasks
  • Is the responsibility of only one team member

There must be a [X]plan.md document in the .sprints subdirectory of the project's core repo. The file should have the following format:

**Total Story Points**: [Sum of SP for all PBIs]

# Sprint [X] Plan
Sprint goal goes here.

# PBIs for this Sprint
1. [ ] [PBI#] [Story Points] [TL;DR]
2. [ ] [PBI#] [Story Points] [TL;DR]
3. [ ] [PBI#] [Story Points] [TL;DR]
4. [ ] [PBI#] [Story Points] [TL;DR]
...

# Risks
Identify any risks to successfully completing the sprint here.

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.