Back to Scrum in Different Contexts

Scrum with Kanban

5 minutes 5 Questions

Scrum with Kanban merges the structured framework of Scrum with the visual management capabilities provided by Kanban. This helps to enhance transparency and deliver products of high quality efficiently. This approach retains the benefits of Scrum's iterative approach while harnessing the benefits …

Test mode:
Start practice test
PSM I - Scrum with Kanban Example Questions

Test your knowledge of Scrum with Kanban

Question 1

As a Scrum Master, you realize that the lead time is increasing each sprint. Additionally, the team comments that they feel overwhelmed by the amount of work. How should you solve the problem using principles of Scrum and Kanban?

Correct Answer: Implement a Kanban system to visualize work, limit Work In Progress (WIP), and ensure flow efficiency by adjusting based on team capacity.

Although all options aim to manage workload and improve efficiency, implementing a Kanban system alongside Scrum practices (sometimes referred to as Scrumban) is the most effective way to address the issue of increasing lead time and team overwhelm. It allows for continuous work flow, visualization of work, and limiting work in progress, which can help balance the workload more effectively than merely redefining goals, simplifying tasks without considering team capacity, or pushing for increased velocity without sustainable practices.

Question 2

You have a mature team using Scrum with Kanban. However, during the sprint retrospective, some team members express frustration towards the length of the sprint review. As the Scrum Master, how might you address this concern?

Correct Answer: Streamline the sprint review process by working with the team to identify key stakeholders and ensure that only the most relevant feedback is solicited.

To address concerns about the length of the sprint review, the focus should be on making the process more efficient and engaging without compromising its purpose. Streamlining the session to involve relevant stakeholders and feedback optimizes the review's value. Introducing a rotating facilitator might make the meetings more engaging but doesn't directly address the issue of length. Adjusting the Sprint Backlog prioritization doesn't necessarily shorten the sprint review; it's more about focusing on efficiency in sprint work. Providing pre-meeting reports could inadvertently extend the duration by encouraging more detailed pre-discussions, which misaligns with the goal of having an interactive and collaborative sprint review.

Question 3

During a Scrum with Kanban, your team is complaining about the constantly shifting priorities, leading to unfinished tasks in every sprint. How as a Scrum Master could you address this issue?

Correct Answer: Engage with the Product Owner to refine and stabilize the product backlog, ensuring a more predictable flow of work for the team.

The correct answer focuses on working with the Product Owner to create a more stable workflow, which addresses the root cause of the issue: constantly changing priorities. Suggesting a more flexible definition of 'Done' could lead to quality issues and does not address the issue of shifting priorities. Implementing a buffer for unforeseen changes might treat the symptom by providing flexibility, but it doesn't address the stability of the backlog. Advocating for a continuous flow model disregards the principles of Scrum, which include sprints as a core element, and may not be feasible for every team or product.

More Scrum with Kanban questions
8 questions (total)
Start 8 question test