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
IBM Engineering Lifecycle Management
Score 5.3 out of 10
N/A
IBM Engineering Lifecycle Management (ELM) is an end-to-end engineering solution used to manage system requirements to design, workflow, and test management, extending the functionality of ALM tools for better complex-systems development.
It is great for organizations that want to ensure that the work they focus on is the work that will have the most impact on value and drive them toward their strategic objectives. I consider it to be a real Product Management tool. If all you are looking for is a tool to hold your product backlog or collect customer feedback, then Aha! is probably going to be overkill for your needs
The software is robust enough to handle highly complex software development or other product development and can be used well beyond the range to do what a client needs. However, because of the inability to hold its users to proper best practices, things can get wildly out of hand and cascade over the years, creating unnecessary technical debt. The system has a lot of usable features, but they don't funnel users toward the correct processes and practices.
Aha! is an all around product management suite. It is great for breaking product plans into initiatives, features, and user stories. This helps the organization understand the product plan and what is driving individual work items. Unlike Jira and project management tools, it helps you prioritize by major themes, features, and releases. Once you start to use it, you can't go back to a project management tool because the views for organizing and prioritizing features just isn't there.
Aha! also excels at idea management. You can create a portal for users to submit ideas and manage them through a workflow. Users can submit ideas through a variety of channels, including email, ZenDesk, and SalesForce. You can even attach account values to an idea submitted through SalesForce, though the UI in SalesForce is a little kludgy. This is a great feature for those that have the capacity to manage feedback this way, but be aware that it takes time to manage.
Aha! works pretty well with Jira so that project managers can have their backlog that is understandable to the business and engineering can break down those work items however they want.
Aha! also has a lot of useful integrations: Slack, ZenDesk, Zapier, etc. It also integrates with every major software project management tool on the market: Jira, Pivotal, Rally, Redmine, and TFS.
I feel like it is too heavy sometimes and updating is not very straight forward. For example, if I want to change an incident ticket (IN) to a service request (SR) and add some comment for the change, I have to first change the IN to SR, then click refresh which takes a few seconds, then add a comment. If I forget the refresh step, my comment will be discarded without warning like my ticket is not in the latest status. This also happens when somebody else changes the ticket during my edit as I can not lock the ticket exclusively.
At the moment we are required by contract to continue to use the IBM DOORS software for our current client. Given that it can be expensive, if we were to use it after our current client's needs were met, we would have to secure other projects in order to justify the continued use of the software.
I think Aha! works really in general, it offers a very comprehensive and well-structured platform that supports strategic product management at scale. Although there is a learning curve for new users and a few areas to be improved. Overall, it is highly usable for experienced product teams who need a robust roadmap tool.
The UI is terrible and not intuitive. Users need training in order to complete tasks. Much like SAP, it's not the clearest tool. The tracing feature is especially complicated because you must write the scripts yourself. There is a learning curve. Also, even the setup, installation, and logging in each time takes a considerable amount of time.
We've always had excellent support whenever we need help from the company or need questions answered regarding the setup and installation of the product. Tickets are answered in a timely fashion and there's minimal back and forth to get issues resolved, which are rare.
It does a basic job and has the potential to complete some robust reporting tasks, however, it really is a clunky piece of software with a terrible user interface that makes using it routinely quite unpleasant. Many of our legacy and maintenance projects still use DOORS but our department and company use many alternatives and are looking for better tools.
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 every feature in Aha! that we were looking for.
It was easier to do all the change management-related activities, even configurations were handled very effectively. New process definitions and initiatives made it easier for better project deliverables. Effective resource allocations and better reporting and defect management. The overall cost of the tool is great too and well within budget.
It has helped us improve our product lifecycle communication. We have less wasted time spent figuring out where the project is and what it's waiting on. This has helped departments further down the project better use their time so they're already aligned with what's happening rather than waiting for a handoff.
Aha! has helped include our customers more in our product planning and especially in our bug fixes and new feature roadmaps.
Aha! has improved our strategy meetings or roundup discussions by storing everything in one place. They're shorter and more focused.
It's part of CLM suite so it can be used to manage the whole lifecycle with tight integration with development module (Rational Team Concert) and quality module (Rational Quality Manager).
Comprehensive reports and dashboards provide better visibility.
