Planview LeanKit

To help keep track of my audit projects in terms of planning, fieldwork, drafting of issues and observations, and report issuance. It centralizes the audit team's project monitoring and management process and keeps the whole team engaged at one source. We set up one Planview LeanKit project board for each audit assignment.

No, so far have not had the need to do so.

Awesome tool. We use it to organize the work of many teams in various legal practices.

In our case we maintain a very simple kanban-type structure since we work with a lot of different teams. In all cases we adapt the solution for them.

Planview LeanKit is used is a couple of different business areas. The Performance Improvement team, which supports multiple applications, utilizes it to manage our backlog of work that needs to be one. This is used in team meetings to talk about work in process, recently finished and in the pipeline waiting to be started. Planview LeanKit makes our weekly team meetings more effective as we talk through each card on the board. We are able to flag things that are waiting outside input, assign deadline dates so they are visible and allow for team collaboration outside of meetings to ensure the work is getting done. It's great to be able to reference back on work we did in case there are questions or follow-up. Another area of the business uses it lightly to manage the work for their customer, identifying work in process, recently finished or in the pipeline. They are still working to find all of the benefits of the tool but it is starting to drive meeting progress. We are excited to dabble in the new functionality of Instant Coffee and OKRs.

We change the board layout, card types, custom icons, add custom fields. We have set swimlanes for "Templates" so card types that need a set of specific data points are setup in a template card in the template swimlane. When a new one needs to be created it is easy to duplicate that card and provide answers to the needed questions.

It's an ideal digital Kanban - simple to use, flexible, and robust. I'm looking forward to future integration with whiteboarding and ideation.

Some, but the limitations in reporting has held me back.

LeanKit is easy to use, and adopt, facilitates agile adoption, and can be use for any size and type of company. You may find a lot of professionals and consultants who help with the implementation and some workshops, online Kanban boards for Lean and Agile teams help you visualize your workflow and begin to see things you never saw before. Visually manage work using Kanban boards with the flexibility to easily model any workflow process, regardless of complexity

Yes. It's really easy to customize.

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.

LeanKit is the project management tool to build Kanban boards to record and track all team’s work in one place, visualize progress across multiple projects, and get work done. Easy to create projects (in the matter of a few clicks), divide them into categories and drag-and-drop cards across lanes based on the progress. It is primarily used by Technology, Product Management, and the Business Intelligence Department.

Leankit board is quite flexible and customisable which can be a plus for most of the users. Every company has different process and way of implementing things. We had customised project board, swimlanes and cards to suit our requirement

Used in IT Dept. LeanKit addressed the problems with managing large projects. It is beneficial both on the individual level as well as for the entire team.

Customized labels by task category.
Swimlanes by person for smaller teams.

Our IT department is using LeanKit to track both development and support/admin projects. Right now the use of LeanKit is limited to the IT deparment. The biggest problem it addresses is our workload and work tracking management. We use a form of Kanban and Scrum to run our projects, LeanKit's flexibility, makes it easy to handle different processes with different teams.

The customizable board templates have allowed us to create different processes and tracking styles that fit the process we practice. The ability to change the swimlanes, the "start" lane, the different card labels, tags, and card fields means we can fit many different levels of tracking and sorting into one board. The ability to setup icons to identify card types visually is great also. Another major benefit is that LeanKit allows you to filter by all the different custom setups also.

I used LeanKit to manage a variety of projects but primarily used it to manage the recruiting/hiring pipeline for all open positions. Different departments used it differently. For example, the marketing team used it to manage their editorial calendar and different process workflows. It helps to keep the whole company in sync and able to check progress at a glance.

We used the tool for a hiring pipeline, so each “lane” was a separate job we were hiring for. Within the lane each step had a variety of candidates so we could see where we had a surplus of candidates and where we had a shortage. We also color coded the candidates so we new if they knew what their status was.

LeanKit is a simple, intuitive way to create and track tasks for KANBAN. I've used others and I'm fairly happy with LeanKit. Integrates with SSO (Okta) and is very nice.
We use it for our team projects and constantly review from it. We also have shared LeanKit boards for cross-functional teams and mult-team collaboration projects. Tagging, external links to ticketing systems, etc. make it really nice.

My team has much different workflows from an engineering and operational standpoint that most, so having the customizability was really nice for my unique team.

We use LeanKit across our entire organization. It helps us stay organized and understand what everyone is working on on a given day. It also helps us stay accountable since it is easy to see if someone does or does not have something to work on. It can also be used to assist our project manager since she can see who is in charge of what project.

We had two boards-- one that showed the whole work pipeline of our team, and one that was dedicated to team meeting specifically. However, in the end we ditched the second board for just one board. Most of us found LeanKit to be a necessary evil that was complex enough in its UI; we didn't want to make it even more complicated and difficult to understand. I think we actually tended to stick to the bare bones as much as possible, although I know there was more to the program than we explored.

LeanKit is used by my department to organize development work and issues that need to be addressed within our web applications. It's primarily used by other teams that I occasionally need to work with. It provides a way for these teams to organize and sort things in a way that fits their needs.

We use LeanKit in the IT Department to organize action and steps surrounding projects. We use a ticketing system for support requests and LeanKit for handling details of project work keeping track of exactly where we are with each step along the way until projects are complete.

LeanKit is used as an alternative planning tool for teams in engineering. [It's an] alternative to Pivotal and Trello. It's a matter of preference really, but a lot of people like it. It's great for agile development. It basically allows teams to track project progress and list goals that they want to work on, both internal to the team and across the organization.

I have helped product development teams choose LeanKit as they were developing better processes for their teams. The teams used LeanKit instead of JIRA, as it was easier to manage the flow of work that just didn't fit into JIRA. They would put all their tasks in it and be able to calculate the flow.

LeanKit was a team initiative that began when we were exploring platforms to plan projects collaboratively as a team. The way we use it today is each team within the broader Marketing organization, be it the web team, digital marketing, content, etc. has a LeanKit to organize specific activities against, be it short term projects or quarterly goals. It helps us collect tasks, assign them to owners, and serves a centralized location for accessing and keeping track of workflows and progress towards goals.

We use Leankit across the organization but have divided boards on a department basis. We use LeanKit as our primary development tool for all stories and defects.

LeanKit was implemented at Mueller Co. a couple of years ago in the operations, product management and engineering areas. As director of marketing, we were searching for a collaborative project and task management platform for our marketing team. When we discovered that the engineering and product management teams were using Leankit, we decided it would be easier for us to adopt their system than have them adopt a new one just for marketing projects.

LeanKit is being used by a single department of specialists. It is presented to the entire organization to show progress on existing, upcoming and past projects. LeanKit is being used to provide visibility into the progress of projects being handled by specialists that are managed by project managers. It provides a view of resources available and helps to forecast project deadlines for client managers.