re: Is Jira an antipattern? VIEW POST


The reason Waterfall exists is because it adds structure to an otherwise chaotic endeavour, by having large projects have a prescribed flow. What it misses is self-checks and the ability to shift course when needed.

Agile (and in particular Scrum) tries to remedy this by using much shorter cycles. And I say shorter because Waterfall also cycles, but on a project level, with the (large) chance that the product gets scrapped before a follow-up project is started.

That's structurally the biggest difference between Agile and Waterfall (though communication of course comes in as a big tooling difference). So shouldn't be that big of a surprise that an Agile tool feels Waterfall-y at the lowest level.

code of conduct - report abuse