[Build] RACI (responsible, accountable, consulted, informed)

[davidfine]

Wish I could have been there to clarify how the RACI model was used at
my nonprofit. (We used the version called DARCI because it was less of a
flat hierarchy).
http://en.wikipedia.org/wiki/Responsibility_assignment_matrix#RACI_.28alternative_scheme.29

    /Responsible/
        There should be exactly one person with this assignment for each
        task.  They delegate and work and make sure their team has
        everything they need to get it done to spec. They make
        adjustments to the plan as needed. They are the point of
        contact, and the one that reports back about progress. They are
        the one person whose neck is on the line.

    /Assists aka Accountable
    /
        Those who assist completion of the task. The worker bees. Most
        tasks will have many, all coordinated by the 'Responsible'. They
        often have more expertise in their work than the 'R' does, so
        they get to choose what tools to use and other specifics that
        weren't covered by the spec. For small tasks the 'R' and 'A' may
        be the same person.

    /Consulted/
        Those whose opinions are sought; and with whom there is two-way
        communication. Outside experts. Other teams who will be impacted
        by your work.

    /Informed/
        Those who are kept up-to-date on progress; and with whom there
        is one-way communication. The mailing list.





On 6/25/14, 7:25 AM, Naomi Most wrote:
> Greetings Rebooters,
>
> TL;DR -- if your name was on the board yesterday, please start a
> thread right now on the Build list to describe your area(s) of
> Accountability and recruit help.
>
> We talked last night about using the "Responsibility Assignment
> Matrix" to manage our projects.
>
> http://en.wikipedia.org/wiki/Responsibility_assignment_matrix
>
> Click on that link to the expanded definitions.
>
> Last night we attempted to assign an "accountable" role to each
> project and collect any interested "consulting" or "responsible"
> roles.
>
> The "informed" role goes to the Build mailing list.  I'll read it
> obsessively and occasionally pry for more information when I think
> someone's missed some information that another project needs.
>
> CONCERNS about this system:
>
> There was a lot of mixup between "accountable" and "responsible" in
> our discussion last night.  I was a little sleep-deprived and couldn't
> keep them straight myself.
>
> We may want to make the world easier *and* more fun for ourselves by
> making up our own parallel system.  For example:
>
> Accountable = BOFH
> Responsible = Developer
> Consulted = Bikeshedder
> Informed = Mailing List
>
> (We can do better than that, of course.)
>
> Or we can just all agree to get really good at knowing the difference
> between "responsible" and "accountable", but as a user interface, I
> wouldn't call this nomenclature intuitive.
>
> DISCUSS!  :)
>
> Cheers,
> Naomi
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.noisebridge.net/pipermail/build/attachments/20140625/024934f3/attachment-0003.html>