Marek RudnickiPMO, Program Management, Project Management, Business Development| FreelancerPoland
Dear PM Community,
Would like to ask you for best practices to manage RAID in a large program/project.
So far approaches are not working well.
Main Issue :
RAID file is getting very big as there are many streams and people involved in the program (hundreds of items on RAID). Obviously many actions and issues are interdependent. Not talking, people are mixing risks with issues, and concerns. Overall it is getting not manageable.
It is hard to control content and make sure communication is happening between the originator and the owner of the item.
Questions:
1) How regularly should RAID be reviewed?
2) Should the review be done on the program level or first by different streams than on the program level? (I am afraid of spending too much people's time on this)
3) Should review dedicated to content or just statistics (new, closed, pending)
What are your best practices/approaches for the process?
"If you have an apple and I have an apple and we exchange apples then you and I will still each have one apple. But if you have an idea and I have an idea and we exchange these ideas, then each of us will have two ideas."
