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
Finished on the inside "Those stretcher bars were finished on the inside in ways no one will ever know; I spent days, weeks, months finishing things no one is ever going to see. But it had much more to do with the fact that I couldn't leave them unfinished. I just had this conviction that in the sense of tactile awareness, if all those things were consistent, then the sum total would be greater, even though that might not be definable in any causal, connected way." Lawrence Wechler & Robert Irwin, Seeing Is Forgetting the Name of the Thing One Sees All the way throughInvisible substanceCompleting work properly in unseen areas craft