ylai@lemmy.ml to Programming@programming.devEnglish · 3 months agoStudy finds 268% higher failure rates for Agile software projectswww.theregister.comexternal-linkmessage-square137fedilinkarrow-up1442arrow-down126
arrow-up1416arrow-down1external-linkStudy finds 268% higher failure rates for Agile software projectswww.theregister.comylai@lemmy.ml to Programming@programming.devEnglish · 3 months agomessage-square137fedilink
minus-squarebecausechemistry@lemm.eelinkfedilinkarrow-up43·3 months ago Hack together a proof of concept Works well enough that management slaps a “done” sticker on it Pile of hacks becomes load bearing One or two dependencies change, the whole thing falls over Set evenings and weekends on fire to fix it Management brags about moving fast and breaking things, engineers quit and become cabbage farmers and woodworkers New graduates are hired, GOTO 1
minus-squaremctoasterson@reddthat.comlinkfedilinkarrow-up6·3 months agoThis is the most accurate description of anything that’s ever been written.
minus-squareGBU_28@lemm.eelinkfedilinkEnglisharrow-up12arrow-down3·edit-23 months agoIf 2 and 3 happen the game is up. Management killed it. That’s not agiles fault.
minus-squaretyler@programming.devlinkfedilinkarrow-up1·3 months agoBut that’s what agile sounds like to management. They don’t understand the “it’s held together by hopes and dreams” communication, because all they see is something that appears to work. So why would they invest anything else in it.
minus-square0x0@programming.devlinkfedilinkarrow-up5·3 months agoSurely you’re not gonna blame the manager… /s
This is the most accurate description of anything that’s ever been written.
If 2 and 3 happen the game is up. Management killed it.
That’s not agiles fault.
But that’s what agile sounds like to management. They don’t understand the “it’s held together by hopes and dreams” communication, because all they see is something that appears to work. So why would they invest anything else in it.
Surely you’re not gonna blame the manager… /s