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
The Topography of Tears A Book by Rose-Lynn Fisher www.rose-lynnfisher.com Show image 0 Show image 1 The Topography of Tears is a visual investigation of tears photographed through an optical, standard light microscope, a vintage Zeiss from the late 1970's, mounted with a digital microscopy camera. Tears are the medium of our most primal language in moments as unrelenting as death, as basic as hunger, and as complex as a rite of passage. They are the evidence of our inner life overflowing its boundaries, spilling over into consciousness. Wordless and spontaneous, they release us to the possibility of realignment, reunion, catharsis, intractable resistance short-circuited. Shedding tears, shedding old skin. It’s as though each one of our tears carries a microcosm of the collective human experience, like one drop of an ocean. melancholyemotiontopologygeometry