Product Management is excluded from Continuous Exploration on the 911 CAD/RMS integration ART, leaving engineers to guess dispatcher needs. What CDP practice should the RTE restore?
Select an answer to reveal the explanation.
Short Explanation
Engineers guessing what a 911 dispatcher needs is how you ship a radio stack nobody can use on a call. Continuous Exploration is Product Management's sensing job—needs and hypotheses—before the ART builds. Leave PM out and the pipeline starts in the wrong place.
Full Explanation
Continuous Exploration includes Product Management so customer needs and hypotheses are sensed before the ART builds. When Product Management is excluded from Continuous Exploration on a 911 CAD/RMS integration ART and engineers guess dispatcher needs, the RTE should restore PM participation in sensing. Restricting Continuous Exploration to the System Architect so dispatchers never influence the backlog removes the product voice. Moving all exploration to a closed steering committee after coding has started arrives too late. Replacing Product Management with a CAD vendor statement of work and skipping sensing locks the ART to vendor assumptions. 911 dispatcher needs must enter Continuous Exploration through Product Management; vendor SOWs and architect-only sensing leave public-safety gaps in the backlog. Exam caveat: architects and engineers contribute strongly to exploration; the failure mode is excluding Product Management entirely. Operational check: schedule joint discovery with dispatchers, Product Management, and architects, and capture resulting hypotheses on the Program Backlog before large CAD/RMS builds. Verify exploration outputs become backlog items with PM owners before large CAD/RMS builds start.