Aha! Roadmaps is used to set strategy, prioritize features, and share visual plans. It includes Aha! Ideas Essentials for crowdsourcing feedback. For an integrated product development approach, Aha! Roadmaps and Aha! Develop can be used together. The software is available with a 30-day trial.
$59
per month per user
Zenhub
Score 8.0 out of 10
N/A
ZenHub is a project management solution that runs native within GitHub with collaboration boards, file sharing, and pipeline selection.
$0
Pricing
Aha! Roadmaps
Zenhub
Editions & Modules
Premium
$59
per month per user
Enterprise
$99
per month workspace owner or contributor
Enterprise+
$149
per month workspace owner or contributor
Free
$0
Growth
$8.33
per month per user
Growth
$8.33
per month per user
Enterprise
Contact us
Enterprise
Contact us
Offerings
Pricing Offerings
Aha! Roadmaps
Zenhub
Free Trial
Yes
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
Optional
No setup fee
Additional Details
Startup pack available for early stage companies.
The listed prices are per user, per month when billed annually.
More Pricing Information
Community Pulse
Aha! Roadmaps
Zenhub
Considered Both Products
Aha! Roadmaps
Verified User
Anonymous
Chose Aha! Roadmaps
ProductBoard was used in the organization when I arrived, but after assessing ProductBoard, I felt it was too lightweight for our ambitious product goals. It's also critical, especially in a startup, that we focus our limited capacity on the work that matters most. Aha! far and …
Compared to some other types of software we've tested or use in other areas of the company Aha! has a better user interface, has more customization ability and grows with the company and the work we're doing.
I initially tried to do this using Notion but without an API to integrate it is all very manually driven when any updates are made in ADO, I would have to hunt it out.
I've worked with other homemade tools and Jira, Confluence as well. They are more tailored for the developers' community than Product and Program managers.
In terms of outright features, a lot of roadmapping tools have the same feature set. We chose Aha! based on look-and-feel, the easy learning curve, and the reviews it has. Between collaboration, milestone tracking, comment threads, and content importing and exporting, we had …
Jira is centered around product development, whereas Aha! is centered around product management and road-mapping. Both allow for planning and tracking, but Aha! is more user-friendly.
Aha has more features continually being released as a Product Management tool. In comparison to ProductPlan, Aha has more complex features and increased support for getting organizations up and running on the platform. They also provide migration tools to determine what data …
Jira has a lot more bells and whistles. It was easier to see how different teams across the (larger) company were prioritizing their own work against all of the incoming requests, and to see how those ideas mapped across the current and next springs. However, it was necessary …
In terms of product road-mapping, Aha! beats its competitors upfront. Aha! is one of the best tool to visualize your product strategy. However, JIRA in terms of PRDs, gives a complete environment in its own. Aha! is for product managers only. If Tech needs to be involved, JIRA …
Aha! definitely does more than either Pivotal Tracker or JIRA. We still use JIRA to track tasks by department, but for strategy everything is in Aha! and aligns all of our other project/task trackers including integrating with Salesforce so we're able to work within every …
We selected Aha over the other options as our specific goal and need was to align as a Product Management team across all our lines of business. While other products did well, the customized abilities of Aha, price points, and Atlassian integration tools made it a clear choice.
Aha! is a better fit for the specific type of strategic planning that I do. The other tools are more intended for other grains of planning and/or execution.
Aha! is completely different compared to the other products I've evaluated. I would compare Aha! to Atlassian/Jira. It's great for agile teams to do weekly sprints and breakdown large features/product upgrades into individual tasks.
Aha! is slightly more complex and nuanced than Trello, which is nice. Trello feels like a digital sticky note system sometimes. It's more straightforward in UI and collaboration than Workfront or Workamajig without all the extra (seemingly unnecessary) features, like scoping …
Wizeline is an up-and-comer in this space. At the time we considered them, the solution was not robust enough to manage a large backlog or multiple products with a Jira integration. They are adding features rapidly, though, and every release is very robust.
Zenhub is purpose built for Github users and provides just the tools you need to run Agile sprints without any extra complexity or fluff. Azure is a much more "enterprise" solution in which you drown in all of the available options, very similar story with Jira (pricing is also …
Zenhub partners with Github and it's nice to use both in tandem, ultimately Zenhub has the project management capabilities we were looking for. Additionally Zenhub has a really user-friendly platform that is intuitive and not much training was required for any of the team …
The only other program we tried that had somewhat seamless integration with our GitHub projects is GitKraken's Globoards. Globoards has a long way to go to compete, though it does have a read-only option for boards so it can be displayed corporately as an information radiator …
I have used Workfront in the past, which in my experience, is best with a traditional waterfall methodology, similar to Microsoft Project and the other more traditional project management software projects. ZenHub is truly designed around the agile methodology. Other products …
Way better than competition if you use github because it seamlessly integrates without doing anything. You don't need to duplicate your issues, etc. As long as your devs already use github and github issues this will be a no brainer and simple to implement. With JIRA or Trello …
Aha! is the all around product management tool. You need something once you build out a product management role and grow beyond a small scrum team with one or two products. JIRA, Pivotal, and project management tools don't cut it for aligning [engineering] with product initiatives once the backlog starts to scale.
On the other hand, there are several unfinished features that my peers all admit to having to work around: Capacity Planning, Salesforce Integration, Roadmap Display Flexibility, User Feedback, etc. This year has been all about reporting in terms of feature releases. As Aha! grows, they will fill in these other areas, so stay tuned.
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
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.
Notes - There's not a great place to leave lots of notes or instructions, almost like a Confluence page. Although not required, it would be nice to have this built in.
Learning curve - As with most new tools, there's a bit of a learning curve to become proficient.
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.
If you have the time and resources there really isn't anything you can't get Aha! to do for you in regards to managing workflow and releases. The Prioritization features are top of its class, the dashboards are getting better and better every day and the team all seem to really enjoy using it to manage their workloads.
Once it's up and running it's easy to use. It needs a little consideration to get set up perfectly for your own needs, but that is the same for any feature-rich software.
When we signed up for Aha!, we were assigned an Aha! team members to help us with training/questions. The meeting was set weekly, and it exponentially helped with our familiarity with Aha! Support is beneficial and has a lot of experience working with product teams.
Support is good, but quite honestly, I haven't needed any support since 2015. As I remember, I was required to open a ticket and had to wait a few days for resolution. I give it a rating of 8 because of the lag in getting a solid resolution, but it was resolved adequately.
productboard was used in the organization when I arrived, but after assessing productboard, I felt it was too lightweight for our ambitious product goals. It's also critical, especially in a startup, that we focus our limited capacity on the work that matters most. Aha! far and away had superior capabilities in defining strategy directly in the product and associating all of our work to the strategy. Aha! is a serious product management tool and I found productboard to be more of a simple backlog management tool.
Way better than competition if you use github because it seamlessly integrates without doing anything. You don't need to duplicate your issues, etc. As long as your devs already use github and github issues this will be a no brainer and simple to implement. With JIRA or Trello we were doing everything twice, things got dropped, etc.