Battlecard: RAID Is Not Admin
Respond to RAID-log resistance by linking the log to decisions, path protection, and sprint adaptation.
A teammate says the RAID log duplicates Jira and slows the team down. Can we skip the RAID log? We already have Jira. I agree we should not duplicate task tracking. Let's keep RAID only for risks, assumptions, issues, and dependencies that can change the Sprint Goal, critical path, or stakeholder decision. The vendor key belongs there because nobody on this team can complete it alone and it gates release testing. It validates the admin concern, narrows the log's purpose, and ties RAID to Scrum transparency and critical-path protection. Do not use RAID for every task or it will become…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in