Today, we'll explore the next new report template - A Planning Poker. ♣️
In case, if you aren't familiar with the Planning Poker, you can read about this task estimation process here.
How to set up the report to efficiently run a Planning Poker via Standuply:
1️⃣ Set up the frequency of this process.
We recommend running this process a few days before every new Sprint planning ritual. E.g. if you start the new Sprint on Mon, every 2 weeks, so it means, by the Monday morning you should have a prepared backlog to pull the tasks from it into the new iteration.
So, in this case, you may schedule the planning poker report in Standuply to run since Wednesday, a week before the new Sprint. This way the team is able to review the backlog tasks asynchronously with no rush and you may just intense the process only if you find the big difference between team members estimations.
But based on our experience, if you have the proper setup process with the product owner, who creates, describes and prioritize stories in your backlog, for 90% of these stories team are able to provide the same assessment and discuss just 10% of most difficult tasks.
Standuply helps you this way to save a huge time by avoiding unnecessary meetings.
2️⃣ Select the poker player.
The planning poker players are usually the whole team who assesses the coming stories for the new iteration.
We strongly advise engaging the entire team into this process.
3️⃣ Set up the task tracker params.
It means that you should specify in Standuply your task tracker params to let it pull the tasks and send it to respondents for estimation.
By the moment of planning poker, the tasks in your backlog usually already prioritized by the product owner.
It means that you can select the "First N" tasks from the backlog column of your project to send them for the estimation.
This case, when the whole team participated in the processes, every poker run you will have the estimations of the same tasks from the eery team member. You will be able to review it and focus the team communication only on tasks which have the different estimations from your team and skip those ones that got the same assessment.
🅿️ - productivity 😂
It's not necessary for the planning poker to specify the assignee from your task tracker. Because in this process all members estimate all tasks. But you can do this if needed in your particular case.
4️⃣ Create the questions to ask on planning poker.
So, afterward, you just need to write down the questions that every respondent have to answer. Or you may just use our samples. It depends what style of estimation you use. Eather it story point estimations or T-Short sizes.
5️⃣ Choose the channel to share results.
So, as for usual reports in Standuply you just can specify the report summary delivery point.
We recommend sharing the report summary of the planning poker with the entire team in the separate Slack channel.
This case the whole team stay updated and can discuss or add the comments to the assessments from other teammates.
Into the Slack, the process looks like this:
So, as usual, be even more productive with the Standuply and let us to handle the whole routine work to let you be focused only on crucial things. 😎
Note: currently, the planning poker works only for the Trello, but shortly we'll extend it to JIRA, Asana, and other task trackers.