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
Non-architects In 1964, the historian Bernard Rudofsky curated a show at MoMA called Architecture Without Architects, celebrating the formal qualities of a range of traditional building practices drawn from around the world. Setting aside the endlessly troubled implications of the Western gaze on “primitive” cultures, the show had the very constructive impacts of encouraging formal diversity at a time when mainstream architecture had grown desperately, myopically monochromatic and of suggesting that “non-architects” were capable not only of making good judgments about their environments but of actually taking the lead in creating them. Michael Sorkin, 20 Minutes in Manhattan The Timeless Way of BuildingMost cities were mostly built by improvisationArchitecture Without Architects architecture