Answering: “When using Scrum, can a Scrum Team use Continuous Delivery?”

Table of Contents

Understanding Continuous Delivery in Scrum

Continuous Delivery (CD) is a practice where code changes are automatically prepared for release to production. This approach allows teams to deploy small, incremental updates to their products frequently. Scrum, as a framework, does not conflict with Continuous Delivery and can be effectively combined with it to enhance the delivery of value.

Exam Question

When using Scrum, can a Scrum Team use Continuous Delivery?
(choose the best answer)
A. No, because the Product Owner may not be available each time a PBI is done and the Product Owner has to decide if it should be released.
B. No, because the increment has to be approved at the Sprint Review before it can be released, and a 2-week Sprint would not be considered continuous.
C. No, because before releasing an Increment it first has to fulfill the Definition of Done.
D. Yes, there is nothing in Scrum that conflicts with Continuous Delivery.
E. No, because Stakeholders may have already seen the new features and the Sprint Review will be meaningless.

Correct Answer

D. Yes, there is nothing in Scrum that conflicts with Continuous Delivery.

Explanation

Correct Answer

D. Yes, there is nothing in Scrum that conflicts with Continuous Delivery:
Scrum is a framework that allows teams to adapt and improve continuously. There are no restrictions within Scrum that prevent a team from implementing Continuous Delivery. In fact, CD can be a powerful complement to Scrum, allowing teams to release increments frequently and get feedback more quickly. Continuous Delivery ensures that every change is production-ready, which aligns well with Scrum’s iterative and incremental approach.

Why the Other Options Are Less Appropriate

A. No, because the Product Owner may not be available each time a PBI is done and the Product Owner has to decide if it should be released:
While the Product Owner is responsible for deciding the release timing, Continuous Delivery can still be used. The team can set up a process where the Product Owner reviews and releases increments at appropriate times without being a bottleneck.

B. No, because the increment has to be approved at the Sprint Review before it can be released, and a 2-week Sprint would not be considered continuous:
The Sprint Review is an opportunity to inspect the Increment and adapt the Product Backlog. However, Scrum does not mandate that releases happen only at the Sprint Review. Releases can happen anytime during the Sprint if the increment is ready and meets the Definition of Done.

C. No, because before releasing an Increment it first has to fulfill the Definition of Done:
The Definition of Done must be met before an increment is released, but this does not conflict with Continuous Delivery. CD ensures that only increments meeting the Definition of Done are automatically prepared for release, allowing for frequent and reliable deployments.

E. No, because Stakeholders may have already seen the new features and the Sprint Review will be meaningless:
The Sprint Review is not just about showing new features; it’s about inspecting the Increment and adapting the Product Backlog based on feedback. Continuous Delivery can actually enhance the Sprint Review by providing more frequent feedback and allowing the team to adapt more quickly.

Relevance to the PSD Exam

Understanding how Continuous Delivery fits within the Scrum framework is important for the PSD exam as it highlights the flexibility and adaptability of Scrum. It also shows how modern development practices can be integrated with Scrum to enhance the delivery of value.

Key Takeaways

  • Scrum and Continuous Delivery: Scrum does not conflict with Continuous Delivery, and both can be combined to deliver frequent, incremental updates.
  • Flexibility: Scrum allows for flexibility in release timing, and teams can choose to release increments as soon as they are ready.

Conclusion

Continuous Delivery is a valuable practice that complements Scrum by enabling teams to release increments frequently and with confidence. By integrating Continuous Delivery with Scrum, teams can enhance their ability to deliver value and respond to feedback more quickly. For more information on preparing for the PSD exam, visit our Professional Scrum Developer PSDâ„¢ Exam Prep.

Sign up for more exam tips and discounts



You cannot copy content of this page

$35 Exam Preps

Sale Ending Soon

Day
Hour
Min
Sec
Offer Expired
Add Your Heading Text Here