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
Only a mind opened to the quality of things Only a mind opened to the quality of things, with a habit of discrimination, sensitized by experience and responsive to new forms and ideas, will be prepared for the enjoyment of this art. The experience of the work of art, like the creation of the work of art itself, is a process ultimately opposed to communication as it is understood now. What has appeared as noise in the first encounter becomes in the end message or necessity, though never message in a perfectly reproducible sense. You cannot translate it into words or make a copy of it which will be quite the same thing. Meyer Schapiro, Robert Irwin: A Conditional Art The work is what it meansThe medium is the messageWhat the painting was not about