this post was submitted on 02 Jun 2025
681 points (98.7% liked)
memes
15345 readers
3295 users here now
Community rules
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to !politicalmemes@lemmy.world
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads
No advertisements or spam. This is an instance rule and the only way to live.
A collection of some classic Lemmy memes for your enjoyment
Sister communities
- !tenforward@lemmy.world : Star Trek memes, chat and shitposts
- !lemmyshitpost@lemmy.world : Lemmy Shitposts, anything and everything goes.
- !linuxmemes@lemmy.world : Linux themed memes
- !comicstrips@lemmy.world : for those who love comic stories.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That may be true in some truly well organized (usually "legacy big corpo" companies).
Where I've worked it's more like:
That is a basic side-effect of Agile development. If you have implementation details figured out to such an extent before writing the code, you are not doing agile, you are doing waterfall. Which has a time and a place, but that time and place is typically banking or medical or wherever you're okay with spending several times the time and money to get maximum reliability (which is a different metric than quality!).
I bet NVIDIA has driver crashes to figure out, and I know which of those issues I'd want them to focus on first if I used their windows driver.
I've been a PM for about 7 years and God do I miss waterfall. My team is lucky to get a week or two of testing now and that usually puts us right at code freeze so any issues we find we now have to justify to multiple teams and dev on why it needs to be fixed.
How much of it is due to Agile (which is a very broad concept even though some people mistakenly equate it with scrum), and how much is it due to corporate pressures and inadequate processes though?
I find Agile conceptually meshes a lot better with "standard" product and solutions development thanks to the tighter feedback loops and increased reliance on local expertise over centralized planning. This only gets truer as project complexity grows.
However some companies try to make Agile work with top-down decision making and/or hard deadlines, which are deadly antipatterns. As for lack of time/resources and/or timesheet micro-management, this isn't a problem unique to Agile nor something that waterfall is exempt from.
Good agile teams are mostly independent and can define their own testing/release cycle as required for a given project; though of course when that happens there are at least a couple layers of management who feel a burning itch to stuff their dirty nosed where they don't belong because if the team succeeds despite their lack of direct involvement then everyone might realize the emperor has no pants.
Agile in corpo is usually the soul-crushing, not working kind, where the participants don't get the decision power they need for it to be working and not soul-crushing.
Sure, but I don't think Waterfall is going to save you from the soul-crushingness in such an environment.