Agile transformation: Quagmire of Flexibility
Why do problems stock in our team, and we can't solve them in Scrum?
We all might have some experience with bloody Retros or problems that we try to solve several times and can not.
Why do these things happen? Is there any problem that we can't see? Here is an example of what I refer to as the quagmire of flexibility.
When we see a problem in our time, our first step is to host a retro about it, try to fix the issue, and try to create an improvement in our team processes. This action is also directly compatible with two scrum values, Courage and Openness. But solving some problems is not that easy. We do Retros, but nothings happen, or after a while, the issue comes back with a new shape. A retro loop will run again, but no result will establish. I think the Quagmire of flexibility is what most often happens here. The scrum team thinks that flexibility will help them, and they can go forward and solve the issue by themselves. The thing that they don't self-aware of it at the problem-solving moment is that some issues are like mangrove forests. They have roots in other organizational levels even.
Recommended by LinkedIn
When we bring up an issue that has organizational roots at the team level, We have started a war of attrition against the team's resources and energy. There will be no results. Over and over again, we repeat the process. Guess what happens? No results. We start to mire in our misconceptions. And when problems arise and don't solve properly, team members' faith in the team's problem-solving skills and abilities will reduce. Team members start to avoid expressing their anxieties and worries, which leads to new roots for future issues.
When even a simple issue happens, it's better to be like low tide and try to reveal the roots. Don't let the development team's flexibility miss lead you. Always flexibility is not your silver bullet. When all you have is a hammer, everything looks like a nail.
Senior Software QA Engineer at Snapp!
2yI love this guy 👌🏻😂