Sprint Review

The key component of the Sprint Review is presenting your progress to your Product Owner. It should be clear from your presentation what progress was made. Demoing working software is critical to this communication. In addition, you will document your progress in your repo. At the end of each sprint, make a copy of the [X]plan.md file calling it [X]review.md.

• Insert a first line **Sprint Velocity**: Y where Y is the total number of story points for all completed PBIs.
• Mark all of the completed PBIs with a x inside the square brackets
• Update links to completed PBIs (which have now moved to the issues/closed subdirectory
• Add a Reflections section after the Risks that discusses completion (or not) of the sprint goal, any changes in scope or direction to any of the PBIs, explanations for any incomplete PBIs (including what work remains), and knowledge gained that impacts future work. Your reflections should be focused on the impact to the project, not discussions about process. Those discussions belong in the retrospective document.

The file might look somet

**Sprint Velocity**: [Completed points]
**Total Story Points**: [Sum of SP for all PBIs]

# Sprint [X] Plan
Sprint goal goes here.

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

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

# Reflections
Discussion goes 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.