▲ 422 ▼ Study finds 268% higher failure rates for Agile software projects (www.theregister.com) submitted 2 years ago by ylai@lemmy.ml to c/programming@programming.dev 135 comments fedilink hide all child comments
[–] iamtherealwalrus@lemmy.world 15 points 2 years ago (4 children) On all the agile projects I've worked on, the teams have been very reluctant to make a specification in place before starting development. Often claiming that we can't know the requirements up-front, because we're agile. permalink fedilink source parent hideshow 8 child comments replies: [–] lysdexic@programming.dev 16 points 2 years ago On all the agile projects I’ve worked on, the teams have been very reluctant to make a specification in place before starting development. I don't think this is an Agile thing, at all. I mean, look at what Agile's main trait: multiple iterations with acceptance testing and product&design reviews. At each iteration there is planning. At each planning session you review/create tickets tracking goals and tasks. This makes it abundantly clear that Agile is based in your ability to plan for the long term but break/adapt progress into multiple short-term plans. permalink fedilink source parent [–] pivot_root@lemmy.world 11 points 2 years ago (1 child) For your sake, I hope your employment was agile as well. Those jobs sound like they were dumpster fires waiting to happen. permalink fedilink source parent hideshow 2 child comments replies: [–] kippinitreal@lemmy.world 9 points 2 years ago* Also seems like a shitty get-outta-jail-free card. With no design in place, timelines and acceptance criteria can't be enforced. "Of course we're done now, we just decided that we're done!" permalink fedilink source parent [–] Anticorp@lemmy.world 4 points 2 years ago That's boneheaded. permalink fedilink source parent [–] lemmyvore@feddit.nl 4 points 2 years ago (1 child) How did they know how to break things down into tasks? How did they know if a task would fit in a sprint? 😄 permalink fedilink source parent hideshow 2 child comments replies: [–] Kissaki@programming.dev 3 points 2 years ago 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.) permalink fedilink source parent
[–] lysdexic@programming.dev 16 points 2 years ago On all the agile projects I’ve worked on, the teams have been very reluctant to make a specification in place before starting development. I don't think this is an Agile thing, at all. I mean, look at what Agile's main trait: multiple iterations with acceptance testing and product&design reviews. At each iteration there is planning. At each planning session you review/create tickets tracking goals and tasks. This makes it abundantly clear that Agile is based in your ability to plan for the long term but break/adapt progress into multiple short-term plans. permalink fedilink source parent
[–] pivot_root@lemmy.world 11 points 2 years ago (1 child) For your sake, I hope your employment was agile as well. Those jobs sound like they were dumpster fires waiting to happen. permalink fedilink source parent hideshow 2 child comments replies: [–] kippinitreal@lemmy.world 9 points 2 years ago* Also seems like a shitty get-outta-jail-free card. With no design in place, timelines and acceptance criteria can't be enforced. "Of course we're done now, we just decided that we're done!" permalink fedilink source parent
[–] kippinitreal@lemmy.world 9 points 2 years ago* Also seems like a shitty get-outta-jail-free card. With no design in place, timelines and acceptance criteria can't be enforced. "Of course we're done now, we just decided that we're done!" permalink fedilink source parent
[–] lemmyvore@feddit.nl 4 points 2 years ago (1 child) How did they know how to break things down into tasks? How did they know if a task would fit in a sprint? 😄 permalink fedilink source parent hideshow 2 child comments replies: [–] Kissaki@programming.dev 3 points 2 years ago 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.) permalink fedilink source parent
[–] Kissaki@programming.dev 3 points 2 years ago 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.) permalink fedilink source parent