Estimate effort effortlessly
Story point estimation – in half the time. Planning poker enables you to request estimates from select team members and have estimates automatically applied when a consensus is reached.
A more accurate way to estimate
Agile estimation with planning poker allows your team to come to a consensus on story points that everyone agrees on without biased input.
Make agile work for your team
Increase story point
accuracy
What our customers are saying
“Zenhub offers the fundamentals while including useful additions, like planning poker. Using planning poker and high-priority tagging makes it easy to set and see priorities.”
Why software teams love planning poker
For developers
For product leaders
Explore other features
Boards
Reporting
Sprint planning
Workflow automation
Roadmaps
Zenhub extension
Key terms and concepts to know
Story points in agile project management estimate the amount of “effort” an individual issue will require. “Effort” isn’t necessarily time-based, it's a relative value that is measured by comparing the size of one issue to another.
Agile estimation or story point estimation is the process of estimating story points to determine the amount of effort an issue requires.
Sprints, in agile project management, are defined periods of time in which a software team commits to an assigned group of issues to work on. Sprints are usually 2-4 weeks long.
“Issues” in agile project management are another word for smaller tasks or individual units of work. In Zenhub, issues best suited to developers are GitHub Issues and issues best suited to non-technical team members are Zenhub Issues.
Planning poker is a story point estimation technique that traditionally involves handing voting cards to team members, discussing the logistics of completing an issue and voting anonymously for how much effort the issue would take. The effort is measured in story points.
Frequently asked questions
What is planning poker?
The concept of “planning poker” is an agile estimation technique used to get more accurate results by requesting input from select members of a team to vote on what story point estimate they feel is most realistic for an issue.
Can you request multiple issues be estimated at the same time?
Yes, you can request that multiple issues be estimated at the same time from the Zenhub board view. To do this, click on multiple issues at the same time and then “set estimate”.
Do you need to use planning poker to estimate in Zenhub?
No, you can set your own story point estimates if you do not wish to get input from your team on how large an issue is. However, planning poker is recommended as an agile best practice for its accuracy.
Need more help?
