As a small PM team where we do not yet use any portfolio tool except various spreadsheets and documents, and where all of our teams are using Jira backlogs, we have been seriously investigation Jira Portfolio and found it very interesting and most probably our prefered tool in the near future.
We more recently discovered Aha! and realised it was very good as well and very much equivalent but we were wondering for the challenge on the integration level in both direction with the Jiras backlogs.
I found several discussion here and about the integration learning, steps etc ... several topics on the Aha! usage, but none really on the Jira Portfolio and less trying to compare the 2 together. I found this Reddit topic on it which again is very much on the integration aspects.
At the end of the day, I'm not searching for a revolution on the PM side, since I'm sure we'll need many doc still in future, but my main goal are to:
- manage new ideas, turn some into a product roadmap and to priorities those roadmap
- get those roadmaps easy to be found & understood by the for stakeholders
- get those release into the engineering backlog and get new items from the backlog up into the roadmap as well
- get the visibility into the teams’ progress to keep our plans up-to-date and play some scenarios
I'm pretty sure that I might get some users for Aha: and some for the Portfolio, but I wanted to see still if there would be experience to collect.
I guess that there are also many other tools that are more Project or Program Management tools and less Portfolio ones.
Thank you in advance.
I just completed a project integrating Aha! with JIRA and HipChat for a 35 person Product team. The integration was very easy and the process to onboard the team was easy. I had several meetings with the PM's Dev counterpart to help them see what the PM's were doing, why and how it would indirectly help them.
We also used this project as a catalyst for standardizing some high level processes for all of Product.
If you think it would help, I'm happy to jump on a call or Hangout with you to discuss this integration further.
All the best,
We have been using Jira for many years and have tried to integrate Aha! with Jira. The bottom line is that it has been a failure. Updates in Jira don't get passed back to Aha! and Aha! overwrites the latest information in Jira causing problems for the developers. Status is not being sent back to Aha!
The product managers were trying to use Aha! while the developers work strictly in Jira. We have been using Aha! for over a year.
One of the dev managers evaluated Portfolio. I don't really prefer Portfolio over Aha! but I can see why the developers like Portfolio. It is a very good tool to clearly understand the team velocity and capacity for each release. Not so much for roadmapping.
Now I'm the only product manager that uses Aha! while the rest are using Portfolio. Unfortunately the Jira integration with Aha! is so poor that I have to periodically perform a manual update to get the information sync'ed between the two. The reason I continue to use Aha! is for the roadmap tools. Portfolio feels more like a project planning tool instead of a product planning tool.
I really wish that Aha! would work to fix the integration issues with Jira. If you are using Jira, then I would recommend going with Portfolio that is designed as part of Jira. If you can get the teams to use Aha! then I would recommend Aha!