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
Silence A Book by John Cage archive.org I would want to be in that darkness The Sound Of Silence soundsilencemusicartzen
I would want to be in that darkness If there were a part of life dark enough to keep out of it a light from art, I would want to be in that darkness, fumbling around if necessary, but alive. And I rather think that contemporary music would be there in the dark too, bumping into things, knocking others over and in general adding to the disorder that characterizes life (if it is opposed to art) rather than adding to the order and stabilized truth beauty and power that characterize a masterpiece (if it is opposed to life). And is it? It is. artdarknessmusic