Kanban overview in Software Engineering - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Kanban in software engineering?

Kanban is a visual method to manage work by showing tasks on cards and moving them through columns that represent stages of work, helping teams see progress and limit work in progress.

beginner

What are the main columns typically found on a Kanban board?

Common columns are: To Do (tasks to start), In Progress (tasks being worked on), and Done (completed tasks). These show the flow of work from start to finish.

intermediate

Why does Kanban limit work in progress (WIP)?

Limiting WIP helps teams focus on finishing tasks before starting new ones, reducing multitasking and improving flow and quality.

beginner

How does Kanban help improve team communication?

Kanban boards make work visible to everyone, so team members can easily see what others are doing, which helps coordinate efforts and spot bottlenecks early.

intermediate

What is a key difference between Kanban and Scrum?

Kanban is continuous flow without fixed time cycles, while Scrum works in fixed-length sprints with planned tasks. Kanban is more flexible and focuses on ongoing delivery.

What does a Kanban board visually represent?

A A list of team members and their roles

B The stages of work and tasks moving through them

C A schedule of meetings and deadlines

D A detailed project budget

Kanban boards show tasks as cards moving through columns that represent stages of work.

Why is limiting work in progress important in Kanban?

A To increase multitasking

B To add more tasks quickly

C To avoid communication among team members

D To focus on completing tasks and improve flow

Limiting WIP helps teams focus on finishing tasks, reducing multitasking and improving efficiency.

Which of these is NOT a typical Kanban board column?

A Planning Meeting

B In Progress

C Done

D To Do

Planning Meeting is not a typical column; Kanban boards focus on task stages like To Do, In Progress, and Done.

How does Kanban differ from Scrum?

A Kanban uses fixed-length sprints

B Scrum uses continuous flow

C Kanban focuses on continuous flow without fixed time cycles

D Scrum does not use boards

Kanban is continuous flow without fixed sprints, while Scrum uses fixed-length sprints.

What benefit does making work visible on a Kanban board provide?

A Improves team communication and spotting bottlenecks

B Hides tasks from team members

C Increases task complexity

D Removes deadlines

Visibility helps team members coordinate and identify problems early.

Explain how a Kanban board helps a team manage their work.

Think about how seeing tasks moving helps the team.

Describe the purpose of limiting work in progress in Kanban and its impact on team productivity.

Why is it better to finish tasks before starting new ones?

Practice

1. What is the main purpose of using a Kanban board in software engineering?

easy

A. To replace all meetings with emails

B. To write code faster using automation

C. To visually track and manage work tasks through different stages

D. To create detailed project budgets

Solution

1. Step 1: Understand Kanban's function

   Kanban is designed to help teams see and manage work visually by moving tasks across stages.

2. Step 2: Identify the correct purpose

   Among the options, only visual tracking and managing tasks matches Kanban's main use.

3. Final Answer:

   To visually track and manage work tasks through different stages -> Option C

4. Quick Check:

   Kanban = Visual task management [OK]

Hint: Kanban is about visualizing work stages [OK]

Common Mistakes:

• Thinking Kanban automates coding
• Confusing Kanban with budgeting tools
• Assuming Kanban replaces communication

2. Which of the following is the correct way to represent a Kanban board?

easy

A. A list of tasks without any columns

B. Columns representing stages with cards for tasks

C. A pie chart showing task percentages

D. A text document listing deadlines

Solution

1. Step 1: Recall Kanban board structure

   A Kanban board uses columns to show stages and cards to represent tasks.

2. Step 2: Match the correct representation

   Only Columns representing stages with cards for tasks describes columns with task cards, which is the standard Kanban format.

3. Final Answer:

   Columns representing stages with cards for tasks -> Option B

4. Quick Check:

   Kanban board = Columns + task cards [OK]

Hint: Kanban boards have columns and cards [OK]

Common Mistakes:

• Confusing Kanban with charts or lists
• Ignoring the column structure
• Thinking Kanban is just a text list

3. Consider a Kanban board with columns: To Do, In Progress, and Done. If a task card moves from 'In Progress' to 'Done', what does this indicate?

medium

A. The task has been completed

B. The task is waiting to be started

C. The task is blocked and cannot proceed

D. The task has been started but not finished

Solution

1. Step 1: Understand column meanings

   'In Progress' means work is ongoing; 'Done' means work is finished.

2. Step 2: Interpret the card movement

   Moving a task from 'In Progress' to 'Done' shows the task is completed.

3. Final Answer:

   The task has been completed -> Option A

4. Quick Check:

   Done column = Completed tasks [OK]

Hint: Done means task finished [OK]

Common Mistakes:

• Confusing 'Done' with 'To Do'
• Assuming 'In Progress' means completed
• Thinking 'Done' means blocked

4. A team using Kanban notices that too many tasks are in the 'In Progress' column, causing delays. What is the best way to fix this problem?

medium

A. Add more columns to the board

B. Start all tasks at once to finish faster

C. Remove the 'Done' column

D. Limit the number of tasks allowed in 'In Progress'

Solution

1. Step 1: Identify the problem

   Too many tasks in 'In Progress' cause bottlenecks and slow progress.

2. Step 2: Apply Kanban principle

   Kanban suggests limiting work in progress (WIP) to improve flow and focus.

3. Final Answer:

   Limit the number of tasks allowed in 'In Progress' -> Option D

4. Quick Check:

   WIP limits reduce delays [OK]

Hint: Use WIP limits to avoid overload [OK]

Common Mistakes:

• Adding columns doesn't reduce task overload
• Removing 'Done' breaks workflow tracking
• Starting all tasks at once causes more delays

5. A software team wants to improve their Kanban board to better handle urgent bugs without disrupting ongoing tasks. Which approach best applies Kanban principles to solve this?

hard

A. Create a separate urgent bug column with a strict WIP limit

B. Add urgent bugs to the 'To Do' column without limits

C. Ignore urgent bugs until current tasks finish

D. Move all tasks to 'In Progress' to speed up work

Solution

1. Step 1: Understand the need for urgent bug handling

   Urgent bugs require quick attention but should not block other work.

2. Step 2: Apply Kanban principles

   Creating a separate column with WIP limits allows focus on urgent bugs without disrupting flow.

3. Step 3: Evaluate other options

   Adding bugs without limits or ignoring them breaks Kanban flow; moving all tasks disrupts focus.

4. Final Answer:

   Create a separate urgent bug column with a strict WIP limit -> Option A

5. Quick Check:

   Separate urgent work + WIP limits = better flow [OK]

Hint: Separate urgent tasks with limits to keep flow smooth [OK]

Common Mistakes:

• Ignoring urgent bugs delays fixes
• Mixing urgent bugs without limits causes overload
• Moving all tasks at once reduces focus