kanban

Kanban Framework In A Nutshell

Kanban is a lean manufacturing framework first developed by Toyota in the late 1940s. The Kanban framework is a means of visualizing work as it moves through identifying potential bottlenecks. It does that through a process called just-in-time (JIT) manufacturing to optimize engineering processes, speed up manufacturing products, and improve the go-to-market strategy.

Understanding the Kanban framework

Like many lean manufacturing processes, the kanban framework was first developed by Toyota in the late 1940s. 

Through a process called just-in-time (JIT) manufacturing, Toyota began to optimize its engineering processes based on a model supermarkets were using to control inventory levels.

Using this model, supermarkets stock just enough product to meet consumer demand.

As inventory levels respond to consumption patterns, the supermarket avoids holding excess stock and the inefficiencies that result. 

Removing these process inefficiencies – or project bottlenecks – is central to the kanban framework.

To identify these bottlenecks and increase transparency and collaboration, the entire project is illustrated on a kanban board.

Kanban boards visually depict:

  • Tasks that are completed
  • Tasks that are currently being performed.
  • Future tasks.

This simple approach to defining projects means that external stakeholders or new team members can quickly get up to speed.

Many businesses utilize physical kanban boards while those in software development use virtual boards.

This facilities better collaboration and increases accessibility from multiple locations.

Four core principles of the kanban framework

Kanban principles are based on:

  1. An emphasis on small and gradual changes to the existing workflow.
  2. Limiting existing tasks. Here, the team must not take on too much work such that the project is negatively affected.
  3. Respect for existing roles and responsibilities. The kanban framework improves efficiency in established systems. It does not require that businesses change their operations or culture.
  4. Leadership. Traditional project management practices stipulate that a project manager must sign off on every task, no matter how menial. However, the kanban framework affords whoever is working on a task the freedom to make their own decisions. This creates a culture of iterative improvement and creates the next generation of leaders.

Implementing the Kanban framework

To apply kanban principles to almost any scenario, kanban management consultant David J. Anderson identified six core practices:

Visualize the workflow

This begins by creating a kanban board with columns for the three types of tasks mentioned in the introduction.

For each type, kanban cards representing specific work items should be assigned.

Cards should be moved from column to column as work on them progresses.

Limit tasks that are currently being performed by setting constraints

This helps avoid multitasking and subsequent process inefficiencies. 

Manage flow

Or the movement of work items through each step of the process.

Many businesses make the mistake of micro-managing staff to keep them constantly busy.

But the kanban framework simply focuses on moving the work through the process as quickly and efficiently as possible.

Make management policies explicit

Members of the project team must understand what they are trying to achieve.

Collect feedback

Kanban boards should have a column assigned for daily feedback – whether that be from staff or customers.

This creates agile feedback loops that encourage knowledge transfer between key stakeholders.

Collaborative improvement

With a deeper understanding of the project and potential bottlenecks, organizations using the kanban framework have a collective understanding of problems that need addressing.

Working toward the same goal, they also share a collective vision of future success.

Kanban framework examples

In truth, kanban frameworks take many forms depending on the particular business, industry, or project at hand.

Below we will list some of the most common applications.

IT 

Kanban is a favorite of IT operations teams because of the enormous amount of tasks their departments need to deal with.

Boards are used to visualize workflows with columns used to better differentiate flow stages.

Some also use swimlanes to acquire a deeper understanding of the work’s importance and avoid priority conflicts. 

In truth, many IT departments seek to process more work than their capacity allows.

The result is invisible work which causes longer lead and cycle times and causes unhappiness among customers and managers alike.

Effective structuring of the kanban board to provide a holistic overview of operation is key.

Software development

Kanban boards designed for development teams display workflows comprised of many functional steps and their associated columns.

Swimlanes can also be effective in software development as a way to visually represent the different classes of work.

For example, some tasks will involve work on defects, while others will be related to product features.

Small teams or those that are new to kanban may choose a simple workflow that consists of basic steps such as design, development, code review, testing, and deployment.

More advanced teams may want to combine their workflows with quality assurance or customer support.

Sales

Small to medium-sized businesses can use kanban boards to move customers through an entire pipeline – whether that be one related to sales or marketing.

This is an easy way to spot bottlenecks and call upon an Account Executive or SDR to intervene.

Since kanban boards provide a complete overview of the entire customer journey and sales funnel, teams can also avoid sending the same emails twice.

On that note, kanban workflows can illustrate simple sales pipelines with a Qualification, Proposal, and Sale step.

As these workflows become more complex over time, additional steps such as Presentation, Evaluation, Negotiation, and Closing can be added.

Portfolio level

Teams who are focused on day-to-day tasks can sometimes become overwhelmed and lose sight of the bigger, strategic-level picture.

Portfolio kanban frameworks help these teams plan long-term activities and strategies and are an ideal way to appreciate the strategic evolution of the team, department, or company itself.

Portfolio boards vary according to the size of the team or the focus of the work.

Product development teams use two swimlanes to prioritize their initiatives, while project management teams break initiatives down into smaller pieces that are represented by small colored squares.

UX teams and designers

Some UX teams and designers use kanban boards that are divided into:

  • Design-related tasks – user research, design reviews, etc.
  • Administrative tasks – meeting the client, signing a contract, and so forth.

Workflows can also be divided into phases such as Draft, Wireframes, Mockups, and Prototypes.

This allows teams to move individual tasks from the ideation phase through to the final product.

Kanban vs. Scrum

what-is-scrum
Scrum is a methodology co-created by Ken Schwaber and Jeff Sutherland for effective team collaboration on complex products. Scrum was primarily thought for software development projects to deliver new software capability every 2-4 weeks. It is a sub-group of agile also used in project management to improve startups’ productivity.

Kanban and Scrum are agile project management methodologies enabling quick iterations, short development cycles, and team productivity.

Thus, both tools are extremely useful and essential in the agile development framework.

Key takeaways

  • The kanban framework is an illustrative approach to project or product development with a focus on removing bottlenecks.
  • The kanban framework analyses project tasks according to whether they are completed, currently being performed, or assigned to a future date. This enables project team members to visualize the workflow and minimize multitasking to prevent bottlenecks.
  • The kanban framework is suitable for most industries and does not require that a business change its culture or management practices. The framework also empowers those carrying out the tasks to make important strategic decisions.

What are the 6 rules of Kanban?

Connected Agile Frameworks

AIOps

aiops
AIOps is the application of artificial intelligence to IT operations. It has become particularly useful for modern IT management in hybridized, distributed, and dynamic environments. AIOps has become a key operational component of modern digital-based organizations, built around software and algorithms.

Agile Methodology

agile-methodology
Agile started as a lightweight development method compared to heavyweight software development, which is the core paradigm of the previous decades of software development. By 2001 the Manifesto for Agile Software Development was born as a set of principles that defined the new paradigm for software development as a continuous iteration. This would also influence the way of doing business.

Agile Project Management

agile-project-management
Agile project management (APM) is a strategy that breaks large projects into smaller, more manageable tasks. In the APM methodology, each project is completed in small sections – often referred to as iterations. Each iteration is completed according to its project life cycle, beginning with the initial design and progressing to testing and then quality assurance.

Agile Modeling

agile-modeling
Agile Modeling (AM) is a methodology for modeling and documenting software-based systems. Agile Modeling is critical to the rapid and continuous delivery of software. It is a collection of values, principles, and practices that guide effective, lightweight software modeling.

Agile Business Analysis

agile-business-analysis
Agile Business Analysis (AgileBA) is certification in the form of guidance and training for business analysts seeking to work in agile environments. To support this shift, AgileBA also helps the business analyst relate Agile projects to a wider organizational mission or strategy. To ensure that analysts have the necessary skills and expertise, AgileBA certification was developed.

Business Model Innovation

business-model-innovation
Business model innovation is about increasing the success of an organization with existing products and technologies by crafting a compelling value proposition able to propel a new business model to scale up customers and create a lasting competitive advantage. And it all starts by mastering the key customers.

Continuous Innovation

continuous-innovation
That is a process that requires a continuous feedback loop to develop a valuable product and build a viable business model. Continuous innovation is a mindset where products and services are designed and delivered to tune them around the customers’ problem and not the technical solution of its founders.

Design Sprint

design-sprint
A design sprint is a proven five-day process where critical business questions are answered through speedy design and prototyping, focusing on the end-user. A design sprint starts with a weekly challenge that should finish with a prototype, test at the end, and therefore a lesson learned to be iterated.

Design Thinking

design-thinking
Tim Brown, Executive Chair of IDEO, defined design thinking as “a human-centered approach to innovation that draws from the designer’s toolkit to integrate the needs of people, the possibilities of technology, and the requirements for business success.” Therefore, desirability, feasibility, and viability are balanced to solve critical problems.

DevOps

devops-engineering
DevOps refers to a series of practices performed to perform automated software development processes. It is a conjugation of the term “development” and “operations” to emphasize how functions integrate across IT teams. DevOps strategies promote seamless building, testing, and deployment of products. It aims to bridge a gap between development and operations teams to streamline the development altogether.

Dual Track Agile

dual-track-agile
Product discovery is a critical part of agile methodologies, as its aim is to ensure that products customers love are built. Product discovery involves learning through a raft of methods, including design thinking, lean start-up, and A/B testing to name a few. Dual Track Agile is an agile methodology containing two separate tracks: the “discovery” track and the “delivery” track.

Feature-Driven Development

feature-driven-development
Feature-Driven Development is a pragmatic software process that is client and architecture-centric. Feature-Driven Development (FDD) is an agile software development model that organizes workflow according to which features need to be developed next.

eXtreme Programming

extreme-programming
eXtreme Programming was developed in the late 1990s by Ken Beck, Ron Jeffries, and Ward Cunningham. During this time, the trio was working on the Chrysler Comprehensive Compensation System (C3) to help manage the company payroll system. eXtreme Programming (XP) is a software development methodology. It is designed to improve software quality and the ability of software to adapt to changing customer needs.

Lean vs. Agile

lean-methodology-vs-agile
The Agile methodology has been primarily thought of for software development (and other business disciplines have also adopted it). Lean thinking is a process improvement technique where teams prioritize the value streams to improve it continuously. Both methodologies look at the customer as the key driver to improvement and waste reduction. Both methodologies look at improvement as something continuous.

Lean Startup

startup-company
A startup company is a high-tech business that tries to build a scalable business model in tech-driven industries. A startup company usually follows a lean methodology, where continuous innovation, driven by built-in viral loops is the rule. Thus, driving growth and building network effects as a consequence of this strategy.

Kanban

kanban
Kanban is a lean manufacturing framework first developed by Toyota in the late 1940s. The Kanban framework is a means of visualizing work as it moves through identifying potential bottlenecks. It does that through a process called just-in-time (JIT) manufacturing to optimize engineering processes, speed up manufacturing products, and improve the go-to-market strategy.

Rapid Application Development

rapid-application-development
RAD was first introduced by author and consultant James Martin in 1991. Martin recognized and then took advantage of the endless malleability of software in designing development models. Rapid Application Development (RAD) is a methodology focusing on delivering rapidly through continuous feedback and frequent iterations.

Scaled Agile

scaled-agile-lean-development
Scaled Agile Lean Development (ScALeD) helps businesses discover a balanced approach to agile transition and scaling questions. The ScALed approach helps businesses successfully respond to change. Inspired by a combination of lean and agile values, ScALed is practitioner-based and can be completed through various agile frameworks and practices.

Spotify Model

spotify-model
The Spotify Model is an autonomous approach to scaling agile, focusing on culture communication, accountability, and quality. The Spotify model was first recognized in 2012 after Henrik Kniberg, and Anders Ivarsson released a white paper detailing how streaming company Spotify approached agility. Therefore, the Spotify model represents an evolution of agile.

Test-Driven Development

test-driven-development
As the name suggests, TDD is a test-driven technique for delivering high-quality software rapidly and sustainably. It is an iterative approach based on the idea that a failing test should be written before any code for a feature or function is written. Test-Driven Development (TDD) is an approach to software development that relies on very short development cycles.

Timeboxing

timeboxing
Timeboxing is a simple yet powerful time-management technique for improving productivity. Timeboxing describes the process of proactively scheduling a block of time to spend on a task in the future. It was first described by author James Martin in a book about agile software development.

Scrum

what-is-scrum
Scrum is a methodology co-created by Ken Schwaber and Jeff Sutherland for effective team collaboration on complex products. Scrum was primarily thought for software development projects to deliver new software capability every 2-4 weeks. It is a sub-group of agile also used in project management to improve startups’ productivity.

Scrum Anti-Patterns

scrum-anti-patterns
Scrum anti-patterns describe any attractive, easy-to-implement solution that ultimately makes a problem worse. Therefore, these are the practice not to follow to prevent issues from emerging. Some classic examples of scrum anti-patterns comprise absent product owners, pre-assigned tickets (making individuals work in isolation), and discounting retrospectives (where review meetings are not useful to really make improvements).

Scrum At Scale

scrum-at-scale
Scrum at Scale (Scrum@Scale) is a framework that Scrum teams use to address complex problems and deliver high-value products. Scrum at Scale was created through a joint venture between the Scrum Alliance and Scrum Inc. The joint venture was overseen by Jeff Sutherland, a co-creator of Scrum and one of the principal authors of the Agile Manifesto.

Read Also: Business Models Guide, Sumo Logic Business Model, Snowflake

InnovationAgile MethodologyLean StartupBusiness Model InnovationProject Management.

Read Next: SWOT AnalysisPersonal SWOT AnalysisTOWS MatrixPESTEL

Read Next: AgileDevOpsDevSecOpsScrumLeanSprint.

Main Guides:

Scroll to Top
FourWeekMBA