Using Kanban for Project Management

Instructor: Stephen Meyer

Stephen has worked as a Project Manager and is PMP certified, as well as certified by the Scrum Alliance.

There are countless project management methodologies available for different needs or preferences. For adaptable teams working on projects that need to produce fast results, Kanban is a popular choice. Learn about using Kanban for project management.


Lindsay has been working as a project manager for more than a decade and has recently moved into a consultant role. One of her main purposes in working with teams is to help them decide the best project management methodology to use. Her current client is a software development company. She believes that an Agile methodology, specifically Kanban, is the best approach for them.

Project Management

Lindsay first discusses with the team is what falls under the umbrella of project management. Often the teams with whom she works have many responsibilities, which may or may not be project-related. The type of work she intends to help them manage involves a specific, non-routine outcome, the actions or functions that produce it, and the defined timeframe in which this occurs. To help her client understand, she makes the distinction between a website they might create, which would be a project, and the day-to-day functions that involve use of the website, which would not be a project.

Managing the project first involves moving from an idea or concept to defining the work and making a plan. From there, the work is completed, verification that the work is complete occurs, and steps are taken to end the project. The main areas of focus include the scope, the timeframe, and the product. Lindsay's recommendation of Kanban as a methodology is based on these areas.


Before Lindsay details how Kanban handles the scope, timeframe, and product of a project, she gives them a background of Kanban and what it attempts to accomplish. Kanban is an Agile project methodology. Agile is an approach to projects that seeks to offer an alternative to traditional methodologies. Rather than placing an emphasis on document-driven process, it emphasizes interactions between the team and customer and creating a quality product efficiently.

There are several methodologies used to implement Agile. While they each have a shared focus on people and product, Kanban is unique among them in terms of process. Its primary identifier is a continuous flow with limits at various points to identify and remove bottlenecks, as well as maximize the team's efficiency. This maximized efficiency allows the full team to feel utilized throughout the process and leads to a higher quality of product produced in shorter, more frequent intervals.


Once Lindsay helps give her client a background on how she approaches project management and Kanban, she moves into the specifics of how Kanban is used in each aspect of project management. The first area she discusses involves scope.

From Lindsay's perspective, scope is representative of the project work, or the various requirements needed to accomplish the project. Kanban, like many Agile methodologies, breaks project work down to be smaller and more manageable, taking the form of user stories. User stories detail functionality desired for specific users.

In Kanban, user stories are displayed visually for the team on cards and displayed on a Kanban board, which captures work that is available for the team to work on, as well as work that the team has taken on. Visualizing the work, and the scope of the project, is a key component of Kanban, which helps keep the team focus and committed to completing the work in a reasonable amount of time.

Kanban Board


The discussion of completing project work is Lindsay's segue into the next thing she considers a key aspect of project management, which is timeframe. In traditional project methodologies, the timeframe is the length of the project. However, in Kanban, the timeframe, like the project work, is broken down.

A continuous flow is used to complete user stories. The flow is marked by points of progress, typically work that is ready to be taken on, work that is in progress, and work that has been completed. These high-level descriptions might be broken into lower-level descriptions of progress, but the concept is consistent. Each user story moves, or flows, through the points of progress. It is continuous in the sense that there are not specific starting or ending points for the flow.

To unlock this lesson you must be a Member.
Create your account

Register to view this lesson

Are you a student or a teacher?

Unlock Your Education

See for yourself why 30 million people use

Become a member and start learning now.
Become a Member  Back
What teachers are saying about
Try it now
Create an account to start this course today
Used by over 30 million students worldwide
Create an account