Why we stopped breaking down stories into tasks An Article by Adam Silver adamsilver.io The Scrum process says to break down stories into tasks to make estimation easier, encourage collaboration and to be able to show more granular progress during a sprint. But after a few sprints, we decided to do the next sprint without creating tasks. As a result we drastically increased our velocity and never went back. Here I'll jot down some of the reasons we decided to do this: Breaking down stories into tasks is time consuming The tasks we came up with invariably would change as we worked on the stories Tasks are repetitive Tasks were often carried out in parallel Our estimates didn't improve It decluttered our task board It encouraged collaboration throughout the sprint While we started our process by following Scrum to the letter, we soon realised that breaking down stories into tasks was something that wasn’t worthwhile for us. In the end we realised that it was overplanning and poor use of our time. In the end we used that time to get on with the work and deliver at a significantly faster pace. Why We Don't Do Daily Stand-Ups at Supercede agile
Five barns worth burning I walked around with a map, penciling in X’s wherever there was a barn or shed. For the next three days, I covered four kilometers in all four directions. Living toward the outskirts of town, there are still a good many farmers in the vicinity. So it came to a considerable number of barns—sixteen altogether. I carefully checked the condition of each of these, and from the sixteen I eliminated all those where there were houses in the immediate proximity or greenhouses alongside. I also eliminated those in which there were farm implements or chemicals or signs that they were still in active use. I didn’t imagine he’d want to burn tools or fertilizer. That left five barns. Five barns worth burning. Haruki Murakami, Barn Burning barnsworthburning.net i