Created
July 23, 2021 11:35
-
-
Save tahb/8e1700e4409b8c36711b1819ae64cbac to your computer and use it in GitHub Desktop.
Mid-sprint review template
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # <project name> - Mid-Sprint Review | |
| 2020-09-30 | |
| - Meeting objectives | |
| - Review sprint goals | |
| - Review Trello | |
| - Update sprint goals | |
| ## Meeting objectives | |
| - To check whether we’re doing the right things | |
| - To check whether we are making the progress we expected | |
| - To make sure everyone has visibility of what’s been done | |
| - To adjust what we do if needed | |
| ## Review sprint goals | |
| Briefly remind ourselves of what we expected to be working towards. | |
| 1. Epic 1 | |
| a. Do A, we will know when we are done when X | |
| b. Do B, we will know when we are done when X | |
| 2. Epic 2 | |
| a. Do C, we will know when we are done when X | |
| 3. Epic 3 | |
| a. Do D, we will know when we are done when X | |
| b. Do E, we will know when we are done when X | |
| c. Do F, we will know when we are done when X | |
| ## Review Trello | |
| Walk the board backwards as a group, acknowledge what's been done and discuss what's in progress and if anything is stuck. | |
| ## Reflect | |
| The team should now have a freshed context of how the team are progressing against our estimations. | |
| - Update the goals in this document to colour code those that are done, likely to be done and unlikely to be done | |
| - Do we need more work or do we need to set new expectations about what we think will be done? | |
| - Do we need to bring in more support to help us? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment