Field inspectors want offline mode on a code app, but a field-network study is still incomplete. What release logic best applies?
Select an answer to reveal the explanation.
Short Explanation
Don’t weld on an offline kit before you know how bad the dead zones are. Park that component until the network study lights the map—then build what the evidence says you need.
Full Explanation
When field inspectors want offline mode on a code app but a field-network study is still incomplete, release logic should defer the offline-mode component until the study provides evidence that shapes requirements and release readiness. Evidence-based deferral prevents building the wrong offline behavior and wasting civic capacity on guesses that fail in low-connectivity neighborhoods. Desire alone does not make a component release-ready.
Shipping offline mode immediately with guessed requirements fails conceptually because guessing field-network constraints invites defects, data-loss risk, and rework. Canceling the entire product until every future study for any feature is finished fails because one incomplete study should not halt all unrelated value delivery inspectors can use now. Treating offline mode as release 1 mandatory work regardless of evidence gaps fails because mandatory labeling cannot replace missing requirements evidence from the study.
Exam caveat: Defer components that lack critical discovery evidence; do not equate stakeholder desire with readiness. Operational check: park offline mode behind the field-network study milestone, deliver other ready code-app value in the interim, and reopen offline requirements only when study evidence is available to shape acceptance criteria and tests.