A parking-permit renewal story is ‘almost coded’ but fails its acceptance tests. What is the correct interpretation of success?
Select an answer to reveal the explanation.
Short Explanation
Almost doesn’t count—like a bridge that’s ‘almost’ finished but still has a missing span. If acceptance tests fail, the story isn’t done. Keep it open until the checks pass.
Full Explanation
A parking-permit renewal story that is "almost coded" but fails its acceptance tests is not successful completion; failing acceptance means the story remains incomplete. Adaptive success is measured against agreed acceptance criteria and quality agreements, not against effort expended. Civic users should not be told the renewal path works when tests show it does not, and false Done status corrupts burndown transparency and release forecasts used by permitting leadership.
Treating it as successful completion because developers spent the estimated hours fails conceptually because hours burned are input effort, not evidence that acceptance criteria passed. Marking it done if the Sprint ends tonight even with failing tests fails because the calendar boundary does not rewrite test results or redefine Done. Moving it to Done and opening a separate "nice-to-have" bug that nobody tracks fails because that hides incomplete acceptance inside false Done status and often loses the defect in an unowned queue.
Exam caveat: Failed acceptance equals incomplete—do not equate hours, sprint end, or untracked bugs with successful completion on the CAPM adaptive success questions. Operational check: keep the renewal story out of Done on the board, fix until acceptance passes and Definition of Done is met, update status honestly for the Sprint Review, and only then demonstrate the working renewal path to permitting stakeholders.