My sadness was not in the authors or the article itself, but in the fact that it has come to this. Instead of simply identifying, collecting and having the patterns available to use as needed, we as the agile community have felt the need to try and mix and match patterns in various ways, label them as frameworks, sell certifications for them and argue about which framework is the best. This has been ongoing and is being perpetrated as the focus is now on “scaling” agile instead of anchoring to the mindset if “being” agile. What this has caused is noise, confusion and many many less than stellar results then practitioners who try to lay these frameworks on top of organizations without first identifying what is needed.
Read Tom’s complete “I Must ASK (Agile Scaling Knowledge) — Has It Really Come to This?” blog post for more!
And while Tom acknowledges the importance of patterns and frameworks, he emphasizes the importance of “implementing” or “pulling in” those patterns that confront the dysfunctions (and offer efficiency and effectiveness) within an organization based on it’s needs — thus, birthing a framework (starting with a fresh “blank” canvas) based on the needs of the organization (Brad Barton, Mark Ferraro, and Si Alhir) — that is, Constructively (rather than Destructively) Adopting and Sustaining …
All too often, we neglect the journey (adopting, sustaining, and scaling) and obsessively/compulsively focus on the destination. . .
Life is a journey, not a destination.
(Ralph Waldo Emerson)