Templates /
Sprint Turnover Process

Sprint Turnover Process

Reviewing, estimating, and assigning issues to the next sprint.
1
Introduction:
2
Click the "Complete sprint" button in JIRA
3
Review the "Issues for Next Sprint" JIRA search
4
Review the "Recently created unresolved bugs" JIRA search
5
Estimate all issues for new sprint in the Agile Poker tool
6
Divide sprint issues up
7
Move all unassigned issues into the next sprint
8
Start the new sprint
9
Sources:
10
Related checklists:

Introduction:

Teams need to do a certain amount of upkeep between sprints, and that’s what this checklist is for. To make sure you aren’t missing any issues you kicked out of the last sprint, or any bugs that cropped up mid-sprint, run this checklist at the end of every sprint period.

To make it easier for yourself, tag issues in JIRA as suggested in this process. Tagging issues "Issues for Next Sprint", "Recently Created Unresolved Bugs", etc, helps you quickly filter the issues so you can see only the vital ones.

This process is linked to another one you can use if you need to, the Sprint Estimation Process.

Click the "Complete sprint" button in JIRA

Mark the sprint as complete is JIRA by clicking the arrow next to the Agile button. Click Work, then choose Complete Sprint next to the name of the sprint you want to complete.

Estimate all issues for new sprint in the Agile Poker tool

Agile Poker tools:

Divide sprint issues up

Divide all the issues up between each team member.

For each issue being carried over, be sure to subtract however many points have been completed in those issues.

The total points per person should be ~16.

Move all unassigned issues into the next sprint

Start the new sprint

You can use a sprint name generator like this one to help you come up with a unique and interesting name for the upcoming sprint.

Sources:

Take control of your workflows today.