For developers
Provide story point estimates directly on the GitHub Issue- Story point estimation happens on their own schedule
- Less time spent in meetings estimating story points
Planning poker
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
Estimation that fits everyone’s schedule
Collaborate and get everyone’s feedback on story point estimates without ever hosting a meeting. Zenhub lets your team estimate on their own time and will let you know the results.
Estimate inside GitHub
Developers have a lot on their plate – and story points aren’t usually top-of-mind. Make things simpler for them by enabling them to estimate inside GitHub with Zenhub’s GitHub extension.
Increase story point accuracy
Unbiased story point estimations
Avoid bias by allowing team members to provide estimates anonymously without knowledge of what other team members estimate.
More accurate velocity
Planning poker encourages teams to provide more accurate story points, improving the overall accuracy of velocity calculations in Zenhub and giving realistic ideas into your team’s capacity.
testimonials
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.”
Read the story
Bob Wei
Engineering Manager at Dapper Labs
Why Zenhub
Why software teams love planning poker
For product leaders
- Manage story point estimation from Zenhub while letting devs work in GitHub
- Increase the overall accuracy of your team’s agile reporting
- No need to use third-party tools to facilitate story point estimation practices
additional zenhub features
Explore other features
Boards
Learn more
Reporting
Learn more
Sprint planning
Learn more
Workflow automation
Learn more
Roadmaps
Learn more
Zenhub extension
Learn more
glossary
Key terms and concepts to know
Story points
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
Agile estimation or story point estimation is the process of estimating story points to determine the amount of effort an issue requires.
Sprints
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
“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
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.
Need Help?
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?
Visit our Help Center