LEARN. PRACTICE. GROW.Concept and mechanism
A contextual assessment identifies conditions making delivery more or less feasible. For example, limited user availability can undermine feedback. Recording a score does not change that condition: define a response, an owner, and a point to check its effect. Technical investigation reduces uncertainty but may expose more risk than expected. When a test shows latency above the assumption, update forecasts, impact, and options. Distinguish risk from an event that has already occurred and handle issues with enough information to decide. The purpose is timely action within authority and escalation when forecast boundaries are exceeded.
Guided application
Interpret every dashboard through its measurement boundary. Stable throughput does not establish the absence of blockers: fast items can leave while older ones remain stuck. Open-item age differs from a completed item’s cycle time. Look for distributions and causes rather than an average alone. If a dashboard excludes required integration, green status does not represent the overall outcome. Correct the boundary and revisit forecasts with dependency owners. When a request exceeds cost tolerance, fitting in the backlog does not authorize it. Prepare a recommendation with options, effects, and the required decision before making the commitment.
If six items leave weekly but two have been blocked for twenty days, investigate those two; aggregate output can hide their condition.
Common pitfalls
Agilometer as approval; investigation as resolution; average as guarantee; fragmenting tickets to evade tolerances.
Related topics: Decide at startup and coordinate delivery · Learn, continue, and transfer responsibility
Expose risk and boundaries before the deviation materializes.
Reference: PRINCE2 Agile Practitioner syllabus · Version 2; inspected syllabus 2.0 (May 2025); revision 2.1 comparison pending