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
It is a little world See how many a pretty thing I always from the cube can bring: Chair and sofa, bench and table, Desk to write at when I’m able, All the household furniture, Even baby’s bed I’m sure; Not a few such things I see; Stove and sideboard here can be. Many things, both old and new, My dear cube brings into view; So my cube much pleases me, Because through it so much I see. It is a little world. Ellen Lupton & J. Abbott Miller, The ABC's of ▲■●: The Bauhaus and Design Theory Cubed modularity