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
Poems of an Indian summer To build one's house is very much like making one’s will. When the time does arrive for building this house, it is not the mason’s nor the craftsman’s moment, but that moment in which every man makes one poem, at any rate, in his life. And so, in our towns and their outskirts, we have had during the last forty years not so much houses as poems, poems of an Indian summer, for a house is the crowning of a career. Le Corbusier, Towards a New Architecture Rand HillJapanese Death PoemsEach ruler commissioned his own gardenThe Abode of Fancy melancholyhomedeathpoetry