Planview LeanKit helped us find ourselves and quickly became the centre of our transformation towards Agile.
June 24, 2020

Planview LeanKit helped us find ourselves and quickly became the centre of our transformation towards Agile.

Daniel Schleusener | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Review Source

Overall Satisfaction with Planview LeanKit

Over the last two years, we kanbanised a lot of our business processes with Planview LeanKit. Our first and to date most successful implementation was in Service Operations. But since then, we started to use Planview LeanKit virtually everywhere, from Sales and Consulting over Project Management - both as meta and project specific boards - up to top-level management meeting organization.

So far, most tries to use Planview LeanKit as a way to realize potential in a business process were a success, independent of department. In all use cases it helps to visualize work where our other tools merely list and obfuscate data and To-Dos. It also supported our transformation towards Agile Management.
  • Planview LeanKit is particularly good in visualizing a process and the work that is in it. While the column structure seems simple, it still manages to capture the essence of our work and in a way de-abstracts it.
  • The multiple ways of customizing boards, lanes, cards and reports mean Planview LeanKit can be made fit to any process.
  • With descriptions and comments it is a great tool to facilitate project work and collaboration in a comprehensive manner.
  • The reporting offers many ways to keep track of the current state and development potential of a board and its process.
  • The Planview LeanKit support is particularly fast to respond, answers (and asks) very knowledgeable and like-able.
  • Over the last two years I saw Planview LeanKit develop a lot of great features that were really helpful. The product constantly evolves.
  • Planview LeanKit currently can't or should not be used as a central spot for data and collaboration. Particularly attachments are not well-handled.
  • The portable side of Planview LeanKit is really lacking.
  • We would appreciate some options to group or stack cards.
  • ROI for Planview LeanKit was easily achievable with just a month of setting up.
  • We could rapidly cut down on unnecessary work in all fields.
  • We can easily monitor current the health and input and adjust our capacities as necessary.
  • Value throughput in innovation management has grown.
  • Covid-19 was a business opportunity for us as many customers moved their workforce into home offices. The resulting business was handled differently. So each of those orders received a small pill bottle icon, signifying it to be a "Corona Order".
  • In Order management we used the custom field for billing prospective.
  • In Operations we used a swimlane to distinguish customer from internal work.
  • Tagging helps operations to identify which type system an incident is for.
  • Complementing the last point, engineers have personalized tag filters which contain all tags of systems they're familiar with. They only see work that they can actually handle.
  • For our adaption of Scrumban we have created a board template that is used in every project.
Particularly in operations and project management we could put reporting to good use. In service operations we have daily, weekly and monthly reports, looked at directly in Planview LeanKit. Two highlights:
  • We carefully watch the flow of work in service operations, as service transition of bigger customers is a bit capacity issue for us and can cancel out the normal highs and lows. We can therefore react on a day to day basis in terms of distributing our engineering capacity.
  • Our escalation management has benefited massively through the use of "stale" cards, which have unfortunately been renamed to "inactive" a short while ago.
So far we have not used other products from Planview but we plan to check project place out.
This is one of the key aspects of Planview LeanKit within our organization. During the last two years we have steadily transformed towards agile processes. Planview LeanKit, with its evolving features and customizable implementation, is not only a visible example of this transition, it is also the tool with which we transform processes. For several processes it has become the place where the process happens and as such the process can adapt simply by adapting Planview LeanKit, which is rather easy, given the data we receive through the reports and simply by using it.

Another example of Planview LeanKit's role as a catalyst for change is our Scrumban implementation. With each large project we use Scrumban in, we adapt the board and try a few new things. Some work, others not (yet). But it's always as simple as a small change to the board, a card or a lane.
Originally, we had evaluated two other tools next to Planview LeanKit: Kanbantool and Kanbanflow. The latter was a close contestant for productive use, as it was also very customizable and a joy to work with and look at. It also had lower user fees and a mobile integration.

In the end, we picked Planview LeanKit because of several reasons:
Aesthetics: The look was much more clean and professional.
Reporting: It was obvious from the start that we could use Planview LeanKit as a tool for improvement.
API: We needed to integrate the Kanban into our central systems and Planview LeanKit API was (and still is) a way to do it.
Card Headers: This sounds like a simple thing, but the headers above the titles fit our work perfectly and looked perfect, which helped the decision.

Planview LeanKit excels in any scenario where you need to visualize and organize work to be done. You can feasible even use it as a personal to-do application. We use it as a way to keep track of our current topics in management meetings as well as a Scrumban implementation of project management.

However, when processes and work is very file- and data-heavy, using Planview LeanKit is less appropriate as there's just not way of doing a sensible file management.