Yes, and it plugs in more naturally than you might think. Review your RAID during sprint planning to catch risks and dependencies early, flag blockers in standups as issues, and use it in retrospectives as a lessons learned record.

In scaled Agile environments with multiple teams running parallel sprints, a shared RAID log gives leadership the cross-team visibility that no individual sprint board can. The key is ownership — assign it to the Scrum Master or Product Owner and keep it actively maintained, not treated as a one-off document.