3 ms·
The big problems I see are this: 1. Talking about "Agile" like it's a "thing" you can adopt (it's not). Agile is a description of a family of methodologies. O
by mindcrime 9y ago
The big problems I see are this:
1. Talking about "Agile" like it's a "thing" you can adopt (it's not). Agile is a description of a family of methodologies. Or, to be more precise, it's a set of principles and ideals which a large set of methodologies claim to incorporate and emphasize (and do so to varying degrees). Anyway, you don't adopt "Agile" you adopt Scrum, or Crystal, or AgileUP, or XP, or SAFE, etc. And yes, this matters, because people say "Agile says you do X" where this statement is basically incorrect for almost every value of X. "Agile" is not some heavyweight, prescriptive methodology that dictates a Jira workflow, blah, etc. It's your shitty implementation of Scrum, SAFE, etc. that dictates these things. But people get to use the excuse "this is Agile" if you argue against any part of the current process.
2. Completely missing sight of how the Agile Manifesto says "favor individuals and interactions over processes and tools" and implementing some highly prescriptive, top-down, command-and-control process. And thinking that "we're Agile" because we have daily scrums, use Jira (or Rally), and work in "sprints". Basically, people adopt the ceremony and some of the language used by some agile-family methodologies, but completely avoid the principles and ideals of Agile (and articulated in the Agile Manifesto).
3. Impedance mismatch between the way developers expect to work in an "Agile" environment, and what management wants. Basically, somebody in management read an HBR article or something that said "Agile lets you move faster" and misinterpreted that as "If we implement Agile, my developers will crank out more code faster, and I don't have to change anything else about how this company works".
- zwieback 9y agoYes, yes and yes!