Alt Text
menu

Scrum's RACI

Every two weeks or so I get into a conversation about using a RACI on a scrum team, and in the past I have fought this idea, saying RACI would not add anything to a scrum discussion. One day a college said:
format_quote
Every team has a RACI, some just write it down.
format_quote
College
Sprint Planning is timeboxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.
This made me want to prove that a RACI and scrum just don't work so grabbed this RACI-loving college and we build out a RACI based on the scrum guild. Turned out that a scrum RACI is illuminating. And I now think can be a great tool to help people do Scrum.

First Some Context

format_quote
RACI is an acronym derived from the four key responsibilities most typically used: responsible, accountable, consulted, and informed.[4] It is used for clarifying and defining roles and responsibilities in cross-functional or departmental projects and processes.
format_quote
Wikipedia
This are drawn up in a matrix with the activites on one axis and the members on the other.
So our exercise here was if we use the Scrum Guild can we filling a RACI matrix.

Step One Pull Directly from the Scrum Guild.

First of all we need the players
format_quote
Scrum defines three specific accountabilities within the Scrum Team: the Developers, the Product Owner, and the Scrum Master
format_quote
That seems like a good start! So we have our players. It then goes on to say the accountabilities of each.
First the Developer:
format_quote
the Developers are always accountable for:
- Creating a plan for the Sprint, the Sprint Backlog;
- Instilling quality by adhering to a Definition of Done;
- Adapting their plan each day toward the Sprint Goal; and,
- Holding each other accountable as professionals.
format_quote
Scrum Guild
Next up the Product Owner:
format_quote
The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. How this is done may vary widely across organizations, Scrum Teams, and individuals.
The Product Owner is also accountable for effective Product Backlog management, which includes:
- Developing and explicitly communicating the Product Goal;
- Creating and clearly communicating Product Backlog items;
- Ordering Product Backlog items; and,
- Ensuring that the Product Backlog is transparent, visible and understood.
format_quote
Scrum Guild
And Finally the Scrum Master:
format_quote
The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization.
The Scrum Master is accountable for the Scrum Team’s effectiveness. They do this by enabling the Scrum Team to improve its practices, within the Scrum framework.
format_quote
Scrum Guild
So This is enough to start the matrix.












Ok that is a good start but is there anything else we can add?

©Erik Summerfield 2022

e2thex.org Last Updated: 3/22/2022