We performed a comparison between Alfabet IT Planning & Portfolio Management, Basecamp, and Jira based on real PeerSpot user reviews.
Find out what your peers are saying about monday.com, Broadcom, ServiceNow and others in Project Portfolio Management."The dashboard is the most valuable feature."
"The ease of use is valuable."
"The ability to network informally is great for communicating with colleagues."
"Overall, the solution is very nice and has a variety of great features."
"The most valuable feature is the Burndown Chart to see work that is outstanding."
"This is a user friendly solution."
"We have the best community to support any problems that we have."
"It's a Scrum tool, so it's very easy to use."
"The most valuable feature is the full integration between Work management, Source code management, and Test Automation."
"You no longer need to email people. You can mention them right in Jira and have conversations there."
"It's easy to escalate the issues to the product development team."
"The user-experience, enhanced performance, and in-hand governance can be improved."
"The solution could be more user-friendly."
"The product isn't easy to use. It's not very intuitive."
"Jira has recently updated their UI, but more can be done to make it even better."
"I want the tool to integrate connectors."
"For a non-technical person to use, Jira is not intuitive."
"There are some features and reports we need that are not there. For example, if I have to find out the capacity of the current sprint by user and compare it with the previous sprint, that visibility isn't there."
"I struggle with Epics, how they are implemented in JIRA, because they don't work like any other Story, I see a list of Epics, but although I can order them, there are some mismatches with how the Epics are used compared to what Scrum expects, or what Story mapping expects an Epic to be."
"The solution could be more user-friendly."
"Stability is an area of concern and it needs improvement, otherwise, it's a good product."
"It is not capturing the number of hours for which each person has worked on certain things. We use many add-ons to let resources enter the time in the user story itself. We use an add-on called Tempo, but it is kind of a lousy add-on. It is not straightforward. Rather than helping us, it creates a lot of confusion. So, instead of looking out for the additional add-on, I would prefer to have the timesheet entered as a part of Jira itself. They are anyways capturing every information they could for each user story, and then we are able to break down all the task lists. For each task, we're also assigning a resource. So, while we're doing it, why can't they allow the users to enter the time that can be created as a report? Right now, we need to acquire the add-on, and the add-on is not great. It is not helping. The add-on is also not free."
More Alfabet IT Planning & Portfolio Management Pricing and Cost Advice →
