Lecture: 6 Kanban Flashcards
Motivation for Kanban
Software project manager
- Have a hard time setting clear priorities in their field and thus making corresponding decisions
- They do not understand how their team works and why it does not “work” the way they want it to
- They are frustrated because the team does not manage to “work according to plan”
Project team
- The members are overwhelmed and stressed
- The development takes longer than planned because the team members continuously have to justify their actions to the management and are interrupted
- The quality of the finished software is insufficient
- They do not understand why the management makes such significant changes to the direction of the work and wants something different every day
What is kaizen?
- Change the process
- Measurement analysis
- Recognize potential
- Eleminate redundancy
- Muda, Mura and Muri (Japanese for “waste” or “scrap”)
- Muda is every activity or process that does not add value to the production (Tailoring)
- Mura refers to the waste resulting from inhomogeneity and inconsistency
- Muri is waste resulting from misusing resources (workers, machines, etc.)
Muda, Mura, Muri
Muda, Mura and Muri (Japanese for “waste” or “scrap”)
- Muda is every activity or process that does not add value to the production (Tailoring)
- Mura refers to the waste resulting from inhomogeneity and inconsistency
- Muri is waste resulting from misusing resources (workers, machines, etc.)
5 core principles of kanban
- Visualize the current workflow
- Kanban board
- Limit the work in progress (WIP)
- WIP limit on kanban board
- Measure and optimize the flow
- Lead time: clock starts when request is made and ends when delivered
- Cycle time: clock starts when work begins
- Make policies explicit
- Definition of done
- Work together to optimize the process in small steps (Kaizen)
- process tailoring
Properties of Kanban (1/3)
Kanban (method) stands for
- Transparency
- Optimization
- Personal responsibility
Kanban does not solve problems, it simply makes them visible!
Kanban begins with the current state and process of a system
- Current system development, job titles and process is respected
Kanban is evolution and not revolution
- • Kaizen
- • Kanban always considers the overall picture
Properties of Kanban (2/3)
Kanban requires to rethink traditional management
- Multitasking”Stop starting, start finishing”
- Push without limit Pull with limit
- 100% capacity utilization “Slack Time” is wanted!
Kanban focuses on people and not on mechanics
- • Kanban is team sport
Kanban does not favor a specific management approach!
Kanban can be combined with different approaches
- Traditional: Waterfall Model, V-Modell XT, Boehms Spiral Model, Unified Process…
- Agile: ScrumScrum-ban
Kanban enables
- Incremental process tailoring (at runtime throughout the process)
- Process Change / Improvement Management
A Kanban system is an example of a
Select one or more:
a. Pull system
b. Drum-Buffer-Rope system
c. Push system
a
What should the Kanban board reflect?
Select one or more:
a. The desirable process of the team
b. It depends
c. Official process of the team
d. What the team actually does
d
How does a WiP reducing affect the lead time?
Select one or more:
a. Shortens lead time
b. Has no effect
c. Lengthens lead time
a
Kanban changes
Select one or more:
a. Roles and responsibilities
b. Working practices
c. None of the mentioned
d. Job titles
c
Kanban is an approach that drives change by
Select one or more:
a. Changing the workflow
b. Implementing a new process
c. Changing as much as possible
d. Optimizing your existing process
d
