TrustRadius Insights for Zenhub are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Business Problems Solved
Zenhub has become an essential tool for development teams looking to streamline their project management process. With its seamless integration with Github, users are able to effortlessly organize, plan, and run sprints using existing Github issues and workflows. The user-friendly interface requires no training, making it accessible for both product and engineering teams.
Many users have found Zenhub to be a valuable project planning tool that offers all the necessary features for effective organization and tracking. It serves as an agile storyboard pipeline tracker and allows for coordination with source control. By visualizing work and tracking implementation progress, Zenhub significantly improves bottom line results for development projects.
With its intuitive Kanban/Scrum boards, Zenhub is widely used by IT teams, including product owners and project managers. It facilitates backlog management and sprint planning by providing stakeholders with a clear status overview. Furthermore, Zenhub fills the gaps in Github's sprint planning and backlog management tools by adding extra categorization with Epics and enabling better estimation and tracking of work.
As a project management board for repositories uploaded to Github, Zenhub becomes the go-to platform for communication and keeping users up to date with project information. While primarily used internally by development departments, it offers powerful functionalities that enhance collaboration and efficiency across teams. Overall, Zenhub is valued by users for its ability to seamlessly integrate with Github while providing an array of robust project management features needed for successful implementation.
We used Zenhub to fill the gaps in GitHub's sprint planning and backlog management tools. Zenhub allowed us to better organize our work by adding an extra level of categorization (Epics) with which we could group multiple user stories together. Zenhub allowed us to estimate the work prior to the sprints and better keep track of what was being done and what was left to do. Being able to track dependencies also made it easier for our development teams to stay on top of the work required.
Pros
Scrum boards
Allowing us to track more information in tickets
Sprint planning
Automations and workflows
Cons
At the time, the planning poker functionality lacked flexibility
Automation had some limitations that wouldn't accomodate our workflow
Likelihood to Recommend
The standalone Github project/sprint management is complete garbage when compared to tools like Atlassian Jira. We wanted a cost-effective way of tracking our backlog that was well-connected with our repo (Github). Zenhub seemed to contain all of the features we wanted, plus a few more, and none of the bloat that we didn't want or need. The pricing was very reasonable for our team size when compared to other solutions. Very easy to set up and use as well.
VU
Verified User
Former Employee in Product Management (11-50 employees)
Zenhub would assist us with development tasks for our software programs, additionally we would use it to help track implementation progress and project management. Business problems the product solved included coordinating team members, even customers for tasks that are required to successful capture customer revenue. Ultimately this software helped improve our bottom line leading to positive results.
Pros
organize complex projects
customize workflows
coordinate and communicate with customers around project updates
Cons
Additional communication/collaboration inside the platform would be helpful
Integration with additional systems like Slack would be a plus
sometimes web pages load slowly, but for the most part things are alright
Likelihood to Recommend
Zenhub is incredible for the below areas: Burndown Charts, Release Reports, Velocity Tracking, Control Points Charts, Cumulative Flow Diagrams And if there is a bottleneck in your workflow, ZenHub identifies it. The most important aspect is serving as a collaboration tool for areas that are impeding implementation projects. For example when working with non-standard ERPs and having to document ERP integrations this tool is very helpful
I'm a big fan of this project planning tool. It's not too complicated, but it still offers all the features I need to get my projects organized and on track. It's easy to use, and it makes me feel like I have control over my projects. I don't know how I got by without it!
Pros
- project scheduling and management features
- organizing with teams
- task/project management
Cons
Sometimes, updates to a GitHub project can get lost if they're made through ZenHub. You do need to open the GitHub project occasionally, as you don't have exactly the same ability to modify issues and milestones from within ZenHub.
It's great to be able to see your projects from within ZenHub, but sometimes you'll need to check in on the GitHub project itself, as well.
I've run into some problems with updates getting lost on occasion. I think this happens when you do the update from within ZenHub instead of from GitHub itself. I also don't have quite as much control over my issues or milestones from within ZenHub.
Likelihood to Recommend
I love the flexibility that ZenHub offers. It's so easy to create a project and add issues and milestones. The interface is really clean and simple, and it's nice to be able to see all of my projects in one place. If you use ZenHub for all your projects and are using GitHub for code management, then it's easy to forget that you're not looking at a complete picture of what's going on in your organization.
We use ZenHub for the software team backlogs and sprint items. It allows us to create boards that provide intuitive Kanban/Scrum boards for the team to use during a sprint. It also allows our product owner to groom the backlog, and acts as a great information radiator throughout the organization so stakeholders can see the status at a glance.
Pros
Integration with GitHub.
Great Kanban board functionality.
Cons
A way to display a read-only Kanban/Scrum board for corporate use. Currently, you must have an account to view a board.
While the reporting features are good, it would be great to have some updated Scrum sprint tools to assist with estimating and the like.
Likelihood to Recommend
If you use GitHub/GitHub Projects, then ZenHub integrates perfectly with your projects. It is fantastic for backlog grooming, sprint estimation, and planning. It does require a license to view any board, so when we wanted to make the boards available corporately, we decided to try GloBoards, which does provide the ability to display a read-only board for information radiation purposes. That lasted about a month before the team started complaining and found that the functionality of GloBoards was lacking, thus making the teams less productive. So we went back to ZenHub and have been using it ever since.
ZenHub is used as a project management board for repositories uploaded to GitHub. We work on different projects and keep up to date with information about them all by using this software. Internal use of the development department only.
Pros
Project organization.
Notifications on board changes for better tracking.
Looking at other boards.
Cons
Nothing to add here so far.
Likelihood to Recommend
The reporting function is great. This works great for web developers because you can fill in information as time passes and by creating specific issues you can keep track of any changes in the project, making it perfect for the use of any agile methodology such as Scrum or XP when working with a team.
We use ZenHub in conjunction with Github for the development team, as well for our agile storyboard pipeline tracking. This is used by the IT department and is used for two different development teams. It is helpful in that it coordinates nicely with our source control, and provides a friendly interface for tracking our project stories. Other divisions in our organization use traditional project management software, as they are not following a formal agile methodology. We now successfully visualize our work and and see where each item stands.
Pros
ZenHub has a lot of basic functionality, so that limits the complexity of the application
The ability to provide user defined labels and customize pipelines provides flexibility
The integration with GitHub provides a seamless process
Cons
The software seems to at times have hiccups, and is not accessible
The software sometimes throws errors that it can't do something, or save, and you can't determine why, and typically need to start over
The admin type functions/entering values, codes, projects, releases, those sorts of things, do not seem to be logically located
Likelihood to Recommend
This is great for people that want a 'light' tool that is easy to learn. This is great for a group that does not want to have a costly solution, nor one that would require a full time admin to run. (which seems to be common with the more robust products).
ZenHub is used by our entire IT team, including the product owners and project managers. This incorporates approximately 30 people. IT resource forms the vast majority of this segment of the overall organization. We are able to track our projects in an agile fashion, as well as being integrated with GitHub, which is a great benefit and keeps us all aligned.
Pros
ZenHub continually adds to its reporting suite-- that truly allows you to track forward motion and see what issues may be the cause of any delays.
Both our technical and non-technical staff can understand and use the functionality.
We like the flexibility of being able to provide labels to our stories that can be customized to the way our company does things--- such as knowing if an epic is part of a module or a stream.
We also like the flexibility of the number and labeling of the pipelines--- again, very adaptable to our organization.
The filtering is very useful--- with and/or conditions, and allows people on different projects, doing different functions, an easy way to view what is important to them.
Cons
We would really like the ability to get detailed level reporting by issue.
We would like the ability to better view hierarchically epics and their sub epics.
when creating an issue, it always defaults to a particular repository, which often isnt the one you want. would be better off if you could specify what you want as your default---- or just leave it empty so you have to pick, since it is cumbersome to have to move to the one you really wanted.
A template library for issue content.
Likelihood to Recommend
ZenHub is very well suited for an organization where the project teams run in an agile methodology and environment. ZenHub is also well suited if already using GitHub for source control. ZenHub is not well suited for a waterfall methodology organization, nor if team members are not expected to update their own progress in a tool like this.
Zenhub is used within our development team. I flat out expect it to be acquired by Github at any time because it works so well and integrates so seamlessly into Github using the chrome extension. We use it to easily organize, plan, and run our sprints with our existing github issues and development flow. It's easy enough to use that both the product and engineering teams can use it effectively without training. It's a feature Github should have by default, but doesn't.
Pros
Makes it very easy to get a high-level overview of sprints and sprint progress, creates burndown charts, etc
UX is top notch, almost everything works intuitively
You can create issues and epics right from the interface, basically all github issue functionality is available through zenbhub
Embeds into github using an extension so you don't need an external site
Free starter plan good to test and for small dev teams
Cons
Mobile experience is hard as it's a board layout. Could use a dedicated app.
Has some UX quirks that rear their heads randomly, i.e. can't convert an issue to an epic if you click the wrong button when creating
May have recently moved to all-paid for companies with a 14 day trial, used to be free for small teams
Likelihood to Recommend
If you have more than 2 developers this thing is basically a requirement within github to manage sprints if you use agile methodology. Why use a different website entirely when you can run your entire board right from github itself? I've tried other solutions but basing everything on github issues makes it so no duplicate work has to take place. If the UX quirks and mobile were fixed this would be 10/10 for me!
If you're only one or two devs on a team it may be overkill to use, but if you're going to scale it's better to put the process in early.
