this post was submitted on 06 Jun 2024
1 points (100.0% liked)
Technology
58458 readers
4421 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
I think I would also need to see the point at which agile projects are scrapped vs waterfall and how much money is sunk into them by time of scrapping.
My company knows agile will fail more often but also that they fail earlier. So they take on more projects and those seemed to be a bit riskier compared to what they would take on if it were to go by waterfall process.
I am not an agile acolyte, but failure % alone is not convincing. "Fail early, fail often" is a common mantra for a reason.
I haven't read the article yet, but surely they can't be juxtaposing waterfall as the alternative to agile. The modern alternative, especially in small to medium businesses, would be kanban.
Kanban is Agile. They are pushing Impact Engineering.
Well that's news to me
Ehhhh...Kanban is much older than Agile even if they tried to subsume it and say it's an agile technique, so that's sort of right. But kanban vs "scrum" - which virtually everyone means when they say "agile" - is fair.
Within my company there is a mix of Scrum and Kanban, so Agile != Scrum.
I don't think it makes much sense to say "We are switching from Agile to Kanban", but "We are switching from Scrum to Kanban" does make sense (at least to me)