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
Most cities were mostly built by improvisation In Architecture Without Architects, Bernard Rudofsky documented the ways in which most cities were mostly built by improvisation, following no consistent formal design. Building was added to building, street to street, their forms adapting to different site conditions in the process of extension. Rudofsky thought that this hidden order is how most settlements of poor people develop and that the work of improvising street order attaches people to their communities, whereas 'renewal' projects, which may provide a cleaner street, pretty houses, and large shops, give the inhabitants no way to mark their presence on the space. Richard Sennett, The Craftsman I am hereNon-architects urbanism