The other day I was thinking about the problems I have been seeing with clients. My thoughts expanded from the current team and organization concerns to more general scope of experiences with other transformations. Below is the resulting list of ideas, in no particular order and without fanfare. Let’s talk about it if you’d like to go deeper on your favorite!
Random Issues in the Agile Transformation Bridge
- Managing by email doesn’t work well. Leading a transformation by email doesn’t work at all.
- Documents are important. Leading by example is vastly more important.
- Before you can scale Agile (or anything else) you have to have Agile (or that anything) to scale.
- If the business around the teams does not change, the teams will work they way they always have and just use the new labels for what they do. And have more frustration.
- Policies, procedures and processes send messages. These messages define your culture. To ignore the messages is to ignore culture.
- Culture eats strategy for lunch. And dinner. And steals your lunch money. Unless culture is aligned with your strategy. Then it gives you lunch. And Dinner. And more lunch money in beautiful greeting cards.
- Ownership of improvements is better handled by those who need to improve. That means improvements mandated by others rarely create the desired result.
- If a team doesn’t have what they need to get the work done, asking them to work harder will not help much.
- For every decision maker or specialized skill that is not dedicated to a team add two days to every request. For example, if the stakeholder needs to approve a feature change it will take at least two days to get an answer. If a meeting is needed, add four days.
- 99% or more of the time everyone is doing the best they can under the circumstances. Check your system and environment for the root causes of failure, not your people.