Intro to Kanban, Part 1

Introduction to Kanban

Introduction and Acknowledgments

• The speaker introduces the session on Kanban, expressing appreciation for colleague Alan Brouilette's contributions to the event.

• Alan Grenada introduces himself, mentioning his role at 18F and his experience with Agile methodologies, particularly Scrum.

Background of Agile and Scrum

• Alan shares how he discovered Agile while working in internet-related fields, realizing it aligned with his work style.

• He briefly discusses his diverse background in finance and radio before transitioning into teaching Agile and Kanban.

Understanding Kanban

Key Concepts of Kanban

• The speaker emphasizes that Agile and Scrum are not universal solutions for all teams or organizations; they are tools among many.

• Kanban is introduced as a flexible approach that can adapt to various situations where Scrum may not be effective.

Goals for the Session

• The objectives include understanding good Kanban implementation characteristics, pull systems, capacity vs. demand matching, and designing a Kanban board.

• There will also be discussions on scaling Kanban at organizational levels towards the end of the session.

Kanban Fundamentals

Core Principles of Kanban

• The session will cover basic premises of Kanban, including its emphasis on visualizing processes through a Kanban board.

• Topics will include pull systems, work-in-progress (WIP), WIP limits, classes of service, and process policies.

Benefits of Using Kanban

• Unlike Scrum, which requires significant structural changes to implement effectively, Kanban allows for gradual integration into existing workflows.

Understanding Kanban: A Flexible Approach to Workflow

The Nature of Kanban

• Kanban requires more discipline from teams compared to Scrum, which has defined roles and meetings. It leaves many aspects open for interpretation.

• The fundamental aspect of Kanban is the visible part, represented by the Kanban board, which helps in managing workflow effectively.

Flow Model in Kanban

• Work in Kanban comes in discrete pieces, flowing from left to right on the board. This flow model is derived from lean principles.

• Teams work on tasks one at a time, whether it's developing ideas into products or fulfilling customer orders.

• The process resembles an assembly line where value-releasable products flow out after completion.

Visualizing Work with a Kanban Board

• A simple three-column Kanban board consists of "To Do," "In Progress," and "Done" columns that visualize workflow.

• Items are represented as sticky notes or digital cards (e.g., in JIRA), making it easy to track progress visually.

Practical Application of Kanban

• Implementing a Kanban board can impose necessary structure even amidst chaotic environments.

• An example is shared about a family using a Kanban board to manage children's activities and responsibilities, illustrating its simplicity and effectiveness.

Benefits of Using a Kanban Board

• The primary function of the Kanban board is to make processes visible, allowing teams to understand their workflow better.

• It implements a pull system that limits work-in-progress (WIP), aligning demand with capacity for improved efficiency.

Historical Context of Kanban

• The term "Kanban" translates to "ticket" or "card," originating from Toyota's efforts to reduce waste through just-in-time manufacturing practices.

Understanding Kanban and Just-in-Time Manufacturing

The Concept of Kanban in Manufacturing

• Instead of using large bins for parts on an assembly line, a small box with a Kanban card is utilized. When the box is empty, the card is handed off to request more parts.

• This system allows for continuous manufacturing by knowing exactly how long it takes to receive new parts, minimizing wasteful inventory.

• The pull system implemented through Kanban aligns with just-in-time manufacturing principles, which were later adapted for software development.

Visualizing Work Processes

• The speaker discusses modifying their process visualization board, indicating that items ready to be worked on can be seen as a backlog.

• A column labeled "Work in Progress" (WIP) replaces traditional "To Do" lists, emphasizing the importance of managing ongoing tasks effectively.

• Items are prioritized from upper left (highest priority) to lower right (lowest priority), guiding workflow into the WIP column.

Managing Knowledge Worker Inventory

• Cards represent knowledge worker inventory; they have associated costs and can become invalid due to external changes, leading to wasted effort.

• Limiting WIP helps prevent overuse of these cards and ensures efficient flow within processes while avoiding paralysis caused by excessive workload.

Overcoming Overwork Challenges

• A large pile of work can obscure process visibility; limiting WIP clarifies workflow and identifies bottlenecks or delays in the process.

• Contrary to popular belief, having too many tasks leads to panic rather than productivity; clarity in task management enhances efficiency.

Implementing Pull Systems Effectively

• The goal is matching demand with capacity through a pull system that simplifies team management amidst high workloads.

• A more complex Kanban board includes columns for different stages: Ready, Estimate & Analysis, Development, Testing, and Done.

Understanding Kanban Implementation

The Benefits of a Pull System

• A pull system allows teams to manage workload effectively, reducing panic and confusion. This leads to quicker completion of tasks with less waste.

• Key features of Kanban include Work In Progress (WIP) limits and the pull system, which are essential for its effective implementation.

Distinction Between Kanban and Scrum

• While both Kanban boards and Scrum task boards may appear similar, they differ fundamentally; Scrum is a small batch process, whereas Kanban is flow-based and implements a true pull system.

Recommended Tools for Kanban

• For implementing the Kanban process, physical tools like sticky notes on a wall are preferred for their simplicity.

• However, in distributed teams, digital tools become necessary. JIRA is highlighted as an easy-to-use option that is widely adopted despite not being the most ideal representation of Kanban.

Other Notable Tools

• LeanKit is mentioned as another good tool for managing Kanban processes, particularly effective for personal use cases where individuals apply Kanban principles to their lives.

Making Policies Explicit

• Establishing clear policies helps streamline complicated processes by eliminating waste and enhancing productivity.

Understanding Kanban Board Dynamics

Column Definitions and Work Understanding

• The Kanban board's columns indicate specific statuses of work items, such as "submitted," "estimate," and "development," helping teams understand the workflow accurately.

• In complex Kanban situations, descriptions for each column are often posted on the board or accessible to ensure team members comprehend their meanings.

Policies and Transition Criteria

• A mnemonic related to policies is likened to a restaurant rule where a full party must be present before being seated, illustrating the importance of clear criteria for moving work items through stages.

• Transition specifications include defining what constitutes a completed state in one column and the requirements needed to move to the next column.

Reducing Waste in Processes

• Clear transition requirements from development to testing (e.g., code checks, static analysis completion) minimize confusion and streamline processes, reducing waste.

• Establishing defined transitions leads to fewer back-and-forth movements in workflows, enhancing efficiency.

Importance of Coaching in Implementation

• Engaging an experienced Kanban or agile coach can simplify implementation challenges; trial and error can be avoided with proper guidance.

• Mapping and analyzing the value chain is crucial; it involves understanding all steps from idea inception to final product delivery.

Value Chain Analysis

• The value chain encompasses every step required for new work entering a system until its completion, highlighting opportunities for waste reduction but also potential mistakes.

Understanding Kanban Boards and Team Dynamics

The Importance of Clarity in Work Processes

• The initial steps in creating a Kanban board reveal discrepancies between team members' perceptions of their workflow, highlighting the need for clarity in how tasks are accomplished.

• Acknowledging the difference between perceived and actual work processes is crucial; this requires courage to confront reality versus expectations.

Designing a Media-Oriented Kanban Board

• The proposed media-oriented Kanban board includes stages such as outline, draft, graphics addition, approval, and completion to visualize the workflow effectively.

• An essential component of the board is a "submitted" column for tasks that are ready to be started, ensuring all work is accounted for before moving forward.

Implementing Work-in-Progress (WIP) Limits

• Initial WIP limits are set based on team size assumptions; these limits help manage workload and identify bottlenecks quickly.

• The goal is to minimize WIP limits to enhance clarity and efficiency within the team's process, aiming for an ideal state where each task flows smoothly through the system.

Managing Different Types of Work with Swim Lanes

• Teams may handle various types of work; using swim lanes allows differentiation between feature articles and blog posts on the Kanban board.

• Allocating resources effectively—75% bandwidth for feature articles versus 25% for blog posts—ensures focus on priority tasks while maintaining balance.

Ensuring Flow with WIP Limits

• Each swim lane has specific WIP limits that must be adhered to both horizontally and vertically, preventing blockages in any part of the process.

• Maintaining compliance with WIP limits ensures continuous flow of tasks without overwhelming any single step or individual within the team.

Addressing Multiple Work Types Within One Team

Kanban Board Design and Workflow Management

Integrating Different Work Types on a Kanban Board

• The importance of displaying different work types (e.g., feature articles vs. blog posts) on a single Kanban board to maintain clarity and the original intent of using Kanban.

• Suggestion to use a double line to separate swim lanes, allowing for varied column structures under each category while keeping them visually distinct.

• Emphasizes the need for a unified view of workflow across the team, advocating for all tasks to be represented in one place.

Managing Work In Progress (WIP)

• Discussion on WIP limits being effective only when applied to singular columns; highlights challenges with varying task steps that consume time differently.

• Encouragement to customize Kanban boards by adjusting columns and implementing specific WIP limits tailored to team needs.

Benefits of Visualizing Completed Work

• Addressing when to remove cards from the "Done" column; suggests it can boost morale by providing visual evidence of accomplishments.

• Acknowledges satisfaction derived from seeing completed tasks accumulate visibly, reinforcing motivation among team members.

Understanding Board Layout and Flow

• Description of a sample Kanban board layout, including backlog items and multiple columns for work in progress, enhancing visibility into project status.

• Notes on how card design contributes valuable information at a glance, indicating that teams should develop their own formats based on what works best for them.

Enforcing WIP Limits Effectively

• Importance of maintaining strict WIP limits; overflowing columns indicate bottlenecks that hinder workflow efficiency.

• Observations about policies displayed directly on the board, such as demo schedules tied to readiness criteria, ensuring clarity in processes.

Fun Elements in Workflow Management

• Mention of playful elements within the board setup (e.g., enjoying a pint), suggesting that incorporating fun can enhance team dynamics during work processes.

Upcoming Topics in Future Discussions

• Preview of future discussions focusing on handling blocked items and replenishment strategies within Kanban systems.

Role Clarification within Kanban Framework

Product Owner's Role in Backlog Management

Understanding the Product Owner's Responsibilities

• The product owner manages a significantly larger backlog, prioritizing items to ensure stories are ready for development. They drive backlog grooming activities and maintain clarity on completed tasks.

• The product evolves iteratively over time, with or without sprints. The product owner's role is crucial in guiding the development process, addressing questions from developers or testers regarding specific features.

• While the product owner may not be directly involved in every task, they play a vital role in clarifying requirements and resolving queries that arise during testing phases.

• It’s essential for the product owner to focus on customer needs rather than solely their vision for the product. This ensures that development aligns with what customers truly want.

Addressing Blockers and Future Discussions

• A two-part answer was provided regarding how to handle blocked items, indicating that further discussion will occur in a follow-up session scheduled for tomorrow at 2:30 p.m. Eastern Time.

• Feedback is encouraged from participants to improve content quality. An evaluation form link was shared for attendees to provide insights on their experience.

Kanban System Insights

Moving Cards Within Kanban

• A question arose about whether cards move forward when completed or only when there is space available in the next column. The response highlighted that both conditions must be met: readiness of the card and availability of space.

• Emphasis was placed on avoiding push systems where urgency overrides established work-in-progress (WIP) limits; leadership support is critical for maintaining these limits effectively.

Daily Meetings and Card Movement

• In Kanban teams, daily meetings often start by reviewing cards on the board from right to left, focusing on moving tasks forward efficiently through collaboration among team members.

• During daily meetings, team members discuss which cards can be moved based on completion status; this collaborative approach helps identify progress and potential bottlenecks.

Handling Testing Failures

Managing Regressions and Blocked Cards

• A significant question addressed whether it’s acceptable for a card to move backward if it fails testing. This highlights challenges faced when no room exists in previous columns for regression handling.

Understanding Work In Progress (WIP) Limits

The Flexibility of WIP Limits

• There are no strict rules for determining WIP limits; teams should find what works best for them based on their specific circumstances and frequency of tasks.

• If a card frequently needs to move backwards, it may indicate that the columns are not properly adjusted, suggesting a need for reevaluation.

Setting Effective WIP Limits

• When considering WIP limits, it's common to start with limits per column rather than per individual developer.

• A typical starting point is two items per developer; however, this can vary significantly depending on team dynamics and task complexity.

Adjusting WIP Limits in Practice

• Teams should be prepared to adjust their WIP limits as they gain experience; what initially seems appropriate may require changes based on practical outcomes.