▲ 36 ▼ 268% higher failure rates for Agile software projects (www.theregister.com) submitted 2 years ago by Renneder@sh.itjust.works [M] to c/becomeme@sh.itjust.works 14 comments fedilink hide all child comments
[+] MotoAsh@lemmy.world 2 points 2 years ago* (last edited 1 year ago) (2 children) [deleted] permalink fedilink source parent hideshow 2 child comments replies: [–] Heavybell@lemmy.world 2 points 2 years ago (1 child) That was my assumption, too. He also liked to seize on the idea that every sprint must produce something useable… Which I take to mean "give your client something to poke at and test, not a diagram" and he took to mean "every sprint must produce something useful to the client, that they can immediately put into production". permalink fedilink source parent hideshow 1 child comment replies: [+] MotoAsh@lemmy.world 2 points 2 years ago* (last edited 1 year ago) [deleted] permalink fedilink source parent
[–] Heavybell@lemmy.world 2 points 2 years ago (1 child) That was my assumption, too. He also liked to seize on the idea that every sprint must produce something useable… Which I take to mean "give your client something to poke at and test, not a diagram" and he took to mean "every sprint must produce something useful to the client, that they can immediately put into production". permalink fedilink source parent hideshow 1 child comment replies: [+] MotoAsh@lemmy.world 2 points 2 years ago* (last edited 1 year ago) [deleted] permalink fedilink source parent
[+] MotoAsh@lemmy.world 2 points 2 years ago* (last edited 1 year ago) [deleted] permalink fedilink source parent