Kanban Methodology Advantages and Disadvantages

Learn about the Kanaban Methodology which is a popular framework for agile software development. This mind map summarizes its advantages and disadvantages, lean management in general and how a Kanaban board works.

Get Started. It's Free
or sign up with your email address
Rocket clouds
Kanban Methodology Advantages and Disadvantages by Mind Map: Kanban Methodology Advantages and Disadvantages

1. Kanban Definition

1.1. Kanban is a popular framework used to implement agile software development. It requires real-time communication of capacity and full transparency of work.

1.2. The etymology of the word "kanban"

1.2.1. Kanban is Japanese for “visual signal” or “card.” Toyota line-workers used a kanban (i.e., an actual card) to signal steps in their manufacturing process. The system’s highly visual nature allowed teams to communicate more easily on what work needed to be done and when.

2. Kanban Software

2.1. Helps teams visualize work and workflows.

2.2. Common Features of Kanban Software

2.2.1. Kanban boards

2.2.2. Work-in-progress (WIP) limits

2.2.3. Cumulative flow diagrams (CFDs)

2.2.4. Lead and cycle time diagrams

2.3. Examples

2.3.1. MeisterTask

2.3.2. Project Insight

2.3.3. Smartsheet

2.3.4. Workfront

2.3.5. Wrike

2.3.6. Sitetracker

2.3.7. Targetprocess

2.3.8. SmartCore

2.3.9. Ravetree

2.3.10. Trello

2.3.11. Asana

2.3.12. JIRA

2.3.13. monday.com

2.3.14. Hubstaff

2.3.15. GitLab

2.3.16. CaseCamp

2.3.17. Zenkit

3. How Kanban Works

3.1. Visualize Work

3.1.1. Communication and collaboration increases

3.2. Limit Work in Process

3.2.1. Unnecessary working time is reduced

3.3. Focus on Flow

3.3.1. Flow of work improves

3.4. Continuous Improvement

3.4.1. The team’s effectiveness improves

4. Kanban Board

4.1. A visualization of a team’s workflows.

4.1.1. Consitsts of columns, which represent different workflow stages. Cards represent tasks. During the process, the cards move through the various stages.

4.2. An example of a Kanban board software tool by MeisterTask

4.3. Example

5. Agile Scrum

5.1. Is an alternative agile framework. It can be used instead or combined with Kanban.

5.1.1. Illustration Mindmap of Agile Scrum

6. Kanban vs. Scrum

6.1. Cadence

6.1.1. Continuous flow

6.1.2. Regular fixed length sprints

6.2. Release methodology

6.2.1. Continuous delivery or at the team's discretion

6.2.2. At the end of each sprint if approved by the product owner

6.3. Roles

6.3.1. No existing roles. Some teams enlist the help of an agile coach.

6.3.2. Product owner, scrum master, development team

6.4. Key metrics

6.4.1. Cycle time

6.4.2. Velocity

6.5. Change philosophy

6.5.1. Change can happen at any time

6.5.2. Teams should strive to not make changes to the sprint forecast during the sprint. Doing so compromises learnings around estimation.

7. Lean Management

7.1. Seeks to eliminate any waste of time, effort or money by identifying each step in a business process and then revising or cutting out steps that do not create value.

7.2. Guiding principles for lean management

7.2.1. Defining value from the standpoint of the end customer.

7.2.2. Identifying each step in a business process and eliminating those steps that do not create value.

7.2.3. Making the value-creating steps occur in tight sequence.

7.2.4. Repeating the first three steps on a continuous basis until all waste has been eliminated.

7.3. The 5 Basic Lean Principles (create a stable workflow based on actual customer’s demand)

7.3.1. Identify Value

7.3.2. Value Stream Mapping

7.3.3. Create Continuous Workflow

7.3.4. Create a Pull System

7.3.5. Continuous Improvement

7.4. Benefits of Lean Management

7.4.1. Focus

7.4.1.1. By applying Lean, you will be able to reduce waste activities. Therefore, your work force will be focused on activities that bring value.

7.4.2. Improving productivity & efficiency

7.4.2.1. When employees are focused on delivering value, they will be more productive and efficient, because they won’t be distracted by unclear tasks.

7.4.3. Smarter process (pull system)

7.4.3.1. By establishing a pull system, you will able to deliver work only if there is actual demand. Which leads to the next one.

7.4.4. Better use of resources

7.4.4.1. When your production is based on actual demand, you will be able to use only as many resources as needed.