@[email protected] to ProgrammingEnglish • 25 days agoStudy finds 268% higher failure rates for Agile software projectswww.theregister.comexternal-linkmessage-square137fedilinkarrow-up1448arrow-down126cross-posted to: [email protected][email protected]
arrow-up1422arrow-down1external-linkStudy finds 268% higher failure rates for Agile software projectswww.theregister.com@[email protected] to ProgrammingEnglish • 25 days agomessage-square137fedilinkcross-posted to: [email protected][email protected]
minus-square@[email protected]linkfedilink43•25 days 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-square@[email protected]cakelinkfedilinkEnglish9•edit-225 days agoIf 2 and 3 happen the game is up. Management killed it. That’s not agiles fault.
minus-square@tylerlink1•23 days 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-square@[email protected]linkfedilink6•25 days agoThis 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.
Surely you’re not gonna blame the manager… /s
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.
This is the most accurate description of anything that’s ever been written.