3 ms·
The Wikipedia entry doesn't do RASCI any favors in promoting it as any sort of useful artifact from what I can tell. It seems most like a "blame matrix."
by wavefunction 12y ago
The Wikipedia entry doesn't do RASCI any favors in promoting it as any sort of useful artifact from what I can tell.
It seems most like a "blame matrix."
- x0x0 12y agoit's not entirely worthless if, after a meeting, you circulate a quick set of (1) what did we agree on, (2) who is the person responsible for each of (1), (3) who requires signoff on various (1) I find it quite useful. It's good to have it written down to serve as a consensus from the meeting to reduce miscommunication about who has what commitments and who must sign off. Lots of orgs use stuff like this: github has a Primarily Responsible Person, apple has something similar. That said, I've never had to draw out a formal rasci chart, and this can easily be taken too far. In a team of maybe 1-10 people this level of formality is way overkill.