4.3. Documenting Adaptive Project Controls
💡 First Principle: "Self-organizing" describes how the team manages its own execution — it does not mean progress is invisible. Adaptive projects use their own set of documented, visible artifacts to track and control work, just not the same artifacts predictive projects use.
| Artifact | What It Shows | Controls What |
|---|---|---|
| Product backlog | All known, prioritized work not yet done | What's next and in what order |
| Burndown chart | Remaining work in the current iteration over time | Whether the team is on pace to finish the iteration's scope |
| Burnup chart | Completed work (and total scope) over time | Overall progress and scope growth across iterations |
| Task/Kanban board | Current status of each work item (to-do, in-progress, done) | Real-time visibility into where work is stuck |
⚠️ Exam Trap: A scenario implying that an adaptive team "doesn't need documentation because it's self-organizing" is describing a misapplication of adaptive principles, not a correct practice. Self-organization governs how decisions get made within the team, not whether progress gets tracked and made visible.
Burndown vs. burnup, and why both exist. A burndown chart shows what's left — a shrinking line toward zero as an iteration's work completes. A burnup chart shows two lines: work completed (climbing) and total scope (which can itself rise if new items get added mid-iteration). This second line matters because it catches a pattern burndown alone hides: a team can be completing work steadily while ALSO falling behind, if scope keeps growing faster than the team can burn it down. A scenario describing stakeholders confused about why "the team keeps finishing work but never seems to catch up" is pointing at scope growth visible only on a burnup chart.
A worked example. A team's Kanban board shows 6 items in the "In Progress" column and only 1 in "Done" three days into a five-day iteration. Without any formal status meeting, this board alone tells a PM or stakeholder that the team may be over-committed or blocked — the visibility comes from the artifact itself, not from someone verbally reporting status. That's the practical meaning of "self-organizing teams still produce documented, visible control" in this subsection's first principle.
Reading a board's patterns, not just its snapshot. Beyond a single moment in time, certain patterns on a task board are worth watching for specifically: one item stuck in "In Progress" far longer than similar items typically take usually signals a hidden blocker, and items piling up in a single column while others sit empty usually signals a bottleneck upstream or downstream of that stage. A steady, even flow across columns, by contrast, is a healthy pattern and not something that needs intervention. The exam expects associate-level practitioners to read these patterns directly off the artifact, without needing anyone to narrate what's happening.
When good artifacts still don't reach a sponsor. A team can maintain a genuinely healthy board and burndown, yet a sponsor can still report feeling uninformed — this isn't necessarily a sign the artifacts are wrong. It usually means the artifacts exist but aren't being effectively communicated outward, which is a distribution gap rather than a tracking gap, and calls for a different fix than rebuilding the tracking tools themselves.
