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
Thermal aediculae The inglenook, the gazebo, and the porch swing also have strong definitions of their spaces. They are each a bit like a little house set off for a special thermal purpose. They might be termed "thermal aediculae". Although the term aedicula is most often used in conjunction with a sacred or ceremonial little house, it can also be used to describe any diminutive structure used to mark a place as special. Summerson contends that there is a basic human "fascination of the minitature shelter." Perhaps this is because the aedicula intensifies ones experience of the place by working someone like a caricature. By reducing some things in scale, it exaggerates the importance of other things, most especially the size of a person in relation to the space. Lisa Heschong, Thermal Delight in Architecture InglenookAediculaFolliesTo build a folly