Sprint Goal in a Scrum Team Using Kanban
Incorporating Kanban practices within a Scrum framework involves understanding how key elements like the Sprint Goal are maintained or adjusted.
Exam Question
True or False: A Scrum Team using Kanban does not need to craft a Sprint Goal during Sprint Planning. They can instead create one ‘on-demand’ as new work flows into the Sprint Backlog.
A. True
B. False
Correct Answer
B. False
Explanation
Correct Answer
B. False:
Even when using Kanban practices within a Scrum framework, the Scrum Team should still craft a Sprint Goal during Sprint Planning. The Sprint Goal provides direction and focus for the team and ensures that all team members are aligned with the objectives of the Sprint. Creating a Sprint Goal ‘on-demand’ as new work flows into the Sprint Backlog would undermine the structured planning and focus that the Sprint Goal provides.
Importance of the Sprint Goal
- Focus and Direction: The Sprint Goal helps the team stay focused on a common objective, ensuring that their efforts are aligned towards achieving it.
- Guidance for Decision-Making: It serves as a guiding star for the team, helping them make decisions about what work to prioritize and how to handle challenges during the Sprint.
- Consistency with Scrum Framework: Maintaining the practice of crafting a Sprint Goal during Sprint Planning ensures that the team adheres to the core principles of Scrum, even when integrating Kanban practices.
Integration of Kanban with Scrum
- Flow Management: Kanban practices can be used to manage the flow of work within the Sprint, such as visualizing tasks and limiting Work in Progress (WIP).
- Sprint Planning: Despite using Kanban, the structure of Scrum events, including Sprint Planning and the creation of a Sprint Goal, remains essential to provide direction and maintain the integrity of the Scrum framework.
Relevance to the PSK I Exam
Understanding the necessity of maintaining a Sprint Goal even when integrating Kanban practices is crucial for the PSK I exam. It demonstrates knowledge of how to effectively blend Scrum and Kanban practices while adhering to the core principles of both methodologies.
Key Takeaways
- The Scrum Team should always craft a Sprint Goal during Sprint Planning, regardless of integrating Kanban practices.
- The Sprint Goal provides essential focus and direction for the team throughout the Sprint.
- Integrating Kanban with Scrum should enhance, not replace, the core elements of the Scrum framework.
Conclusion
A Scrum Team using Kanban should continue to craft a Sprint Goal during Sprint Planning to ensure focus, direction, and alignment with Scrum principles.

Get ready for the official PSK I exam
115 PSK I practice questions, each with an in-depth explanation like the one above.
- Practice Mode: study at your own pace and choose the test length.
- Mock Exam Mode: 45 random questions in 60 minutes, like the real exam.
$29 is ScrumPrep's one-time price. The official PSK I exam fee ($200) is paid separately to Scrum.org.
More PSK I exam questions
- True or False: The Scrum framework already contains elements that create a pull system.
- What is the potential benefit of limiting Work in Progress (WIP)?
- True or False: When the Developers add Kanban to Scrum, the way they use the Sprint Goal during their Daily Scrum changes.
- When using Kanban in a Scrum environment, some resistance may be found to introducing Work in Progress (WIP) Limits. What is an alternative to introducing WIP Limits in Kanban?
- True or False: Work Item Age is a leading indicator for the length of the Scrum Team’s feedback loop for that (in progress) item.
