Kanban overview in Software Engineering - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Kanban Board Columns

In a typical Kanban board, what does the column labeled "In Progress" represent?

A Tasks that have been rejected or removed

B Tasks that have been completed and are ready for review

C Tasks that have not yet been started

D Tasks that are currently being worked on

💡 Hint

Think about the flow of work from start to finish.

The "In Progress" column shows tasks that team members are actively working on. It is the middle stage between "To Do" and "Done".

📋 Factual

intermediate

Kanban Work In Progress Limits

What is the main purpose of setting Work In Progress (WIP) limits in Kanban?

A To increase the number of tasks started simultaneously

B To assign tasks to specific team members

C To restrict the number of tasks being worked on at the same time

D To prioritize tasks based on deadlines

💡 Hint

Consider how limiting tasks helps manage focus and flow.

WIP limits help prevent overloading the team by restricting how many tasks can be in progress at once, improving focus and flow.

🔍 Analysis

advanced

Identifying Bottlenecks in Kanban

Which of the following scenarios best indicates a bottleneck in a Kanban process?

A Tasks move quickly from "To Do" to "Done" without delay

B The "In Progress" column has many tasks waiting longer than usual

C The "Done" column is empty at the end of the day

D New tasks are added to the "To Do" column daily

💡 Hint

Look for where tasks pile up and slow down.

A bottleneck occurs when tasks accumulate in one stage, such as "In Progress," causing delays and reducing flow efficiency.

❓ Comparison

advanced

Kanban vs Scrum Focus

Which statement best describes a key difference between Kanban and Scrum?

A Kanban focuses on continuous flow, Scrum focuses on time-boxed sprints

B Kanban uses fixed-length iterations, Scrum does not

C Scrum limits work in progress, Kanban does not

D Scrum does not use boards, Kanban always uses boards

💡 Hint

Think about how work is organized over time in each method.

Kanban emphasizes continuous flow of work without fixed time periods, while Scrum organizes work into fixed-length sprints.

❓ Reasoning

expert

Effect of Removing WIP Limits in Kanban

What is the most likely effect of removing Work In Progress (WIP) limits from a Kanban system?

A Work may pile up causing delays and reduced overall efficiency

B Tasks will flow faster because more work can be done simultaneously

C Team members will focus better on fewer tasks at a time

D The Kanban board will automatically reorder tasks to optimize flow

💡 Hint

Consider what happens when too many tasks are started at once.

Without WIP limits, too many tasks can be started simultaneously, causing bottlenecks and slowing overall progress.

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