Christopher HealySR IT Program Manager| General MotorsBerkley, Mi, United States
Anyone have best practices for creating a Program Level RASI/RACI? Basically the challenge I have is how to call out that someone may be Responsible on one piece of work, but inform on another. Saving Changes...
I'd start by making sure the "right" stakeholders are in the room for this discussion. In my past, it has usually been the leads for each distinct work stream within a project or program.
Then, make sure there is a consistent understanding of each of the obligations (e.g. what does it mean if someone is "responsible" for a deliverable or activity).
Make sure there is a senior leader to whom disagreements about "who does what" can be escalated to for a decision.
Finally, using the program-level WBS as support, go work package by work package or deliverable by deliverable and facilitate the discussion around the "who does what".
Kiron Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Trying to add something to @Kiron comments above (and perhaps I am not saying nothing new) based on the functions/process defined for program management you have to create the OBS and the WBS and make an intersection of them to create the RACI. Other tool that could help is creating a CRUD (Create/Read/Update/Delete) Matrix for each deliverable. Saving Changes...
