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
Induced demand Every attempt to cul-de-sac city streets, to change traffic patterns in favor of pedestrians, or to narrow street ends is met with the same howl of protest from the authorities: this will increase congestion because urban traffic is a zero-sum game. Any reduction in volume in one place in the city will inevitably be accompanied by a rise in traffic somewhere else. This claim is fallacious: the true corollary is the opposite. In case after case, a reduction of the space available for vehicular traffic has simply resulted in the reduction of traffic overall. Michael Sorkin, 20 Minutes in Manhattan Like trying to cure obesity by loosening your belt transportation