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
Planview Portfolios
Score 8.4 out of 10
N/A
Planview Portfolios is an end-to-end project portfolio management and enterprise architecture management tool. It includes two components: Portfolio and Resource Management and Capability and Technology Management. The platform is available as a cloud-based or on-premise service.
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
I work as a Hospital Manager and in our hospital we need various equipment and advanced machines that can diagnose the best and give us the best results so that we can analyse the patient's best possible condition. Getting new machines and types of equipment is not an easy task we need so many planning the funds for the projects and implementation of those machines can become challenging part if we don't have a proper roadmap of resource management, funds, vendors suppliers, etc. Here Planview Portfolio smartly computes the all data counts all the variables and gives us the best roadmap to follow it is very useful to get crucial projects in organizations. If the organization doesn't have multiple projects or they work in a monotonous way then this tool might not be the best option for them.
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.
Capture potential opportunities using the Requests Module and analyze and rank these opportunities via lifecycles and promote (dispatch) approved opportunities into Projects. Information captured during the request process automatically get transferred to projects.
Robust schedule management; time reporting; resource management and financial planning and management
Risk and Issue management controlled via robust lifecycles.
Extensive reporting capabilities via SSRS and Power BI Dashboards and delivered to users via tiles in Project and Portfolio views.
this is the area I can see Planview Portfolios is very much lagging behind. If you see Atlassian, they are having a robust API information and using that we can securely access the necessary information based on the role. I think a similar kind of approach need to done in Planview Portfolios as well.
User Information and Resource information is separate. Expecting that, during the User creation, when a resource is linked, automatically all the basic fields should be populated with the values, also if a person is having an User account there is no way for that person to know that what User role that he/she is having. Also none of the reports covering that details.
Automation - It's mentioned using the UiPath some of the Automation has been done in the User creation but don't find any necessary document for better understanding.
We have been a Planview customer since 1999 and have seen it grow and mature as a tool. We have looked at other tools and have found that PV continues to meet our needs and is easy for our resources to use. They work to stay up on the project management industry and the direction it is going, keep on on current technology so that we can work more effectively, provide excellent customer support and have great pricing for what they offer. We can purchase only the modules we need versus buying a tool where we would only use a portion of the functionality.
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.
I feel it is very difficult to use, and very limiting and of over complicated in it's basic project management basic functions. In my opinion it is over engineered to the point of un-useful
We are long time Planview users and its availability is only limited to our internal SLAs for nightly backups. I have never experienced any unexpected or prolonged software downtime from Planview itself.
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.
Consultants are knowledgeable and friendly; it is easy to build relationships with the support people you work with and they learn how best to help you. The vendor is continuously looking for honest feedback about their tool and they use that information to design their product roadmaps
Always have a pre-implementation meeting or conference call with Planview to ensure all are on the same page, disclosure of all and any customization (including reports) and plan for support after implementation of a specified amount of time with the assigned implementation resource. And document everything
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.
Odoo, like this platform, has allowed us to efficiently organize our projects so that they can be prioritized by importance, to know which is the most urgent, in addition, it has also allowed us to assign work in an organized way among our collaborators, and their reports have allowed us to improve.
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 has improved Resource Management. We now consistently represent resource available-to-promise against operational commitments, other projects, q-end commitments, vacations, etc.
It has improved our quality of forecasting. We now model project changes and future requests against available time and resources ("what-if" scenarios).
It has improved our strategic focus. We now manage our projects from a program/portfolio point of view to ensure we are resourcing company strategic initiatives.
