Timeline for RACI matrix and illness/vacation/leave
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 8, 2021 at 19:26 | comment | added | Sarov | Let us continue this discussion in chat. | |
| Nov 8, 2021 at 18:45 | comment | added | Iain9688 | According to one definition (ictshore.com/project-management/raci-alternatives) it means exactly that... Ownership of the outcomes. | |
| Nov 8, 2021 at 18:40 | comment | added | Iain9688 | RACI may not be necessary in an agile environment, however in a hierarchic organisation, especially in a waterfall project (which is where I spent most of my P.M. life), different teams had ownership of different things. Unix were not allowed to touch hardware or databases, Security couldn't touch the data, etc, and every team was measured by its own management. We needed the clarity that RACI provided. | |
| Nov 8, 2021 at 18:21 | comment | added | Iain9688 | Sadly, if nobody takes ownership, nobody owns the fix. If something has gone wrong, someone needs to accept that they need to fix it. Otherwise it will stay broken, or a fight will develop about who needs to fix it. An accountable person takes away the issue, | |
| Nov 8, 2021 at 18:16 | comment | added | Sarov | "neither will take ownership" - why does anyone need to take ownership? What advantage is gained by pointing a finger? | |
| Nov 8, 2021 at 18:12 | history | answered | Iain9688 | CC BY-SA 4.0 |