Kanban Tool vs. Planview PPM Pro

Kanban is well suited for a fast-paced working environment for larger teams who want continuous communication with users. Kanban is good for rapid development and daily meetings for updates and statuses. Kanban is less suited for smaller teams or groups who don't require collaboration and constant communication with involved users. Kanban is time-consuming and it takes additional effort outside of your regular work to maintain and manage the tool.

Incentivized

PPMPro is well suited for tracking new product introduction projects, as well as process changes. It serves to reliably track ongoing action items, issues, resource allocations for projects. Areas where PPMPro is less appropriate for use: Project to project dependencies, automating action item notifications on multiple platforms, integrations of PPMPro into other platforms PMO typically uses (like MS Projects, Teams, ppt, etc)

• It provides a good basic overview of where tasks are on a timeline (particularly helpful for a pull-based approach).
• It provides a good collaborative space to have multiple folks commenting on multiple tasks.
• It does a good job of managing very basic visual elements of an agile development cycle.

Incentivized

• New request workflow/kanban board helps visualize where new requests are in the process of the quote to cash/request to completion
• The time tracking tool is tied directly to project tasks for seamless integration of time tracking, estimates, and actuals
• The reporting capabilities and ease of use has allowed us visibility to data that we never had before
• The tool is easily configurable by Administrators. We can add fields, change reports, add new dashboards within hours vs. days of trying to track things manually

Incentivized

• Kanban does not show the task or story clearly. You have to open the project separately to view the details of the project.
• Kanban gives a higher level project management view but it lacks customization and personal settings features.
• I would like to see Kanban provide mobile access to their tool, data, and board. This would be very useful for all companies and provide an increase in efficiency and productivity.

Incentivized

• The base API is not a REST based interface and is difficult to use for integration with other systems in the enterprise.
• The UI for the maintenance of the task schedule for projects can be a bit cumbersome , although the spreadsheet style editor helps somewhat. The Gantt view is not interactive.
• The workflow engine is designed only for initial project intake, and does not allow for an integration of the work flow with the project from start to end, so it can't be used for routing artifacts like change requests, ancillary project approvals, etc.

Incentivized

We are more likely than not to renew our use of Kanban. Even with its limits, it still is a good product that fulfills our needs.

Incentivized

Because I never evaluated other tools, I would be open to considering others. Given our establishment with Innotas and the value it has provided us, separating from it would cause some organizational discomfort. However, if a tool existed with a more intuitive interface for manipulating the data and factors of projects and resources, I would be very interested.

Incentivized

Again, this is a strong tool for software teams using Agile that are distributed across multiple geographies. It can be good for co-located teams too, but there are better platforms on the market like JIRA that provide a more built-out story.

Incentivized

Still cumbersome in some areas. It really depends on the individual. I've seen very smart developers who get lost just managing tasks and logging time. Whereas others use the system with ease

Innotas is very rarely down if at all.

interface and response is sluggish

This is the best tool I had a chance to work with- since I started to use it I saved a lot of time and I made my work go smoothly.

Their ability to assist and answer questions when needed is incredible. They create innovative ways to share information and help customers trouble shoot. I didn't give it a ten because I believe they could do a better job of personally reaching out to customers and providing improvement guidance based on where the customer is at and their needs at the time

Tim Srjezter was an excellent trainer.

It's been since 2009. A lot has changed. We have not grown as much as we could have because of executive backing.

Incentivized

We've only tried JIRA Agile and KanbanFlow before. Kanban Tool was the one that our team actually liked and enjoyed working with. Also - it's been much easier to get started with and to understand than some of the other two (JIRA in particular). Although JIRA has many more features that we would have possibly used, the user feedback on it was so poor we were afraid that the negativity would create time wasted and less "job satisfaction" amongst the team.

Microsoft Project does not integrate the data or provide meaningful dashboards. We needed a tool that could manage a portfolio of projects versus just a single project view. In addition we needed a tool to track financials and internal effort all integrated into one product. Planview PPM Pro addressed all of our needs

• Better communication and organization of ongoing projects.
• We are a very small team, with many areas to work on. Having everything in one system gives us a lot of visibility.
• Greatly reduced costs from using other tools that were much more expensive.

• Planview PPM directs all the resources in the right channel, hence, credible performance.
• Planview PPM initiates proper time, and resource tracking and hence is friendly for company functions.
• Planview PPM is competent in managing diverse projects, and this offers highly sustainable business continuity.

Incentivized