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
Deliberate acts I do not know what one should call the landscape of a long cultivated countryside, or the enchanting pattern of lights which shows at night time in a modern city seen from overhead. Are these not works of art? It is scarcely justifiable to say that these things have taken shape by chance. Each part of them has been made as it is by what seemed a deliberate act, and it need not necessarily be assumed to be a matter of chance that the results of many acts of many men over a considerably period of time should harmonize together aesthetically. David Pye, The Nature and Aesthetics of Design The Timeless Way of BuildingA Pattern Language evolutionurbanism