Anonymous UserManufacturing Manager, Capital COE at a manufacturing company
Nitin KaushikQuality Assurance at Varroc Lighting System
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."
"All of the features work together to provide a powerful holistic solution - from the dashboard all the way through to security."
"Work distribution among team members and accountability for completion with a clearer picture."
"Traceability reporting is inbuilt and includes all your requirements."
"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."
"Some administrative tasks are difficult to perform. These could be simplified."
"Teams need clearer pictures of resource availability in charts and dashboards along with plans."
"The solution is very heavily vendor dependent."
"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."
"Licensing: The solution cost is high and should be brought down to increase competition."
"It's an expensive investment to make, so the decision should be driven on individual requirements."
"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."
"We pay for the license yearly."
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.
IBM Engineering Workflow Management manages plans, tasks, the project status and acts as the critical link between required and delivered work. It provides flexibility to adapt to any process, which enables companies to adopt faster release cycles and manage dependencies across both small and complex development projects. This solution offers no-charge server software and flexible pricing models. It becomes a complete IBM Engineering Lifecycle Management solution—when purchased as a set of seamlessly integrated tools: IBM Engineering Workflow Management, IBM Engineering Test Management, and IBM Engineering Requirements Management DOORS Next.
IBM Engineering Workflow Management is ranked 11th in Enterprise Agile Planning Tools with 3 reviews while TFS is ranked 2nd in Test Management Tools with 17 reviews. IBM Engineering Workflow Management is rated 7.0, while TFS is rated 7.8. The top reviewer of IBM Engineering Workflow Management writes "Great inbuilt traceability reporting; unfortunately, the solution is heavily vendor dependent". On the other hand, the top reviewer of TFS writes "Good project management features improve discipline and productivity in our application development lifecycle". IBM Engineering Workflow Management is most compared with Jira, Microsoft Azure DevOps, CA Endevor Software Change Manager, codeBeamer ALM and IBM Rational ClearCase, whereas TFS is most compared with Microsoft Azure DevOps, Jira, Rally Software, Micro Focus ALM Quality Center and Visual Studio Test Professional. See our IBM Engineering Workflow Management vs. TFS report.
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.