Mapping Stakeholder Activities to Lifecycle Phases for the CCAR-P Exam

Placing each activity on the frame

The five-phase deployment lifecycle is the frame; this knowledge point places each stakeholder activity on it. The CCAR-P exam treats the mapping as an understand-level skill, because knowing the phases is not the same as knowing which phase a given piece of work belongs to. Getting the placement right is what turns five separate skills into one connected motion and lets you judge when a phase is complete enough to move on.

The mapping is specific. Discovery and trade-off framing are the discovery-and-design work. The feedback loop and its governance table are the monitoring-and-iteration work. Documentation for handoff and audit is the handoff-phase work. Entry-point selection and the outcome document close the loop, drawing on every earlier phase's output. Each of these placements has a reason, and each has a common misplacement the exam probes.

Discovery and trade-off framing: discovery and design

Discovery is obviously discovery-phase work, but trade-off framing belongs with it in the discovery-and-design band, because a trade-off presentation defends the design against the constraint set discovery produced. The two are consecutive steps in setting and defending requirements, not separate lifecycle stages. Placing trade-off framing here keeps it tethered to the constraints it exists to serve rather than treating it as a free-floating communication exercise.

The feedback loop: monitoring and iteration, ongoing

The feedback loop and its governance table are the monitoring-and-iteration work, and the word to hold onto is ongoing. The loop is not a one-time setup task you complete at launch and forget; it is the continuous activity of watching signals, deciding what matters, acting, and reviewing, across the whole life of the deployment. Mapping it to a single setup moment is a specific error, because it hides the fact that monitoring and iteration are recurring phases, not a checkbox ticked before go-live.

Documentation: the handoff deliverable

Documentation for handoff and audit is the handoff-phase deliverable, and this is the placement candidates most often get wrong. It is tempting to file documentation under design, because it describes the design, but its function is to transfer the system to its next owners and to satisfy an auditor, which is handoff work. Treating documentation as a design-phase activity underplays it as note-taking, when it is actually the artifact that gates the transition into monitoring, as covered in lifecycle phase-gating. The three readers of architecture documentation are all handoff-and-beyond readers, which confirms the placement.

Entry-point selection and the outcome document close the loop

The final band is the closing work: entry-point selection and the outcome document. These draw on every earlier phase, the discovery constraints, the design trade-offs, the governance table, and the documentation, to route the live system correctly and to make its value legible beyond the build. They close the loop because they turn the completed work into something reusable and defensible, and they cannot be done well without the outputs of everything before them.

What the exam trips candidates on

The first trap is placing documentation work in the design phase instead of treating it as the handoff-phase deliverable. The exam rewards mapping documentation to handoff, because that is what its readers and its gating function reveal it to be.

The second trap is treating the feedback loop as a one-time setup task rather than the ongoing monitoring-and-iteration activity. The exam credits recognising the loop as continuous work spanning two phases, not a launch checklist item.

Common misreadings to avoid

How this shows up on the exam

Questions describe a stakeholder activity and ask which lifecycle phase it belongs to, or present a mapping and ask what is misplaced. The reliable reading is that discovery and trade-off framing are discovery-and-design, the feedback loop is ongoing monitoring-and-iteration, documentation is handoff, and entry-point selection with the outcome document is the closing work drawing on every prior phase.

This builds on the five-phase deployment lifecycle and feeds the closing activities of entry-point-responsibility mapping and the outcome document as a closing artifact. The placements it establishes are exactly what lifecycle phase-gating uses to judge readiness.