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
Controlled environments “Controlled environments” are another of modernism’s great obsessions. Extravagant amounts of energy are spent to keep buildings—as well as skyway systems, shopping malls, and domed stadia—at a constant temperature year-round via entirely mechanical means. The folly is not simply a touchy-feely isolation from the authenticities of nature, which can admittedly be cruel, but a larger disciplinary presumption that seeks to extend the centralized authority (central air, central government) of power ever more comprehensively. It is possible that this particular hubris may have pushed Gaia to the tipping point. Michael Sorkin, 20 Minutes in Manhattan At a uniformly comfortable termperatureFascination with control sustainabilitycontrol