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
Sonorisms I the authenticity of the gesture as if the air had taken on substance representation and re-presentation a first order of presence this painterly game of pick-up sticks Irwin's "fetish finish" questions all of whose possible answers would never exhaust them the art is what has happened to the viewer an art of things not looked at a dialogue of immanence the information that takes place between things your house is the last before the infinite his "project of general peripatetic availability" that shiver of perception perceiving itself a desert of pure feeling Lawrence Wechler & Robert Irwin, Seeing Is Forgetting the Name of the Thing One Sees PhonaestheticsArchitectural dark matter wordseuphony