A public-works inspection-app team finishes a half-built offline-sync module that inspectors cannot use and that does not add to the previous Increment. Leadership wants it shown as this Sprint's Increment. What should the Product Owner do?
Select an answer to reveal the explanation.
Short Explanation
An Increment you cannot hand an inspector is leftover lumber, not a finished room. Additive means it stacks on what already works. Do not pretend a half-built sync module is the Increment.
Full Explanation
Each Increment is a concrete stepping stone toward the Product Goal and must be usable, meet the Definition of Done, and be additive to all prior Increments. When a public-works inspection-app team finishes a half-built offline-sync module inspectors cannot use and that does not add to the previous Increment, leadership wanting it shown as this Sprint's Increment must be refused. Incomplete work may exist, but it is not the Increment and must not be labeled Done.
Accepting the module as the Increment so Sprint Review has something to demo hides risk behind demo theater. Relabeling the half-built module a spike Increment and marking it Done invents a Done category for unfinished work. Splitting the module across two Product Backlogs so each half can be called complete papers over lack of usability with accounting tricks.
Inspectors in the field cannot use a half-built sync story; calling it an Increment misleads leadership about readiness.
Exam caveat: PSPO II Increments are usable and additive; half-built modules are not Increments regardless of leadership demo pressure.
Operational check: show only Done, usable, additive inspection-app work at Review; keep the unfinished sync module transparent as incomplete work on the Product Backlog.