@ylai@lemmy.ml to Programming@programming.devEnglish • 6 months agoStudy finds 268% higher failure rates for Agile software projectswww.theregister.comexternal-linkmessage-square137fedilinkarrow-up1449arrow-down126cross-posted to: becomeme@sh.itjust.worksprogramming@lemmy.mlhackernews@lemmy.smeargle.fans
arrow-up1423arrow-down1external-linkStudy finds 268% higher failure rates for Agile software projectswww.theregister.com@ylai@lemmy.ml to Programming@programming.devEnglish • 6 months agomessage-square137fedilinkcross-posted to: becomeme@sh.itjust.worksprogramming@lemmy.mlhackernews@lemmy.smeargle.fans
minus-square@lysdexic@programming.devlinkfedilinkEnglish1•6 months agoAgile is not a system. It’s a set of principles, set by the Agile manifesto. The Agile manifesto boils down to a set of priorities that aren’t even set as absolutes. I strongly recommend you read upon Agile before blaming things you don’t like on things you don’t understand .
minus-square@Grandwolf319@sh.itjust.workslinkfedilink1•edit-26 months agoI have read those principles, many years ago. Those principles sound great but they are not compatible with management. If management is gonna be part of the picture then agile principles are not beneficial to a developer experience, regardless of what unachievable ideal they talk about.
Agile is not a system. It’s a set of principles, set by the Agile manifesto.
The Agile manifesto boils down to a set of priorities that aren’t even set as absolutes.
I strongly recommend you read upon Agile before blaming things you don’t like on things you don’t understand .
I have read those principles, many years ago.
Those principles sound great but they are not compatible with management.
If management is gonna be part of the picture then agile principles are not beneficial to a developer experience, regardless of what unachievable ideal they talk about.