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
They can smell the wood All of the wooden shelves used for storing books were on the warehouse's first floor. We decided to keep these shelves as they were to form a library, and we also created a small lecture hall for holding talks by writers and makers. Although contemporary society is moving away from books and towards computers and information technology, people nevertheless have a strong feeling of connection to – and nostalgia for – trees and things that are made from wood. La kagu is a space where visitors can really get a sense of the culture of books. When they step inside, some even say that they can smell wood. Kengo Kuma, My Life as an Architect in Tokyo The Eyes of the Skin: Architecture and the Senses woodsensesbooks