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
FogBugz
Score 2.6 out of 10
N/A
A software project management system used to plan, track and release great software with this lightweight and customizable system that integrates into any project management workflow. FogBugz is designed for software development teams and includes all the project management tools developers need straight out of the box. Users can: Track projects from start to finish - With tasks and subtasks for each case with required details and track them to ensure…
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.
Fogbugz is great for case-and-task based businesses. If your business has hundreds of weekly anticipated tasks that exist, such as processes to get files converted, Fogbugz can manage these processes very well. For our team, we knew each week that we would have about 500 tasks or orders to get processed. Fogbugz helped us break down these projects, get them assigned evenly throughout the team, and easily see who is working on what task. FogBugz is also good for tracking unanticipated tasks like bugs, making notes, flowcharts, and categorizing if the problem is a bug, feature request, etc. For us, it was just the best at nailing down those anticipated tasks.
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.
Workflow capability is very limited to the original implementation, could use a refresh and extension of the capabilities
UI/UX needs improvement. This was in the works prior to purchase by DevFactory, and has taken a back seat to backend improvements that rightfully needed to be fixed first.
Pricing model doesn't fit our usage very well, so we're paying for full-featured users for everyone even though the majority of Users only need to submit Cases and modify the Wikis, and our small percentage of Users are in Dev and need all features.
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.
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.
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.
FogBugz is made for the Developers who actually use it every day, while JIRA is made for the C-Suite who oversees them but has little idea of the finer points of daily dev tasks. In reality, most don't fit into the mold of JIRA tickets, and the summarized information that C-Suite is reviewing is incomplete or skewed. There is also an outstanding issue since 2004 that JIRA refuses to implement despite wide user support, the merging of tickets. You can see the open ticket with the JIRA team here: https://jira.atlassian.com/browse/JRACLOUD-3592
