RAID Log
Let’s look into a helpful framework called RAID.
After breaking down the work and adding time constraints to the roadmap, you are ready to formalize many things that have already been discussed:
Risks that might arise
Assumptions that we have about the future
Issues that already exist with the plan
Decisions to be made
Dependencies across teams
By creating a RAID log, you will identify and document these things. A RAID log is just a formal way of handling that diverse set of information you need to track and drive.
What is a RAID log?
RAID stands for risks, assumptions, issues, and dependencies (or decisions). A RAID log is a tool to document and track these elements, starting in the planning phase but continually being used throughout execution.
Having a comprehensive and up-to-date RAID log will help you consolidate the many moving pieces of the program that you need to track throughout the program lifecycle.
You are learning about it in the program planning phase so that you can create this artifact early in the program.
In this lesson, we will learn how to create a RAID log, and how to use it effectively to ensure the smooth execution of your program.
Creating a RAID log
As the TPgM, you own the RAID log and are responsible for keeping it up-to-date. You drive the successful creation and maintenance of the RAID log. It is created through the combined effort of all members of the program team.
Risks (R-a-i-d)
Risk Management is an important aspect of your role as a technical program manager.
It involves identifying, assessing, and mitigating potential risks that may impact a program's success. Effective risk management requires a ...