ylai@lemmy.ml to Programming@programming.devEnglish · 6 months agoStudy finds 268% higher failure rates for Agile software projectswww.theregister.comexternal-linkmessage-square120fedilinkarrow-up1429cross-posted to: programming@lemmy.mlhackernews@lemmy.smeargle.fans
arrow-up1429external-linkStudy finds 268% higher failure rates for Agile software projectswww.theregister.comylai@lemmy.ml to Programming@programming.devEnglish · 6 months agomessage-square120fedilinkcross-posted to: programming@lemmy.mlhackernews@lemmy.smeargle.fans
minus-squareskoberlink@lemmy.worldlinkfedilinkarrow-up12·edit-26 months agoI understand the frustration; almost nowhere does agile “right”. However, this is a gross misrepresentation of the philosophy. Specifically it leaves out and ignores this very important part: That is, while there is value in the items on the right, we value the items on the left more. As seen on agilemanifesto.org The base philosophy is meant to remind us what we are here to do: make software (or whatever project we’re working on), not become dogmatic about processes or tools or get bogged down in peripheral documentation.
I understand the frustration; almost nowhere does agile “right”. However, this is a gross misrepresentation of the philosophy.
Specifically it leaves out and ignores this very important part:
As seen on agilemanifesto.org
The base philosophy is meant to remind us what we are here to do: make software (or whatever project we’re working on), not become dogmatic about processes or tools or get bogged down in peripheral documentation.