Kanban overview in Software Engineering - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to name the main visual element used in Kanban.

Software Engineering

The main visual element in Kanban is called a [1].

Drag options to blanks, or click blank then click option'

AGantt chart

BPie chart

CFlowchart

DKanban board

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing Kanban board with other chart types like Gantt or pie charts.

The Kanban board is the primary tool used to visualize work and workflow in Kanban.

2fill in blank

medium

Complete the sentence to describe the purpose of Kanban columns.

Software Engineering

Kanban columns represent different [1] in the workflow.

Drag options to blanks, or click blank then click option'

Astages

Bteam members

Cprojects

Ddeadlines

Attempts:

3 left

💡 Hint

Common Mistakes

Thinking columns represent people or projects instead of workflow stages.

Columns in Kanban boards show the stages that work items pass through, such as To Do, In Progress, and Done.

3fill in blank

hard

Fix the error in the statement about Kanban limits.

Software Engineering

Kanban uses [1] to limit the number of tasks in each column to avoid overload.

Drag options to blanks, or click blank then click option'

Awork-in-progress limits

Btime tracking

Cbudget caps

Dteam size limits

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing WIP limits with time or budget constraints.

Work-in-progress (WIP) limits restrict how many tasks can be in a column at once to improve flow and focus.

4fill in blank

hard

Fill both blanks to describe Kanban cards and their movement.

Software Engineering

Each task is represented by a [1] that moves from the [2] column to the Done column.

Drag options to blanks, or click blank then click option'

Acard

Bemail

CTo Do

Dchat message

Attempts:

3 left

💡 Hint

Common Mistakes

Using communication tools like email or chat instead of cards.

Kanban cards represent tasks and move through columns like To Do, In Progress, and Done to show progress.

5fill in blank

hard

Fill all three blanks to complete the Kanban workflow description.

Software Engineering

Work items start in the [1] column, move through [2], and finish in the [3] column.

Drag options to blanks, or click blank then click option'

ABacklog

BIn Progress

CDone

DReview

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing Review with Done or Backlog with In Progress.

Tasks typically start in Backlog, move through In Progress, and end in Done on a Kanban board.

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