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
Joiners A Photograph by David Hockney www.hockney.com Show image 0 Show image 1 In the early 1980’s, English painter David Hockney began creating intricate photo collages that he called “joiners”. His earlier collages consisted of grid-like compositions made up of polaroid photographs. He then switched to photo lab processed 35mm photographs and created collages that took on a shape of their own, creating abstract representations of the scenes he had photographed. The varied exposures of the individual photographs that make up each collage give each work a fluidity and movement that otherwise might not be found. Start drawing, then put the box around it