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
Marginalia Search A Website search.marginalia.nu I want to show you that that Internet you used to go exploring is still very much there. There are still tons of small personal websites, and a wealth of long form text from both the past and the present. So it's a search engine. It's perhaps not the greatest at finding what you already knew was there, instead it is designed to help you find some things you didn't even know you were looking for. The art of finding what you didn’t know you were looking forIn Defense of BrowsingMillion Short micrositessearchdiscoveryserendipity