"Jira Align helps us manage communication and tasks for a variety of teams without overlap."
"The most valuable features are the ability to customize the entries and to update them quickly. Since the new version they released, we started utilizing the customization features to create specific codes and symbols for our teams that were not available before. For example, in team A each person had their own symbols and we had our own demarcation. When our project or task was completed, we had a code that we could enter online that let the main project managers know that it was time to remove it."
"Some of the most valuable features are the configurations and dashboards."
"The most valuable feature is that engineers can access the Jira database and just search for the tasks that are assigned to them. They can then update the status on their own in those records that are assigned to them."
"Velocity and reporting provide good visibility, burndown charts, and particularly velocity measurement."
"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."
"Adoption across stakeholders and visibility have been the biggest success for us with LeanKit."
"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."
"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."
"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 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."
"The customizations on the board, including the various lanes, colors of cards, and visual icons on the cards, are all very helpful to us."
"We use the board and card hierarchies in terms of sprints so that we can see if we have cross-functional teams that are working on the same projects together, especially when projects have dependencies. The parent-child relationship within cards is really nice so that we can see what kind of dependencies there are when we're trying to get projects finished."
"The workflows are scalable from portfolio to individual level but can sometimes be complex to navigate."
"Lacks sufficient reporting capabilities."
"There is no linkage between the Jira records and the overarching schedule. We maintain the overarching schedule in Microsoft Project, and there is no linkage back and forth with the Jira tasks. They are independent of each other."
"Deployment was very complex."
"One of the biggest issues I found in the new version was once we clicked on one of the tasks that were specifically for our group and went to look at the other portfolios in other areas we had to browse all the way back to the beginning. If you click the back button, it would not work, it stayed the same place. Additionally, if you click on page B, but then you wanted to go back to page A it would not go back to page A. You would have to browse back to the portfolio and then find your group again and open it. This was the only issue that I had with it and I am not sure if it is a Jira issue or it was because of the way the site was laid out."
"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."
"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."
"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."
"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 ability to report on customizable fields and third-party extensions needs improvement. I'd like to see more of those being able to be used. I don't know how that works for Planview, but just getting a little bit more added there would be nice."
"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."
"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 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."
Jira Align is ranked 7th in Enterprise Agile Planning Tools with 5 reviews while Planview LeanKit is ranked 3rd in Enterprise Agile Planning Tools with 11 reviews. Jira Align is rated 7.8, while Planview LeanKit is rated 9.0. The top reviewer of Jira Align writes "An easy learning curve with great integrations; reporting provides good visibility". On the other hand, the top reviewer of Planview LeanKit writes "Scalable, flexible, and easy to use". Jira Align is most compared with Microsoft Azure DevOps, ServiceNow IT Business Management, Targetprocess, ServiceNow DevOps and Plutora, whereas Planview LeanKit is most compared with Microsoft Azure DevOps, Rally Software, AgileCraft, Targetprocess and TFS. See our Jira Align vs. Planview LeanKit report.
See our list of best Enterprise Agile Planning Tools vendors.
We monitor all Enterprise Agile Planning Tools 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.
