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
On 'The Master and His Emissary' A Quote by Ian McGilchrist www.ttbook.org People who make works of art, whatever they might be, have gone to great trouble to make something unique which is embodied in the form that it is, and not in any other form, and that it transmits things that remain implicit ...Works of art are not just disembodied, entirely abstract, conceptual things. They are embodied in the words they’re in or in paint or in stone or in musical notes or whatever it might be. The work is what it meansThe meaning of musicIf a book can be summarized, is it worth reading? artmaterialmeaningform