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
Tilted Arc An Artwork by Richard Serra www.artdex.com In the 1980s, Serra found himself in the center of a public controversy over his piece titled Tilted Arc. While it was the government that approached him to create the work for downtown Manhattan’s Federal Plaza, the unveiling of the piece in 1981 was met with sharp criticism. The monumental sculpture was said to disrupt rush hour and the pedestrians who had to cut through the plaza daily. To the dismay of art lovers, the 120-foot-long, 12-foot-tall Tilted Arc was ultimately disassembled in 1989. Weathering SteelWrapped Reichstag20 Minutes in ManhattanPortal Park Slice cities