Dangers of using SCRUM, Process management and especially RACI model
I have seen and been involved in designing processes and writing role descriptions in different organisations. Sometimes the work is really concrete and useful, sometimes it can become really high-level and filosofical.....time consuming, expensive and restricting. Here are some comments I would like to make on the issue:
-The level of detail needed in the models indicates how bad the relations and teamwork are in your teams. If it is on the level of "I take care of the technology and all around it" then you have a good team.
- Detailed and popular models like SCRUM and SAFe are necessary in teams where there are new members and or members from different organizations or cultures. The familiar methods make co-working easier when there is no time to build trust.
- Detailed role definitions and methodologies are dangerous. Even the most detailed descriptions and models do not take into account all the possible scenarios and it can easily happen that everyone does their tasks perfectly, but the system goes down or the development does not deliver. (MOKK - Minu osas kõik on korras / Minun osaltani kaikki on kunnossa)
- Detailed process models and role descriptions turn organizations into bee-hives: very effective in a status quo environment doing the same thing over and over again, but totally unable to adjust if change is needed.....and change as you know is a constant in modern business.