a CTO friend the other day asked what I do. I gave a quick rough approximation of part of it, and he responded oh, you're an agile coach
my immediate reaction was hell no - and yet, he’s not wrong. and he’s also oh so wrong.
I’ve formed the experienced opinion that for some teams, all of the heavily documented agile frameworks are just the wrong solution. that..doesn’t mean agile is bad, or even that those frameworks are bad. it just means they’re not the right fit for those teams for the moment they’re in.
I don’t preach a framework, or a standard, or any kind of approach at all. I’m of the opinion that we need to evolve what we’re doing on a daily/weekly basis to match the needs of the business, the product, and the team. [and we need to build our tooling to support that evolution]
those needs are constantly changing - because our team and business is changing. people in the team gain new and different experiences, new people join, other people leave, and it’s not just the engineering org that this happens to - the entire business is changing constantly. different products within the same business may have different demands, and may necessitate different solutions.
so what, then, do I advocate? change I guess. most of what I do is about empowering the people involved to take ownership of what they do and how they do it.
maybe that’s agile, or maybe that’s anti-agile or even un-agile - I dont know. but for the teams that need it, it works.
how can I help your team? reach out and email me or schedule a call!