ylai@lemmy.ml to Programming@programming.devEnglish · 1 年前Study finds 268% higher failure rates for Agile software projectswww.theregister.comexternal-linkmessage-square136linkfedilinkarrow-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.comylai@lemmy.ml to Programming@programming.devEnglish · 1 年前message-square136linkfedilinkcross-posted to: becomeme@sh.itjust.worksprogramming@lemmy.mlhackernews@lemmy.smeargle.fans
minus-squarelemmyvore@feddit.nllinkfedilinkEnglisharrow-up4·1 年前How did they know how to break things down into tasks? How did they know if a task would fit in a sprint? 😄
minus-squareKissaki@programming.devlinkfedilinkEnglisharrow-up3·1 年前We’re so agile the sprint became a time-block framework rather than a lock-down of tickets that we certainly will finish. (In part because stuff comes up within sprint.)
How did they know how to break things down into tasks? How did they know if a task would fit in a sprint? 😄
We’re so agile the sprint became a time-block framework rather than a lock-down of tickets that we certainly will finish. (In part because stuff comes up within sprint.)