Here are some useful tips for forming a matrix:
The RACI matrix is a project-based matrix, not a product feature development matrix. There are design, engineering, and reporting functions, but no "push-button" tasks.
Development works well when considering 10-25 project phases.
Project phases are represented by specific verbs such as “review,” “issue report,” “estimate timeline,” “create schedule,” “collect data,” “approve concept.”
In the matrix, it is student database preferable to use roles instead of names. If Vasya did not come to work tomorrow, someone else would take his place.
RACI should be created in groups of four to ten people. It is possible to misjudge a situation alone, and a large number of people will make the discussion longer and more difficult. However, before the RACI matrix is approved, each participant must define and agree on his or her role.
At a minimum, A and R must be defined at the appropriate levels.
A – Assignment of responsibility (responsibility is assigned only to those who have authority).
Positions I and C should be kept to a minimum.
If a matrix has been created, inform each project member about it and their role in the process and ask if they agree with a particular function. If not, the design needs to be revised.
The RACI matrix may become out of date as the project evolves, so in some cases it may need to be updated.
Case: VT-metall
Find out how we reduced the cost of attracting an application by 13 times for a metalworking company in Moscow