Roadmap221 words
Unit 1 — Processes and communications — roadmap
Unit 1 — Design and implement processes and communications
Exam weight: 10–15% · 3 topics · 17 learning objectives
What this unit is really about
Making work visible and traceable, and measuring the system rather than the people in it.
| Topic | Objectives | Core idea |
|---|---|---|
| 1.1 Traceability and flow of work | 4 | The chain: work item → commit → PR → build → test results → release |
| 1.2 Metrics and queries | 7 | Lead time includes the queue; cycle time does not |
| 1.3 Collaboration and communication | 6 | Docs and notifications that people actually read |
The three things to carry
AB#123links a commit to an Azure Boards work item — and the whole traceability chain depends on a human writing it, so enforce it with a branch policy.- Lead time vs cycle time. Short cycle + long lead = an overloaded team, not a slow one.
- Alert and notify on what needs a decision. Volume without signal gets filtered wholesale, taking the important messages with it.
Where it connects
Feature flags (3.4) are what make GitHub Flow viable for multi-cycle work. Published test results (3.2) are what make a build count as evidence. Pipeline health metrics reappear in 3.6.