Domain 6 – Stakeholder Communication & Lifecycle Management (14%)

5 lessons, each ending with a practice scenario (Pro)

Log in to save your progress.

1. ✓6.1 — Structured Discovery and Requirement GatheringThe request is not the requirement. Discovery finds the problem behind the request. Six Outputs Discovery Must Produce: Business problem with measured baseline — hours, error rates, backlog, revenue at risk; Real workflow (including workarounds); Output the system must produce (fixes task shape); Consequence when that output is wrong + thresholded, owned success criteria; Data — what exists, quality, ownership, lawful basis; Constraints and accountable decision-maker.Scenario: Pro
2. ✓6.2 — Communicating Architectural Decisions and Trade-offsSimplifying past the point of truth is not translation. Say the Error Rate Out Loud: State the rate, the population, and the handling path for residual errors. A demo is a sample from the favourable tail — never a substitute for the measured rate.Scenario: Pro
3. ✓6.3 — Expectation Alignment and Service-Level CommitmentsEngineer first, then promise. Never the reverse. Anatomy of a Defensible Commitment (Six Elements): Metric — what is measured and how; Percentile or threshold — means conceal the tail; Measurement point — where the clock starts and stops; Window — over what period compliance is assessed; Population — who and what it covers (defined before measurement); Breach behaviour — what happens when it is missed.Scenario: Pro
4. ✓6.4 — Documentation and Implementation GuidanceA handover pack transfers judgement, not history. Test for every page: does it change what a competent stranger would do?Scenario: Pro
5. ✓6.5 — Supporting the Lifecycle PhasesPhases are gated by outputs, not dates. The architect’s job does not end at deployment. Phase Outputs: Discovery, Design, Build & validate, Handoff, Operate & monitor, Iterate.Scenario: Pro