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
At a uniformly comfortable termperature In America our tendency has been to get away from thermal conditions as a determinant of behavior. Instead, we have used our technology to keep entire living and working complexes at a uniformly comfortable temperature. As a result, our spatial habits have become diffused, and activities that were once localized by thermal conditions have spread out over a whole house or building. We forget, unless a system breaks down, that such wide-ranging use of space is extremely dependent upon the available heating and cooling equipment. Lisa Heschong, Thermal Delight in Architecture Controlled environments spacebehavior