## Overview **RAID methodology** is a... #flashcard structured framework used primarily in project management to help identify, track, and manage key elements that could impact the success of a project... ### ✅ **R – Risks** - **Definition:** Potential events or conditions that could negatively impact the project's objectives. - **Examples:** Budget overruns, resource shortages, technology failures. - **Management Activities:** - Identification and documentation - Assessment of likelihood and impact - Mitigation planning and ownership assignment ### ✅ **A – Assumptions** - **Definition:** Conditions believed to be true for planning purposes but that may not be confirmed. - **Examples:** "Vendor X will deliver on time", "Resources will be available in Q3". - **Management Activities:** - Clear documentation and validation - Monitoring for validity over time - Updating plans if assumptions change ### ✅ **I – Issues** - **Definition:** Events or problems that have already occurred and need resolution. - **Examples:** A critical bug in production, key personnel leaving mid-project. - **Management Activities:** - Logging and prioritizing - Assigning ownership and due dates - Monitoring resolution progress ### ✅ **D – Dependencies** - **Definition:** Relationships between tasks, teams, or external factors that must align for success. - **Examples:** Completion of API before frontend integration, legal approvals before launch. - **Management Activities:** - Mapping internal and external dependencies - Identifying owners and timelines - Actively tracking and mitigating delays <!--ID: 1751507777842-->