Make sprint
planning a
no-brainer
Implement recurring sprints with a realistic workload based on your team’s velocity. Leverage automation to make sprint planning hands-free and easy to adopt.
The fuss-free way to do agile
Don’t let agile processes bog you down. Automated sprint planning enables scheduled sprints to occur instantly without missing a beat (or an issue!).
“Set it and forget it”
agile planning
Predict your velocity.
Plan accordingly.
What our customers are saying
“In the last sprint review, it was fascinating to discover that from sprint to sprint, we always achieved the same average of weighted points. A team of 3 to 4 people cleared around 50 to 60 points in a biweekly sprint. This has happened in the past year. It’s really great to see, and it's a lot of fun.”
Why software teams love to plan sprints in Zenhub
For developers
For product leaders
Explore other features
Boards
Reporting
Roadmaps
Workflow automation
Planning poker
Zenhub extension
Key terms and concepts to know
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.
Velocity in agile project management measures a team’s work capacity in story points. Velocity is calculated by taking the total number of completed issues per sprint and finding the average across all sprints.
Story points in agile project management are a way of estimating the amount of effort a task will take relative to other issues the team is working on. Story points are not measured using time metrics.
“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.
A burndown chart is a graph that displays how many story points your team completes over the course of a single sprint. The X-axis displays a range of dates, and the Y-axis displays increments of story points. Ideally, the graph should steadily fall as the sprint progresses.
Planning poker is a collaborative method of estimating story points. Team members are all called to estimate the number of story points for a single issue, and that number is then averaged out to give the most accurate estimate.
Frequently asked questions
Can I manage sprints inside of GitHub?
Yes! All of Zenhub’s features are completely accessible inside GitHub when you download Zenhub’s GitHub Extension.
How do I set up Zenhub sprints?
If you click on the “+” button on the top right corner of Zenhub’s UI and click on “Modify recurring sprints,” you can set up recurring sprints. From there, you will be prompted to adjust sprints according to your team's needs. Learn more here.
Need more help?
