Run the RAID Log as a Rhythm
Use a RAID log as an active inspection rhythm tied to sprint and schedule decisions.
RAID is a rhythm, not a repository. Categorize to choose the right action Risks need prevention or contingency. Assumptions need tests. Issues need resolution. Dependencies need coordination. Blending them into one vague problem list makes every row sound similar and delays action. Inspect it inside the sprint cadence Bring the top RAID rows into planning, daily inspection, and review. The log should influence what the team selects, what it escalates, and what it renegotiates. Escalate by path impact Use critical path to decide urgency. If a RAID item threatens the chain that sets the finish date, it is not admin.…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in