{"id":11612,"date":"2017-07-20T13:36:46","date_gmt":"2017-07-20T13:36:46","guid":{"rendered":"https:\/\/www.process.st\/templates\/sprint-estimation-process\/"},"modified":"2024-02-28T20:45:54","modified_gmt":"2024-02-28T20:45:54","slug":"sprint-estimation-process","status":"publish","type":"post","link":"https:\/\/www.process.st\/templates\/sprint-estimation-process\/","title":{"rendered":"Sprint Estimation Process"},"content":{"rendered":"
\n

Introduction: <\/h2>\n
\n

Sprint Estimation is part of the Sprint Turnover<\/a> process, which happens at the end of the last sprint but before the next sprint starts.<\/p>\n

The idea is to check your JIRA for issues that were kicked out of the last sprint, or issues that appeared during the last sprint period. To make this process run smoothly, make sure to tag the issues in JIRA as you go.<\/p>\n

For example, any feature-related issues will be planned ahead of time. These issues should be tagged \u2014 along with anything kicked out of the previous sprint \u2014 with "Issues for Next Sprint". This gives the whole team visibility of what they're going to work on, and helps you play Agile Poker!<\/p>\n<\/p><\/div>\n<\/section>\n

\n

Start with a joke <\/h2>\n
\n

Start with a joke and break the ice. You're all about to get together and play Agile Poker, after all.<\/p>\n

Use the Dad Joke Generator<\/a>!<\/p>\n<\/p><\/div>\n

\n
\n <\/a>
\n <\/figure>\n<\/p><\/div>\n<\/section>\n
\n

Review "Issues for Next Sprint" search in JIRA <\/h2>\n
\n

As you progressed through your last sprint, there will have been issues to kick out, or issues that appeared but you didn't have time to address straight away. These should be tagged "Issues for Next Sprint", so you can easily access them for the estimation process.<\/p>\n

[Insert a link to a filtered JIRA view of issues for next sprint]<\/em><\/p>\n<\/p><\/div>\n<\/section>\n

\n

Review recently created unresolved bugs <\/h2>\n
\n

Let's make sure nothing was missed by reviewing issues tagged "Recently Created Unresolved Bugs" in JIRA.<\/p>\n

Here's the link: [Insert link to a filtered JIRA view showing recently created unresolved bugs]<\/em><\/p>\n<\/p><\/div>\n<\/section>\n

\n

Estimate issues for the next sprint using Agile Poker plugin <\/h2>\n
\n

Planning poker<\/a> is a way for a team to quickly assign story points to issues without being influenced by each other's decisions.<\/p>\n

For example, if one member were to assign 5 points to an issue out loud, the other members might be inclined to blindly agree to not risk being disagreeable or wrong. In a Planning poker situation, this is impossible because all point 'bets' are secret until the final reveal.<\/p>\n

Agile Poker tools you can try:<\/p>\n