Kanban Board

Correct Answer: Implement a Work In Progress (WIP) limit to encourage the team to focus on completing tasks before taking on new ones.

Introducing a WIP limit helps the team manage flow, reduce context-switching, and improve focus on completing tasks, thereby indirectly helping with prioritization by limiting work in progress and emphasizing completion. Organizing daily stand-ups solely for reordering tasks may not directly address the root cause of prioritization issues and could lead to time inefficiency. Assigning a 'Priority Manager' role centralizes decision-making, which conflicts with the team-driven approach of Scrum. Implementing a complex prioritization algorithm could add unnecessary complication and obscure the direct responsibility of the team to manage and understand their own workflow.

Correct Answer: Visualize work to optimize the flow

While prioritizing tasks, enhancing collaboration, and measuring productivity are important aspects within a Scrum context, the primary purpose of using a Kanban board is to visualize work to optimize the flow. This visualization helps teams to see the progress of work and identify any bottlenecks in their process, aiming for continuous improvement.

Correct Answer: Ensure a clear Definition of Done (DoD) is established and followed, and review tasks during the sprint review

The correct approach is to establish and adhere to a clear Definition of Done (DoD) for all tasks. This ensures that when a task is marked as 'Done', it truly meets all necessary criteria. Additionally, tasks should be reviewed during the sprint review, which occurs immediately after the sprint. This practice prevents overlooking potential issues and maintains the integrity of the 'Done' column. By following a strict DoD and conducting thorough sprint reviews, the team can avoid the accumulation of questionable 'Done' tasks and address any concerns promptly.