2

Generally I see a Responsibility Assignment Matrix (RASCI) being developed at the start of a project. However, in the current environment, a RASCI is only being developed as part of handover to the operational team. This seems counter-intuitive.

The RASCI being developed is intended to highlight the support model going forward. From my perspective, a RASCI encompasses all aspects of the project including handover.

When should the RASCI be developed?

  • Depends on the environment. In my environment RASCI is frequently developed during initiation/charter - because we work in a large, federated environment with disparate stakeholders. Others defer this till later. – Mark C. Wallace Dec 15 '15 at 18:35
4

The RASCI being developed is intended to highlight the support model going forward. From my perspective a RASCI encompasses all aspects of the project including handover.

It can do both, or neither. RASCI is just a tool to get agreement and understanding on who is responsible for what and at what level.

If it's useful to have as part of your project (lots of deliverables, lots of stakeholders, lots of "opinions" etc) then by all means use it for the entire project.

If it's useful only in certain phases of the project (eg handover and/or operations) then use it only in those phases.

Neither is fundamentally right or wrong, RASCI is just a tool that becomes part of your kit. I find it very useful in larger teams or complicated (or overly bureaucratic) organisational environments to use over the entire project process, but for smaller projects / closer knit teams / collaborative organisational cultures I sometimes find it overkill and use it only for certain phases, and sometimes not at all.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.