This whole Agile Coach debacle has helped me realize something that hadn’t fully landed with me before: agile started as a movement driven by builders to «build better», but it is largely dominated now with people who don’t know how to build and look at agile as a management process style. These are MBA-like folks who are trying to figure out how to manage an IT organization. But that wasn’t what agile was about. It was about a better way to build stuff, better stuff, by collaboration and not getting stuck in our ways.
@Patricia Reminds me of
@einarwh saying in a talk at
@boosterconf:
"Individuals and interactions over processes and tools. And what do we end up with? Scrum and Jira."
@joeposaurus @einarwh @boosterconf oh my, what a gut-punch. He’s speaking the truth tho, as he does uncomfortably often and well.
@Patricia @joeposaurus @boosterconf What's crazy but needs recognition I guess is that in many cases, for many people, Scrum and Jira were a great improvement on whatever came before. As Alistair Cockburn put it, "Scrum struck a magnificent bargain in hostile territory", the deal being that management could change their mind between sprints, and no-one would pester the team during the sprints.
@Patricia @joeposaurus @boosterconf That's not to say it's a deal that delivered on the promises of the Agile manifesto (how could it?) or that it's the best possible deal today. (Though my impression is that many think that realistically, we won't be able to do much better than that.)
@einarwh @joeposaurus @boosterconf I’ve seen better. And not only once. I know it can be done. But it requires leadership that allows it to happen, and I feel that tech leadership has drifted over to «career leadership» and they don’t get what we do. They come from all over and they don’t get the process. They want something «cleaner». But it is messy, and that’s not a bug. We are trying to figure out what we should build by building it, we’re learning what we should’ve built by living with it.