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
I can only conceive for you I cannot perceive for you. I can conceive for you and we can then in a sense hold a general agreement about quality of conception and we may all operate under it and that's what is known as a common agreement. But the area of perceiving as such is totally individual, there's no way that we carry it in that sense. This is not an antisocial gesture; it is in fact a highly ethical one, since trying to get another person to see what and how you see has the potential to become a violation of the other's own autonomy: There is nothing more unethical than having ambitions for someone else's mind. Robert Irwin, Robert Irwin: A Conditional Art Ambitions for someone else's mind