this post was submitted on 06 Jun 2024
473 points (89.2% liked)
Technology
59666 readers
2625 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
A more proper title would be “study finds 268% higher failure rates for poorly planned software projects”.
“Agile” as a word is mostly an excuse of poor planners for their poor planning skills.
Yeah, Agile isn't really at fault here. If done right - if you've got a scrum master, a proper product owner, proper planning and backlog grooming, etc. - it works really well. The problem is some companies think Agile is just "give the devs some pie-in-the-sky hopes and dreams, let 'em loose, and if they don't give half a dozen execs exactly what they want (despite their massively conflicting ideas on what they want), cancel the project."
In my experience it's just kanban, but make the devs feels guilty between sprints for not meeting their goals.
Absolutely It's so management can say "your velocity was down 15% this sprint" and not feel bad about it instead of saying "work more" It's plausible deniability for demanding unpaid overtime