4 ms·
Just to illustrate an example of how people are using the term "agile" wrong: If you ask around, you'll notice that (many|most) people equate "agile" with "two
by mindcrime 11y ago
Just to illustrate an example of how people are using the term "agile" wrong:
If you ask around, you'll notice that (many|most) people equate "agile" with "two week sprints". But if you actually read the Agile Manifesto you find this:
Deliver working software frequently, from a
couple of weeks to a couple of months, with a
preference to the shorter timescale.
Agile does not dictate that you use two week sprints. In fact, th term "sprint" itself is not even part of agile! The term "sprint" comes from Scrum, which is simply one specific methodology which claims adherence to the agile philosophy. But Scrum != Agile. Agile can also be XP, Crystal Clear, or AUP, etc.
- bitwize 11y agoScrum is the easiest for management to grasp at a surface level so out of all the methodologies under the Agile banner Scrum is most readily and widely adopted. The problem is that Scrum "sprints" are like treating a marathon as 422 contiguous 100m dashes.
- mindcrime 11y agoThe problem is that Scrum "sprints" are like treating a marathon as 422 contiguous 100m dashes. Yep. Or to put it another way, too many shops seem to think that you can "sprint" ALL THE TIME. And while it's "only a metaphor", it's a meaningful one in this case. You can't: sprint -> sprint -> sprint -> sprint -> sprint -> sprint -> ∞ You have to: sprint -> sprint -> breather -> sprint -> breather -> sprint -> sprint -> breather -> ∞ or something like that.
- UK-AL 11y agoSprints aren't sprints. Replace sprint with time segment. And you get more accurate picture.
- mindcrime 11y agoSprints aren't sprints. Except when they are. And just using that term encourages people to treat them like actual sprints, instead of just metaphorical sprints. This is why I advocate for use of the term "iteration" instead. But even then, I think it's important to include "slack" iterations that are for random bug fixes, miscellaneous refactoring, etc., that is developer driven, not business user driven.