Releasing in Scrum with Kanban
When integrating Kanban with Scrum, teams have the flexibility to release work multiple times during the Sprint, depending on their workflow and the readiness of their increments.
Exam Question
True or False: When using Scrum with Kanban you can release multiple times during the Sprint.
A. True
B. False
Correct Answer
A. True
Explanation
Correct Answer
A. True:
When using Scrum with Kanban, teams can release work multiple times during the Sprint. The integration of Kanban practices into Scrum encourages a continuous flow of work, allowing increments to be released as soon as they meet the Definition of Done. This flexibility enables teams to deliver value more frequently and respond more rapidly to changes or new requirements. Scrum with Kanban supports releasing at any point during the Sprint whenever it makes sense for the team and stakeholders.
Key Points on Releasing in Scrum with Kanban
- Continuous Delivery: The use of Kanban in Scrum promotes a continuous delivery model, where completed work items can be released as soon as they are ready, without waiting for the end of the Sprint.
- Flexibility: Teams have the autonomy to decide when to release increments. This could be multiple times during a Sprint, depending on the workflow and the urgency or value of the work items being delivered.
- Incremental Value Delivery: Releasing multiple times during a Sprint allows for the incremental delivery of value, ensuring that stakeholders receive benefits from the work as soon as possible.
Relevance to the PSK I Exam
Understanding that Scrum with Kanban allows for multiple releases during a Sprint is important for the PSK I exam. It demonstrates knowledge of how to effectively manage and deliver work using the combined practices of Scrum and Kanban.
Key Takeaways
- Scrum with Kanban supports releasing work multiple times during a Sprint, offering flexibility in delivering increments.
- Continuous delivery is a key benefit of integrating Kanban with Scrum, enabling teams to release as soon as work is ready.
- The ability to release multiple times during a Sprint ensures that stakeholders receive value more frequently.
Conclusion
When using Scrum with Kanban, teams are not limited to releasing work only at the end of the Sprint. They have the flexibility to release multiple times during the Sprint, aligning with the principles of continuous delivery and incremental value delivery.

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: In a flow-based system, the number of tasks is not necessarily limited, rather the amount of value-generating work items is limited.
- True or False: The main role of WIP Aging is to help identify flow bottlenecks; where work may be impeded or constrained.
- Little’s Law is extremely valuable for directly predicting the future because it gives us a measure of what happened in the past?
- The team needs to work on a high priority urgent unplanned item, but they are at their WIP limit.
- Who owns the Kanban board in the Sprint Backlog?
