Anonymous UserManufacturing Manager, Capital COE at a manufacturing company
Ptr KiProduct Owner at PerkinElmer, Inc.
We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
"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."
"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."
"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."
"We have been using it because it gives certain abilities in the automotive industry, such as auditing or keeping track of information."
"We found the requirement management and the version control features to be the most useful for our client."
"Complete traceability as per process requirements."
"The tool is quite structured and has a good command set."
"The most valuable feature is traceability starting from the requirements until the end of a project."
"It's a good tool to manage software versions, update the status, and manage tasks."
"I like the Kanban board. It is very useful in terms of seeing who is working on what and what the current status of work is."
"I like the build management features and the integration with Jenkins and many other tools."
"This solution enables us to link all items usefully, in the way we use Agile."
"The most valuable features are the dashboard and task-selection capability."
"The interface is easy to navigate."
"The most valuable feature is the backlog."
"Good branching and labelling features."
"The most valuable feature is simplicity."
"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."
"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."
"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 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."
"To be honest, the third controller system is kind of old. There are lots of transactional changes that have not been implemented in PTC. If you have a larger project, for example, whenever you give bits and need to change 10,000 files you can just commit them. But here the work style is a little more file based, so you'll have to take care of almost all the files individually. It's not a single commit like you do here, but rather you have to allocate time for each component or file that you want to check in or commit. That's a very big issue."
"It's not so customizable. Compared to other tools, defining user stories is a slightly more cumbersome process as an ALM engineer."
"There are not enough reports. People would like to see something similar to what is available in JIRA."
"I would like to see better integration from the architectural side."
"We are unhappy because everything that we needed required customization and this is not a plug-and-play type of solution at all."
"It's not easy to plan on this solution and it's not user-friendly. The interface should be more like a web interface. It's not easy to use."
"In the next release, I would like them to include integration for various projects, similar to what JIRA has, and they could create this feature on the dashboard."
"One of the areas that could be improved is to have an effective full lifecycle management."
"The test management interface is not very handy."
"The interface can be improved and made more user-friendly."
"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 program and portfolio planning facility can be improved."
"Integration from Visual Studio could be improved."
"They should have design patterns in TFS for the development team, and design patterns for the QA."
"In general, Planview's cost structure is reasonable. You get quite a lot of functionality for the license cost that you get."
"The pricing is reasonable at this time."
"TFS is more competitively priced than some other solutions."
"We pay subscription fees on a yearly basis and the price is reasonable."
"I wouldn't say that this tool is cheap or expensive but in the middle."
"We are using the open-source version."
"The price of the solution is cheaper than other competitors and it is a per-user license."
Earn 20 points
Planview LeanKit enables engineering teams across all levels of the organization with a visual work delivery tool to apply Lean management principles to their work, helping them work smarter and deliver faster.
PTC Integrity is ranked 12th in Application Lifecycle Management (ALM) Suites with 6 reviews while TFS is ranked 4th in Application Lifecycle Management (ALM) Suites with 16 reviews. PTC Integrity is rated 6.6, while TFS is rated 7.8. The top reviewer of PTC Integrity writes "Good item management and version control but does not have good performance ". On the other hand, the top reviewer of TFS writes "Good project management features improve discipline and productivity in our application development lifecycle". PTC Integrity is most compared with Jira, Polarion ALM, codeBeamer ALM, Microsoft Azure DevOps and Atlassian ALM, whereas TFS is most compared with Microsoft Azure DevOps, Jira, Rally Software, Micro Focus ALM Quality Center and Tricentis Tosca. See our PTC Integrity 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.