Yes, Yes, Yes. This is an awesome case for introducing the XXXX Scaled Model in our organization claimed the Program director for agile transformation.
Really?? It’s me asking with curiosity in my voice (can be called “Sarcasm” too ?
“What do you mean? Is this not the perfect case for us to introduce the XXXX Scaled Model as part of our transformation journey?” Asked the program director. Pause….
A few weeks back….
Let’s rewind a few weeks back to see why the program director was so excited.
As the Agile transformation program head and also the Senior Director by designation, my reporting boss is excited about anything and everything about Agile. He is heading the Agile transformation program for the past 9 months and he is happy with the way things are going.
As a part of the New Year strategy, the H.O. advised him to do the next wave of agile transformation (better to call Agile Wave 2.0). As a part of the new wave 2.0 one of the proposals is to introduce the XXXX Scaled Model across the organization.
The program director was looking for enough cases to support his pitch to introduce the XXXX Scaled Model. To his luck, the following feedback from multiple scrum teams popped up
- The new feature development spans across departments and this results in integration and coordination issues
- Varying prioritization across departments results in delays in the integration thus delaying the production release
- Coordination between the departments has become a nightmare and is consuming a lot of time
Fast forward to now...
“Are you sure using the XXXX Scaled Model helps to fix these issues?” It’s me asking the program director.
“Why do you think this will not solve our problem?” Asked back the program director.
“Well, can we NOT conclude the solution from solution space but rather move back to the problem space to see what the problem is?” I asked him back.
Being a big believer in the quote “Problems cannot be solved with the same mindset that created them” my boss agreed to look at beyond just pushing the teams to use the XXXX Scaled Model.
In the next 2 weeks, we figured out some of the other deeper issues that caused the above problem. Some of the critical ones are:
- There are more than 10 product backlog
- Teams work on multiple items at the same time (no prioritization)
- Conflicting goals across departments
- Prioritization issues because of conflicting business demands
The next 3 months are really tough as we introduced our own new way of release planning and other related support changes. We got a lot of push to use the XXXX Scaled Model as it was more “fashionable” and also fix the same issues in a more prescriptive way.
No! We are not going to bring the white elephant (XXXX Scaled Model) as part of Wave 2.0.
This is the final bold statement made by the program director after seeing our simple solutions are working much more effectively.
Yes! Sometimes common sense is the most effective framework to use!!!
Disclaimer: This is a work of fiction. Names, characters, businesses, places, events, locales, and incidents are either the products of the author’s imagination or used in a fictitious manner. Any resemblance to actual persons, living or dead, or actual events is purely coincidental.