Delivery & Execution

Delivery & Execution is the work of turning intent into shipped, reliable software, predictably. Good intentions meet their constraints here: limited time, shifting requirements, a finite number of people, and the plain difficulty of estimating software. The domain carries 20% of every examination: 12 questions on EMA-I, 15 on EMP-II and 18 on EME-III. Its five competencies are listed below with the questions each carries at each level, and the Exam Content Outlines give the proficiency indicators.

Each competency in this domain is about managing under uncertainty. Strong managers do not promise a certainty they cannot deliver. They build predictability from sequencing, honest forecasting, visible risk, owned reliability and the lightest structure that works. The examinations consistently reward the option that surfaces a trade-off or a truth over the one that makes this quarter look good. So the cost of a yes is named instead of absorbed, a range is given in place of a guessed date, an incident is restored before anyone understands it, a masked slip is met with ground truth, and a ceremony is pruned instead of defended.

At team scope you run one team's delivery directly. At organisational scope you run the system between teams: the shared bottleneck, the commitment that depends on four teams, the incident that spans three, the dependency nobody confirmed, the standard at the seam. There the truthfulness of status becomes the thing you manage. At executive scope you build the organisation's execution operating system, meaning the portfolio, the planning cadence, a reliability trend that someone owns, and the information flows that let dozens of teams deliver without you in the room. The general pattern is in How Judgment Scales; each unit's scaling note places its own competency on it.

Start with DE-1 Prioritisation under constraint, since everything else is sequenced against it. DE-2 Estimation, planning, and honest commitments follows, because a commitment is a promise about a sequence. DE-4 Managing scope, risk, and dependencies across workstreams is the companion to both. It covers the dependencies and risks that widen a range and re-order a queue, and it holds the domain's treatment of status that has stopped being true. DE-3 Reliability, incident response, and operational ownership stands somewhat apart and can be read on its own. Read DE-5 Designing how work flows last: it describes the system the other four run inside, and it holds the domain's contested ground on AI-assisted work.

Delivery relies on Strategy & Vision to say what the sequence is for, through SV-1 Engineering strategy for the strategy, SV-3 Roadmapping for the roadmap and SV-5 Engineering metrics and measurement for measuring outcomes in place of motion. It relies on Technical Judgment for the quality floor, TJ-3 Code review and quality standards, and for the governance of AI assistance, TJ-5 AI-assisted engineering. The costly right call, when the error budget is inconvenient or someone asks for a forecast to be shaded, is CC-5 Values, integrity, and ethical judgment under pressure. When boundary friction keeps recurring, the structure it points at is SV-6 Organisational design and leading change.