Differences

This shows you the differences between two versions of the page.

--- training:project_management:kanban2 [2024/09/12 15:14] – created wikiadmin
+++ training:project_management:kanban2 [2024/09/12 15:16] (current) – wikiadmin
@@ Line 1: / Line 1: @@
+====== Kanban in Project Management ======
+Kanban is a visual project management method designed to help teams optimize their workflow, improve efficiency, and ensure a smooth delivery of tasks. It originated from lean manufacturing techniques used by Toyota and has since been widely adopted in various industries, particularly in software development and agile project management.
+===== Key Concepts of Kanban =====
+  * **Visualizing Workflow**:
+    * The core of Kanban is the Kanban board, which provides a visual representation of tasks.
+    * It typically consists of columns representing different stages in the process, such as "To Do," "In Progress," "Testing," and "Completed."
+    * Tasks are represented by cards (usually sticky notes or digital cards) that move across the board as they progress through the stages.
+  * **Limiting Work in Progress (WIP)**:
+    * Kanban emphasizes setting limits on how many tasks can be in progress at each stage of the workflow.
+    * This avoids bottlenecks, overburdening team members, and ensures that tasks are completed before new ones are started.
+    * WIP limits are often visualized directly on the Kanban board (e.g., a maximum of 5 tasks can be in the "In Progress" stage).
+  * **Managing Flow**:
+    * Teams focus on maintaining a steady flow of tasks from start to finish.
+    * By constantly monitoring how tasks move through the stages, teams can identify bottlenecks or delays and address them.
+    * Kanban encourages regular reviewing of the process to ensure continuous improvement.
+  * **Making Process Policies Explicit**:
+    * In Kanban, it’s important to have clear, explicit rules for how tasks move from one stage to another.
+    * These policies help ensure that everyone on the team understands the workflow, reducing confusion and miscommunication.
+  * **Continuous Improvement**:
+    * Kanban is not static; teams are encouraged to continuously refine their processes based on feedback and observation.
+    * Retrospectives or reviews can help identify areas for improvement, ensuring the workflow evolves as the team and project needs change.
+  * **Feedback Loops**:
+    * Regular reviews and stand-up meetings are encouraged to discuss the status of tasks and make adjustments if necessary.
+    * This can be done daily (daily standups) or at the end of each iteration to ensure that issues are identified and resolved quickly.
+  * **Metrics and Measurement**:
+    * Kanban uses metrics like **Lead Time** (the total time it takes for a task to go from start to completion) and **Cycle Time** (the time it takes for a task to go through a specific part of the workflow).
+    * These metrics help teams analyze their performance and efficiency, allowing them to make data-driven improvements to their workflow.
+===== Benefits of Kanban =====
+  * **Flexibility**: Unlike Scrum, which requires fixed-length sprints and pre-planning, Kanban is more flexible. Teams can pull tasks from the backlog as needed, without the need for a sprint cycle.
+  * **Improved Workflow**: The emphasis on visualizing work and limiting WIP reduces bottlenecks and helps teams prioritize work effectively.
+  * **Efficiency**: By focusing on continuous delivery and flow, teams often find they can complete tasks faster and with less wasted effort.
+  * **Transparency**: The visual nature of the Kanban board ensures that everyone can see the current state of tasks, making it easier to communicate progress.
+===== Example of a Kanban Board =====
+^ To Do        ^ In Progress   ^ Under Review  ^ Completed  ^
+| Task 1       | Task 2        | Task 3        | Task 4     |
+| Task 5       | Task 6        |               | Task 7     |
+Tasks (like Task 1, Task 2) move from left to right as work progresses. The board might have WIP limits to ensure no more than 3 tasks are in "In Progress" at a time, preventing team overload and encouraging completion before new tasks are started.
+===== When to Use Kanban =====
+  * **Ongoing projects with no fixed deadlines**: Kanban is ideal for continuous delivery projects where tasks or customer requests come in steadily and need to be handled efficiently.
+  * **Teams seeking flexibility**: Since it doesn’t enforce time-boxed iterations (like Scrum sprints), Kanban works well for teams that prefer a flexible, non-iterative approach.
+  * **Teams focused on improving flow**: When the main focus is to keep the work moving smoothly through the process with minimal disruptions, Kanban is effective.
 ====== Kanban in Project Management ======