I see this sometimes: To be agile requires technical practices, that's the foundation. If technical practices are ignored (which is the common case), we get FlaccidScrum.
I might agree, but I need to ask, what are the technical practices for an org transformation project? and what are the technical practices for installing a clean water system in a rural village?
Expansion on the question: XP was mostly tech practices for programming. Scrum contains no tech practices for any domain. People complain about SCrum that it misses XP's tech practices. Now I see general comments that "agile in general" is missing XP's tech practices, but they don't say "XP's tech practices", they say just "tech practices."
But agile is applicable everywhere, not just programming. When you are not in programming, XP's tech practices are not relevant ---- so, if we choose to agree that tech practices are essential to agile, we have to ask what are those tech practices that apply to some other endeavor.
People who know me also spot here that this is my way of rebutting the assertion that tech practices are the foundation of agile. if you/they can't name the tech practices for other fields, then the assertion "tech practices are the foundation of agile" is false.
So it is both an interesting question in its own right, and a challenge to the assertion. Typical Alistair styles, lol.
@totheralistair IMHO this is a little bit sad that most people think that XP "was mostly tech practices for programming" and not ways to build kickass teams
@alexvictoor
i don't know if you were there when it was created, it was definitely pitched as mostly tech practices for programming.
Any kickass team construction was a side effect that appeared after the fact --
then, there are surely ways to build kickass teams that don't require red-green refactoring and automated regressions unit tests.
