Citizen reports about broken permit uploads are reviewed weekly and turned into backlog items for the next release. What continuous-delivery practice is this?
Select an answer to reveal the explanation.
Short Explanation
Feedback loops turn citizen "upload broken" reports into next-release work. Shipping on a calendar while ignoring ops signals is flying without instruments.
Full Explanation
A feedback loop in continuous delivery ties operational and citizen signals back into the backlog so delivery improves from real outcomes rather than calendar alone. Reviewing citizen reports about broken permit uploads weekly and turning them into backlog items for the next release is that loop: production pain becomes prioritized, tracked work for the permits engineering team.
Deleting production metrics so feedback never reaches developers severs the loop and guarantees repeated surprises on the same upload path. Shipping only on a fixed calendar with no ops or citizen input is calendar-driven delivery without learning from municipal service reality. Disabling the permits portal until the next fiscal year avoids the symptom by denying service rather than improving the broken upload path residents need.
Exam caveat: feedback items still need triage, severity, privacy handling, and product ownership—raw citizen tickets are inputs, not automatic scope commits into every sprint. Operational check: maintain a weekly review of permit-upload incidents and tickets, create tracked backlog stories with owners, and verify subsequent releases reduce upload-failure rates measured in production.