LEARN. PRACTICE. GROW.Concept and mechanism
At iteration start, combine the goal, prepared work, current capacity, and earlier experience. Available days and points are not interchangeable units. With four people over ten days, eight absence days and six non-overlapping support days leave 26 person-days before other constraints. Team Sync helps inspect the goal and coordinate next steps; responding to an incident need not wait for that event. Refinement clarifies needs and criteria with people who understand usage. If “improve alerts” does not identify the failure requiring detection, estimating immediately may merely give ambiguity an appearance of precision.
Guided application
When many items remain open, investigate age and blockers before starting more work. At review, show results and limitations, gather feedback, and discuss adaptation. CALMR helps examine culture, automation, flow, measurement, and recovery together. A fast pipeline without rehearsed restoration leaves an operational capability missing. Deployment may install a change with exposure disabled; release still depends on agreed conditions and decisions. Also evaluate the complete path: if installation falls from 30 to 10 minutes but review and recovery rise from 20 to 60, measured total grows from 50 to 70. Investigate the effect before declaring overall improvement.
An 11:00 incident may need immediate authorized response and scope review with the PO; the next Team Sync is not a barrier to adaptation.
Common pitfalls
Invisible support; points as days; installation as release; automation as recovery; green charts without shared criteria.
Related topics: PI closure and observable improvement · AI with context and oversight
Coordinate work to complete value with quality and demonstrable operational conditions.
Reference: Iteration Planning · AI-Empowered SSM; official exam guide August 11 2026