A public-health clinic check-in Increment meets the Definition of Done, but the health officer wants to wait two months to batch a big launch. What should the Product Owner ensure about the Increment itself?
Select an answer to reveal the explanation.
Short Explanation
Releasable is a quality of the Increment, not a calendar appointment. Think of a fire extinguisher that is ready even if nobody pulls the pin today. The health officer can wait to launch; the Increment still has to be fit to go.
Full Explanation
Each Increment should be a usable, Done, potentially releasable step toward the Product Goal. When a public-health clinic check-in Increment meets the Definition of Done but the health officer wants to wait two months to batch a big launch, the Product Owner should ensure the Increment itself is potentially releasable now so the business can choose to release when value and risk say so. Readiness to release and the act of releasing are separate; quality must not wait on the marketing calendar.
Keeping it unreleasable until the marketing launch date even if Done conflates release timing with unfinished quality. Omitting privacy and accessibility checks because release is months away recreates an undone clinic product. Holding work in a hardening environment until a release train is funded parks undone quality behind a funding ritual.
Clinic launches can wait; privacy and accessibility readiness of a Done Increment cannot wait on a marketing calendar.
Exam caveat: PSPO II potentially releasable Increments remain Done regardless of when the organization chooses to launch.
Operational check: confirm privacy and accessibility are in Done now, keep the check-in Increment releasable, and treat the two-month wait as a release decision—not a license to leave quality incomplete.