this post was submitted on 06 Jun 2024
2 points (100.0% liked)

Technology

61227 readers
4220 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 2 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
2
Study finds 268% higher failure rates for Agile software projects (www.theregister.com)
submitted 7 months ago by sir_pronoun@lemmy.world to c/technology@lemmy.world
104 comments fedilink hide all child comments
 

We all knew it

you are viewing a single comment's thread
view the rest of the comments
[–] Vanth@reddthat.com 0 points 7 months ago (1 children)

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.

[–] grrgyle@slrpnk.net 0 points 7 months ago (1 children)

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.

[–] CameronDev@programming.dev 0 points 7 months ago (2 children)

Kanban is Agile. They are pushing Impact Engineering.

[–] grrgyle@slrpnk.net 0 points 7 months ago

Well that's news to me

[–] drphungky@lemmy.world 0 points 7 months ago* (last edited 7 months ago) (1 children)

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.

[–] CameronDev@programming.dev 0 points 7 months ago

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)