If you are just getting started, this quick tour guide will help you get to know ZenHub. With links to more in-depth getting started tutorials, get off to the right start with the right amount of knowledge to get your workflow in ZenHub setup and your team off to a great start!
From unorganized lists to prioritized workflows
In ZenHub, Workspaces are how you bundle GitHub repositories into a single view. With Workspaces, teams can give bundles of GitHub repositories names and descriptions for better project and workflow tracking. Using Workspaces, teams can create multi-repo workflows to track otherwise silo'd repositories in the same view. Workspaces are inspired by kanban boards and present a simple yet incredibly robust picture of your software projects.
A GitHub repository can be added to more than one ZenHub Workspace. This means each team can create their own Workspace and pipeline structure for the same repo or set of repos. This empowers teams to visualize the status of an Issue according to their own process and workflow.
Acting as a point of focus for teams, visualizing work to be done helps teams answer important questions, such as: “What are our current priorities?”, “What are our highest priority Issues?”, “Do we have any blockers? Are we on target?”
Boards create a picture of project work and processes. By visualizing work this way, you can create focus, establish flow, and continuously improve.
Using Epics to plan and track work
GitHub Issues have no real hierarchy; they're simply a list. Getting insight into which Issues are related, blocked by each other, reliant on other work, or a sense of everything that is being worked on for a project is difficult to determine.
ZenHub Epics add a crucial layer of hierarchy to your GitHub Issues. With Epics, you get greater control end-to-end over the release process. ZenHub Epics help bundle similar tasks into themes of work, which help you plan and track work against larger goals.
Plan smarter and stay informed easier. Learn more about ZenHub Epics in the complete guide here.
Sprint planning with ZenHub
How much work can we actually tackle? Can we really ship all this work in the next two weeks? What Issues can we potentially remove from scope? All questions that your team should tackle before sprint planning. But how do you get the answers to these questions?
Leveraging GitHub's Milestones and using ZenHub story points your team can leverage the information you are already creating inside GitHub to best answer these questions without having to jump into another tool or duplicate data.
From visualizing your sprint backlog, to seeing how you're progressing towards the end of your sprint, ZenHub helps you stay focused. Learn more about sprint planning in ZenHub in our complete guide to creating your first sprint using ZenHub.
Get indicators of project progression using Burndowns
As an early indicator of how projects are progressing, ZenHub's Burndown Charts help teams meet their sprint goals.
Like every ZenHub feature, Burndown Charts integrate with GitHub activity so there is no extra busy work to get accurate reporting against your goals. Each time your team closes an Issue, a new data point is added to the chart.
Burndowns help teams meet deadlines more predictably by providing an early indicator of how a project is coming along. Learn more about Burndowns in ZenHub in our reporting guide here.
Continuously improve using insight from Velocity charts
In isolation, the amount of work completed in one Milestone isn't very helpful. Factors outside your control – a sick teammate, an unexpected bug – are bound to pop up. Life happens. Viewing work completed over time, however, becomes a valuable piece of insight. ZenHub Velocity reporting provides reporting on how your team's amount of work completed fluctuates over time, giving you instant visibility into work done sprint-over-sprint.
Velocity Charts provide insights on how much work your team can realistically tackle. Learn more about Velocity tracking in ZenHub in our reporting guide here.
Understand Issue cycle and lead time using the Control chart
Supporting the Kanban methodology, the Control chart does not require estimation and provides Issue cycle and lead time, or how long Issues take from start to finish. This can help predict how quickly your upcoming Issues will be closed and helps uncover bottlenecks and blockers in particular areas of your process.
Provide stakeholder visibility into your process and identify abnormalities to help improve process with the Control chart. Learn more about reviewing Issue cycle and lead time with the Control chart here.
Visualize Issue throughput using the Cumulative flow diagram
The cumulative flow diagram does not require estimation and helps teams track how much work is accumulating within each pipeline across a set date range. Understanding where work is accumulating surfaces bottlenecks and process improvement opportunities.
Understand how Issues flow across your pipelines and visualize if Issues are getting caught up within a particular workflow stage. Learn more about the cumulative flow diagram here.
Understand how scope changes impact deadlines with Release reports
Releases in ZenHub are used for tracking long-term, flexible scope dynamically changing projects. Feature launches often span multiple sprints and involve multiple teams collaborating together. The release report helps teams better understand scope changes over time to determine if you're on track to hit important goals. As scope changes, the Release report dynamically updates to provide predictions around end dates.
Gain visibility into multi-team, multi-sprint goals and reduce the uncertainty that comes with planning long-term deliverables with Release reports. Learn more on using Release reports here
Improve your workflow with much more!
Have questions? Continue on in our getting started guides or drop us a note—we are here to help!