We performed a comparison between Planview AgilePlace and TFS based on real PeerSpot user reviews.
Find out what your peers are saying about Microsoft, Atlassian, Nutanix and others in Application Lifecycle Management (ALM) Suites."It makes work visible, so everybody knows where everything is. It uses Kanban, and that makes work visible."
"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."
"LeanKit is amazing when it comes to getting answers about a given card's status. That's one of the biggest takeaways that we've had. The status is right there on the board. Everybody can see it. You just click on it and it gives you everything that you need to know, especially the comments feature because it gives us a timeline of updates. We use that a lot where we write a comment on the card and then we can see and track progress as we move it across the board."
"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."
"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."
"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."
"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."
"Basically, the capacity to construct various products is something I find handy."
"TFS' most valuable feature is the triage process. It is a robust solution that is easy to use."
"User alerts are very helpful for knowing when work is required."
"The most valuable feature is integration, particularly if you have a .NET application."
"The most valuable feature is the backlog."
"The work item feature is most valuable. It allows us to store all product requirements. We can also link the test cases to those requirements so that we know which feature has already been tested, and which one is waiting for testing. We can also couple the code reviews, unit tests, and automated tests into these requirements. It is reliable. It has all the features and good performance. It also has reporting tools or analysis tools."
"Complete integration with VS IDE and Office tools: This give us a possibility of high-level automation, thus minimizing human error."
"For what I need TFS for, I have never run into any limitation."
"I do not know what it can do in the area of scrum. Maybe it has that functionality. I have never tried to set it up. You think of LeanKit from the perspective of Kanban. I don't know if there is a template for scrum, a scaled agile framework, or any of those scaling frameworks."
"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 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."
"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."
"Being able to track actual time on cards or sprints, instead of using just the planned start and stop date, would also be useful. I would like to see something like JIRA has with actual sprint starts and stops."
"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."
"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."
"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."
"The price could be cheaper."
"The tool needs improvement in stability."
"We encounter issues with backups."
"It would be better if we could bring it out on the cloud."
"I only use 1% of the functionality, so I am not familiar enough to know what needs to be improved."
"They have room for improvement in merging the source code changes for multiple developers across files. It is very good at highlighting the changes that the source code automatically does not know how to handle, but it's not very good at reporting the ones that it did automatically. There are times when we have source code that gets merged, and we lose the changes that we expected to happen. It can get a little confusing at times. They can just do a little bit better on the merging of changes for multiple developers."
"I would like to see the reporting features expanded so that I can see details on the users connected to all of the projects."
"There should be management of the project built-in."
Earn 20 points
Planview AgilePlace is ranked 17th in Application Lifecycle Management (ALM) Suites while TFS is ranked 3rd in Application Lifecycle Management (ALM) Suites with 93 reviews. Planview AgilePlace is rated 9.0, while TFS is rated 8.0. The top reviewer of Planview AgilePlace writes "Gives us visibility into projects and enables users to leave comments on different projects". On the other hand, the top reviewer of TFS writes "It is helpful for scheduled releases and enforcing rules, but it should be better at merging changes for multiple developers and retaining the historical information". Planview AgilePlace is most compared with Jira, Microsoft Azure DevOps, Jira Align, Rally Software and JIRA Portfolio, whereas TFS is most compared with Microsoft Azure DevOps, Jira, Rally Software, Visual Studio Test Professional and OpenText ALM / Quality Center.
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.