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
Haven't you noticed? I remember my mother sitting me down at the age of about five with pencil and paper to draw an acacia tree in the yard while she busied herself with her own sketchbook. After a while she came over to see my efforts. “Splendid! But haven’t you noticed how the trunk narrows as it rises? And see how the branches flatten out sideways, not like that oleander over there, where they all go up at a steep angle. Now don’t rub that one out, just do another drawing to compare with the first one.” Jonathan Kingdon, In the Eye of the Beholder Looking Closely is Everything seeing