Agile Masterclass: Agile for Project Management - Definition of Done in Kanban

The video tutorial emphasizes the importance of clearly defining 'done' for tasks and steps in a Kanban system. It explains how defining 'done' ensures quality at each step and discusses the pull-based nature of Kanban, where tasks move only when the next team is ready. The tutorial also covers work-in-progress (WIP) limits and suggests not having separate limits for sub-columns. It highlights best practices for implementing 'done' rules, such as documenting them on the Kanban board and having team members verify compliance. The lecture concludes by stressing team accountability for quality delivery.

Why is it important to define 'done' for each step in a task management process?

• To ensure the task is completed quickly

• To maintain quality at each step

• To reduce the number of tasks

• To increase the workload of developers

In a Kanban system, when does a task move to the testing team?

• When the task is marked urgent

• When the testing team pulls it

• When the manager approves

• When the developer finishes coding

What is the general practice regarding work-in-progress limits in Kanban?

• Limits only for the 'done' column

• Separate limits for each sub-column

• No limits at all

• A single limit for the entire step

What is a recommended practice for ensuring 'done' rules are followed?

• Assigning a single person to check all tasks

• Writing the rules on notes and placing them on the Kanban board

• Only checking tasks at the end of the project

• Ignoring the rules if the task is urgent

How can a team ensure accountability for the quality of delivery?

• By using automated tools only

• By having team members check each other's work

• By assigning all tasks to one person

• By setting strict deadlines