We performed a comparison between Jira and Planview AgilePlace based on real PeerSpot user reviews.
Find out in this report how the two Application Lifecycle Management (ALM) Suites solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."JIRA's technical support is absolutely fantabulous. I had used it in the past when I was working at my previous organization. And when we wanted to link it with a framework, they helped us out with the API we were looking for."
"We can integrate a lot of tools with the solution."
"The solution helps a lot with scrums."
"The initial setup was pretty straightforward."
"In terms of scrum teams, I find that usually, the product backlog depends on charts and especially reports like Sprint Reports. I find the reports to be very useful."
"In our organization, we use Jira for project management and usually use the Scrum project type. We might adjust the workflows and stages to better suit our needs, but we mostly use the default functionalities it offers to manage our projects."
"When we run the Jenkins pipeline, the build is already automatically connected to Jira. We've been able to integrate the ecosystem we created using this automation tool."
"The most valuable feature of the solution is the ease of replication of tickets."
"I would say it's highly scalable. LeanKit can scale across the enterprise easily. Every business could probably find a use case for leveraging LeanKit."
"Adoption across stakeholders and visibility have been the biggest success for us with LeanKit."
"It makes work visible, so everybody knows where everything is. It uses Kanban, and that makes work visible."
"My team specifically uses our board for all of our Remedy tickets that come in. We had a card for every ticket that we get, and we're able to add the link to that specific ticket there.If I'm out of office, for example, and someone else needs to work a ticket or someone is being contacted to work on a ticket, I don't have to sign on it. Someone else can easily access that ticket because I put the link in there. It's nice. It has a lot of great functionality in there."
"Every feature is valuable. LeanKit is a Kanban-based tool where you have a visual interface that you can use to create various cards and to create boards to house those cards. You can create a board for managing project work. You can create a board to do PI planning. It is pretty close to the agile way of doing business."
"The transparency that it brings is valuable. I like to look at things from all angles, and sometimes, flip chart paper on a wall and sticky notes are better than something on a screen, but the way they've made it accessible from all points for anyone within an organization is great. As a project management guy, sometimes, you have to force people into new environments where they have to see what you're talking about. Any screen is a barrier, and people got to get into the screen. How do you know they do? You don't necessarily know, but you are getting around that barrier with a countermeasure of making it accessible to as many as possible. So, everyone can jump in there and see everything. It is fully transparent, and I like that. This is one thing that helps."
"People found the ability to set up different lanes and the ability to see where they're within the progress most valuable. They can use different colored cards or sticky notes, and then they can separate out which cards belong to a department or the initiative they're working on. They can filter who's working on it, and I've got good feedback about that."
"The "Blocking" feature has helped our scrum masters track impediments and share them at the program level to stakeholders with accountability and detail so that they understand and the action items which can be noted easily."
"An area for improvement in Jira is that it's not designed for test management. To use it for test management, you need an add-on or several add-ons, e.g. Xray or Zephyr."
"Stability is an area of concern and it needs improvement, otherwise, it's a good product."
"In the way it is deployed, I think Jira is too dependent on the third-party applications that are available in its marketplace. If we could get some of the basic functionalities which are offered by these third-party applications, that would be ideal because each time we need a new functionality, we have to purchase a new plugin as an add-on."
"Nowadays, many organizations are moving toward the Objectives and Key Results (OKR) framework, and this is something that Jira should be able to accommodate."
"Could be more stable with more integrations."
"The part when it comes to the testing area is a bit hard to handle. The screen is too small, you can't really read what you're typing in, and it's only for the testing area. It looks like they have pressed in more than the UI system could handle to display it properly."
"Having more seamless integration with Confluence would really help us track our product management activity and other product details in one place."
"A more organized hierarchy is important. Reporting and JQL create issues for me. They do not completely cover the reporting part that I need to report in terms of my capacity to plan. In the same token, there is no record at this very moment to provide me with one export with epics story points, tasks, or issues and their sub-tasks at the same time."
"There's room for improvement with the Instant Coffee feature. There are other businesses that have been interested in leveraging a virtual whiteboard or sticky note capability and how Instant Coffee was developed has not met the mark."
"We are a 750-employee company, so we got lucky that our board approved the kind of funding we needed for the solution. But, LeanKit probably needs to reduce its pricing."
"The biggest improvement would be the API and data connections and making the data more accessible or quicker to access. One of our team members has brought up actual-time tracking on a card as a potential improvement. They had an interest in knowing how long a specific card had been worked on by a specific user or somebody that was assigned to that card. But there's not really a way for them to start and stop a time that they were actually working on it, except for if we created a different lane and they dragged it into the lane and then stopped using it in the lane."
"Our overall impression of Leankit has been very positive, however, our experience with the JIRA integration into our Leankit boards was much harder than we anticipated and that could be improved by simplifying it somehow."
"They have a feature called Instant Coffee. It was in the beta phase. They released it from beta, and now, it is a legit thing. We were in the pilot here. I liked the idea of Instant Coffee, and I like how it is integrated, to some degree, with LeanKit, but I have two big rocks to throw at them on this. The first one is that Instant Coffee does not save your work very well in terms of saving it in formats that you can then go back and edit as Visio would. It leads to the next point, which is, we're not really clear on what they're trying to do with Instant Coffee. I feel that they're trying not to reinvent Visio, Miro, and other software programs out there that do mapping, visual diagrams, etc. Miro is fantastic in that regard. I gather they're not trying to reinvent Miro, but it sure would be nice if it had more aspects of Miro in it, such as being able to draw arrows and write on them on the top."
"It is a pretty good product. It is really hard to think of things that I'd want to be improved. Sometimes, we use it for project management lessons learned. So, we have three columns, such as Could be Improved, Keep Doing, and Works Really Well. It would be helpful if there was a template set up for something like that because we code different cards based on the category. For example, if something belongs to the Could be Improved category, we may have those cards as yellow, but then I have to change the color of them and put a header. It is not as smooth, but it still works fine. To be honest, I don't have a lot of complaints about it."
"The integration with the Enterprise One product is probably an area for improvement. It's not really broken. It's just that it is such a handy tool and a great way to visually manage things. There is a very limited hookup/integration between Enterprise One, which is the master Planview tool, and LeanKit. While they are looking at this on their roadmap, it definitely needs to happen. There is a lot of opportunity there."
"Within the current features, if they can give some ability to show more icons on the card, it would be helpful. It would help us in showing more data on the cards."
Earn 20 points
Jira is ranked 1st in Application Lifecycle Management (ALM) Suites with 266 reviews while Planview AgilePlace is ranked 17th in Application Lifecycle Management (ALM) Suites. Jira is rated 8.2, while Planview AgilePlace is rated 9.0. The top reviewer of Jira writes "A great centralized tool that has a good agile framework and is useful for day-to-day planning, task management, and work log efficacy". On the other hand, the top reviewer of Planview AgilePlace writes "Gives us visibility into projects and enables users to leave comments on different projects". Jira is most compared with Microsoft Azure DevOps, IBM Rational DOORS, OpenText ALM Octane, Rally Software and IBM Engineering Workflow Management, whereas Planview AgilePlace is most compared with Microsoft Azure DevOps, Jira Align, Rally Software and Digital.ai Agility. See our Jira vs. Planview AgilePlace report.
See our list of best Application Lifecycle Management (ALM) Suites vendors.
We monitor all Application Lifecycle Management (ALM) Suites reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.