We performed a comparison between Planview AgilePlace and TFS 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."It makes work visible, so everybody knows where everything is. It uses Kanban, and that makes work visible."
"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."
"Using the tool seems to save time versus trying to do things in a regular manner. It is highly collaborative; everybody can see things in one place. It is a highly functional, but pretty simple tool. That is hard to find: A tool that has a lot of functions, but is also simple."
"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."
"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."
"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 "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."
"The most valuable feature is the backlog."
"The most valuable feature is simplicity."
"Microsoft's technical team is supportive."
"Build definitions and releases within the product. allow us to put our latest applications in the field."
"Some of the valuable features are version control and the ability to create different collections in terms of segregating the authorization for teams who connect to small projects."
"I have found almost all of the features valuable because it integrates well with your Microsoft products. If a client is using the entire Microsoft platform, then TFS would be definitely preferable. It integrates with the digital studio development environment as well."
"We use TFS for forecast management."
"Complete integration with VS IDE and Office tools: This give us a possibility of high-level automation, thus minimizing human error."
"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."
"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."
"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."
"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."
"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."
"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."
"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."
"We are also using Microsoft Teams. The two products function separately. There is not enough collaboration between Microsoft Teams and TFS."
"The usability of TFS is not that great."
"I would like to see the reporting features expanded so that I can see details on the users connected to all of the projects."
"The execution of test cases could stand improvement."
"The project management side should be addressed and the project and release planning should be somewhat extended."
"Not all of the functionality, which is exposed by the command line interface (tf.exe) is available in the Visual Studio GUI."
"The solution should have better dashboards."
"They should have design patterns in TFS for the development team, and design patterns for the QA."
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 and Rally Software, whereas TFS is most compared with Microsoft Azure DevOps, Jira, Rally Software, TestRail and OpenText ALM / Quality Center. See our Planview AgilePlace vs. TFS 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.