Unwilling to change the system!
Anti-pattern
Less than 1 minute to read
Last Updated: Wed 25 Oct 2023 11:15
draft
This page is in draft and may include errors or omissions. Please check the discussions for any pending updates and changes to the content or to suggest your own changes.
Description
Most organisations are unwilling to change the systems that are finely tuned to maintain the status quo.
They bring in agile frameworks and practices and layer them on top of the existing systems. The practice of layering new systems on top of the old systems are why organisations are not seeing the expected benefits from agile. The only way to fix this is to challenge the systems and change them. That is why Scrum has a Scrum Master that is charged with the teams effectiveness.
Symptoms
- No real change as core differences of new systems (Scrum, Kanban, Lean, etc…) are ignored
- Increased frustration as new systems interact with existing ones
Actions
- Get stakeholder buyin for new system.
- Run OpenSpace Agile or OpenSpace Beta to bring everyone on board.
Recommended Content
-
We are uncovering better ways of developing software by doing it and helping others do it. These are our values and principles.
-
The Scrum Guide (Guide)The Scrum Guide contains the definition of Scrum.