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
Azure DevOps Services
Score 8.5 out of 10
N/A
Azure DevOps (formerly VSTS, Microsoft Visual Studio Team System) is an agile development product that is an extension of the Microsoft Visual Studio architecture. Azure DevOps includes software development, collaboration, and reporting capabilities.
$2
per GB (first 2GB free)
Pricing
Aha! Roadmaps
Azure DevOps Services
Editions & Modules
Premium
$59
per month per user
Enterprise
$99
per month workspace owner or contributor
Enterprise+
$149
per month workspace owner or contributor
Azure Artifacts
$2
per GB (first 2GB free)
Basic Plan
$6
per user per month (first 5 users free)
Azure Pipelines - Self-Hosted
$15
per extra parallel job (1 free parallel job with unlimited minutes)
Azure Pipelines - Microsoft Hosted
$40
per parallel job (1,800 minutes free with 1 free parallel job)
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.
We are moving away from VSTS to Version One since Version One has a better end to end workflow for a product based team (where product and development work very closely together and need to access the same data and communicate in an efficient manner.)
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
ADO is well suited for the visibility of day-to-day tasks and responsibilities as well as things such as Features, user stories, etc. Off the top of my head, I can't think of any scenario where it might not be well suited, as you can customize ADO to your liking to a degree.
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.
Flexible Requirements Hierarchy Management: AZDO makes it easy to track items such as features or epics as a flat list, or as a hierarchy in which you can track the parent-child relationship.
Fast Data Entry: AZDO was designed to facilitate quick data entry to capture work items quickly, while still enabling detailed capture of acceptance criteria and item properties.
Excel Integration: AZDO stands out for its integration with MS Excel, which enables quick updates for bulk items.
I don't think our organization will stray from using VSTS/TFS as we are now looking to upgrade to the 2012 version. Since our business is software development and we want to meet the requirements of CMMI to deliver consistent and high quality software, this SDLC management tool is here to stay. In addition, our company uses a lot of Microsoft products, such as Office 365, Asp.net, etc, and since VSTS/TFS has proved itself invaluable to our own processes and is within the Microsoft family of products, we will continue to use VSTS/TFS for a long, long time.
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.
Azure DevOps is a powerful, complex cloud application. As such there are a number of things it does great and something where there is room for improvement. One of those areas would be in usability. In my opinion it relies too much on search. There is no easy way to view all projects or to group them in a logical way. You need to search for everything.
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.
When we've had issues, both Microsoft support and the user community have been very responsive. DevOps has an active developer community and frankly, you can find most of your questions already asked and answered there. Microsoft also does a better job than most software vendors I've worked with creating detailed and frequently updated documentation.
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.
Microsoft Planner is used by project managers and IT service managers across our organization for task tracking and running their team meetings. Azure DevOps works better than Planner for software development teams but might possibly be too complex for non-software teams or more business-focused projects. We also use ServiceNow for IT service management and this tool provides better analysis and tracking of IT incidents, as Azure DevOps is more suited to development and project work for dev teams.
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.
