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
In the walls and mosses If we reach such a very ordinary state of daily life, and then back it up with building and construction that comes from the depths in us, then that gradually accumulates our value in the world, all of us together as a whole. Later, then, perhaps hundreds of years later, people will look back at our stones and say to themselves, "My word, those people way back then — they certainly knew how to live," and they would say this because they could see the lingering whispers in the walls and mosses, and could read them, and could treasure them, and would learn from these traces how to live like that again. Christopher Alexander, The Battle for the Life and Beauty of the Earth From body to body life