Why don't "agile coaches" seem to comprehend agile?
I've been having an interesting few years.
I'm a contract software engineer - ostensibly, my role is simply to work with a client to build software. I firmly believe that this can only be done in a realistic and mutually satisfactory way iteratively - that is, I generally work with clients in a way that would call under the remit of "agile".
You'd think this would be easy, after all, every single client I've worked with for the last few years has been full of people with titles like "agile delivery coach", "agile delivery lead", "agile manager", "agile technical lead", "agile implementation head", "agile strategy director" etc etc.
However it has not been easy, in fact, every single organization I've worked at in that time has been critically failing to implement any coherent concept of agile, and their day-to-day struggle is not with technology (I believe that the current ecosystem, particularly around Node, the .NET Framework, Azure and AWS has given us a golden age of easy enterprise software development) but with their own incoherent implementation of an agile methodology, so far always Scrum. I've noticed that they rarely want to actually say they're doing Scrum, however, and the reason seems to be that they don't want to adhere to what is found in the Scrum guide. Ironically, they're having all of the problems that the Scrum guide predicts you'd get by acting this way, as the following has been true of every single one of these companies:
- They have separate sub-teams on their scrum teams, such as "tester" and "business analyst". Particularly with regards to testers, there's team members sat around doing nothing and feeling sidelined. Despite this lack of cross-functionality being a direct violation of the definition of the approach they're using, the "agile experts" always seem oblivious to this issue, and often try to fix it by breaking down work into meaningless sub-parts to "get stuff to testing faster".
- They don't work in increments - at the end of a sprint, random bits of things have been built, yet the software is not usable. Again, the "agile experts" rarely seem to comprehend what an increment is, despite "working software" being both a principle of the agile manifesto and one of the three Scrum Artifacts with a clear definition in the guide.
- They take the process of determining how a product backlog item is broken into increments of value out of the developer's hands, and when this results in incoherent or unsatisfactory work, they double-down on this. Very often, people with titles like "agile coach" are actually writing how the developers are to execute the work, again oblivious to the fact this is explicitly forbidden in the Scrum guide and, beyond that, that a non-developer cannot possibly make these kinds of decisions.
- Teams are regularly audited, often mid-sprint, using "story points" as a metric. Story points are used externally to teams, as a way of monitoring their progress. Story points do not correspond to delivered value, indeed so lost is the focus on delivering increments of value that these so-called agile experts will literally talk about "delivering story points", and will consider a story that doesn't deliver any usable functionality to be "done".
The most bizarre aspect of this is that the paid "agile experts" seem to be the people who most drive against both the Scrum framework but Agile principles in general. These people are invariably insisting on "breaking down stories" on behalf of the developers, they talk about "flow" yet don't comprehend that this is meant to be a flow of increments of value not independently unusable "story points", and there's often huge numbers of them. Given the laughable simplicity of the Agile manifesto and Scrum, it seems incomprehensible that I routinely see setups where there's almost as many "agile experts" as developers. These people are often "managing" the developers, even though in the actual Scrum Guide the developers have absolute autonomy over how the work is executed.
This affects me because in almost every new job I have I am usually embedded on some form of team to provide my specific expertise in cloud tech, yet I almost always have to fix a completely dysfunctional agile process before anything meaningful can proceed. This almost always takes the form of having to kick these "agile coaches" out of breaking down the product backlog items into increments of value, and it's not uncommon for a project with more than enough developers and a clear set of goals to be in a state of complete dysfunction because these "agile experts" are trying to define the work instead of the developers, something which they are absolutely not competent to do.
I've become exceedingly good at this, generally being able to kick these people out of the thing they're not competent to do in my second sprint (after all, I'm involved in the planning of that one) and the teams I'm on are usually extremely glad for the incoherence of having the technical work led by non-developers to end. These sprints are usually the first that the business and the team I'm on have been happy with in a long time, and yet I find it rather depressing that I seem to be spending a lot of my career having to free perfectly viable projects from deadlocks created by agile "experts".
Is there something really, really rotten in agile at the moment? Has this just become a group of people who get in the way of developers and justify it with buzzwords? People who mostly oversee Scrum and yet have rarely even bothered to take the 15 minutes required to read the Scrum Guide?
Posted Feb 11, 2022, 5:01 PM UTC
While I agree that most of what you've seen is unfortunately pretty common, and your frustration is certainly something I often feel, in your post there is one fundamentally incorrect assumption: that agile is "easy". The proof is in how consistently badly it is implemented in real life. Saying that agile should be easy because of the "laughable simplicity of the agile manifesto" is also a tricky and incorrect assumption. Try this one on for size: Be a good person. Laughably simple right? In practice, not so much. So the simplicity of the instructions has no bearing on the ease of implementation. The original authors of the the manifesto have repeatedly said that as a framework, it will not be easy to implement, partially because of its contextual nature.
It is awesome that you're there to help teams, you should add a line item to your billing: $x/hr if agile implemented well, $x+50/hr if team needs agile restructuring. It isn't easy, it got super big super fast because it became popularized by some highly visible success stories, then everyone implemented it based on a forumula - that didn't work because there is no one-size-fits-all approach. So then all the Agile coaches rejected the "one-size-fits-all" approach and are now all trying to roll their own scrum system. It is a clusterfuck. To make matters worse, trade schools are pumping out agile coaches every 6 weeks and companies are still hiring them up because they still have this process improvement need. The number of experts are few but the number of practitioners are many.
Lastly, and this is the kicker, we've been doing this stuff for 20 years. On one hand there is still the significant pressure of a more traditional process and a lot of both education and reformation of that process needed. On the other hand people and organizations have gone through 20 years of awkward attempts at agile and have formed all sorts of opinions without good retrospectives of what worked and didn't and why, nor with the recognition that what worked or didn't was nearly entirely a result of the people and context at the time and that those things may not work in their current situation.
So what can you do to not pull your remaining hair out? First, get used to it. Not exactly the answer any of us want to hear but you're absolutely right - this is the reality we live in. Expect to encounter this everywhere. And none of us are perfect or know how to do it "right". For instance, be careful of orthodoxy in your own concepts of agile - I read quite a few red flags of possible orthodoxy in your post. Second, don't assume that this clusterfuck you're walking into is because something when WRONG. What you're experiencing could be someone's moment of progress in a dysfunctional company where everything is finally starting to move in the right direction (there is no perfect agile implementation). Every system has bugs, and balancing when you refactor your agile processes vs just getting the job done is a tricky and political. Finally, as I'm sure you know, you can't just walk in and wave a pen and fix it for them - you might get things slightly adjusted on one team for a moment but organizational change is glacial even in the most nimble of orgs.
I expect that part of your post is just coming here to commiserate rather than really looking for any answers - and boy do I feel ya.
Sounds like you're being part of the solution which rocks, glad for folks like you!
Agree with all of this.
Have a sneaking suspicion that what OP is seeing happen is the result of someone above the agile coach who doesn't understand agile, is still trying to strong arm the teams into some one-size-fits-all approach, agile coaches objected and were told by manager 'my way or the highway'. I've seen it happen. Even after you've had the whole 'scrum isn't command and control' conversation. Not pretty.
[deleted]
And yet I cannot reconcile this with my own experience - I've been able to force many of the companies (and all of them for the past four years or so) to adopt agile simply by kicking agile coaches/scream masters out of the breaking down of product backlog items and the execution of the work, something they were never competent to do to begin with.
This is rarely more than a couple of week's of work until there's been a fundamental shift in thinking, compared to the years these companies throw down the pan paying "agile" people to try and do things that only a dev is capable of doing. I cannot help but call this "easy", even if it's the type of easy that requires a particular clarity of purpose.
Yawn. Big dick swinging isn't agile. Lol glad it works for you. I hope we never work together!
With all due respect, when you said this...
I didn't take offense.
So why don't you drop the "I hope we never work together" childishness? Becoming upset at a fraction of the language you yourself felt comfortable employing is a hypocritical look.