"Instead, let's discuss finding a way to work together more effectively. What are the biggest problems that the people in the system are facing now? Let’s fix those." This really resonated with me. I've spent the last several years where Scaled Agile was forced down people's throats. It was born out of necessity in a perhaps final, last gasp effort, at trying to address those BIG problems. The challenge was that it was one group trying to impose Scaled on all groups none of which had buy in. There was also a total lack of interest from "leadership/executive level" management. They did not care to even ask the question/s "What are the biggest problems?"
:) OK you also wrote, "I don’t think implementing one little thing at a time is either." Why not? :) What if you continuously improve one sprint at a time and as learnings of each sprint/PI/release we uncover the those big problems holding EVERYONE back?
Always interesting trying to remember why I wrote what I wrote! My newsletter is a quick musing of what's been on my mind during the week, and I don't give it the depth of thought I do in my other writing.
Today I interpret this sentence to mean implementing part of a framework to work towards implementing that framework fully. I'm certainly not opposed to implementing a small change that the team has decided to try, and we should do so as often as possible. I completely agree with everything you say about small changes overcoming big problems. ❤️
Thank you for asking such thought-provoking questions!
"Instead, let's discuss finding a way to work together more effectively. What are the biggest problems that the people in the system are facing now? Let’s fix those." This really resonated with me. I've spent the last several years where Scaled Agile was forced down people's throats. It was born out of necessity in a perhaps final, last gasp effort, at trying to address those BIG problems. The challenge was that it was one group trying to impose Scaled on all groups none of which had buy in. There was also a total lack of interest from "leadership/executive level" management. They did not care to even ask the question/s "What are the biggest problems?"
This is exactly the same situation I've seen recently that in part inspired me to write this post. :)
:) OK you also wrote, "I don’t think implementing one little thing at a time is either." Why not? :) What if you continuously improve one sprint at a time and as learnings of each sprint/PI/release we uncover the those big problems holding EVERYONE back?
Always interesting trying to remember why I wrote what I wrote! My newsletter is a quick musing of what's been on my mind during the week, and I don't give it the depth of thought I do in my other writing.
Today I interpret this sentence to mean implementing part of a framework to work towards implementing that framework fully. I'm certainly not opposed to implementing a small change that the team has decided to try, and we should do so as often as possible. I completely agree with everything you say about small changes overcoming big problems. ❤️
Thank you for asking such thought-provoking questions!