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
Forces of conflict A pattern which prevents us from resolving our conflicting forces leaves us almost perpetually in a state of tension. For, if we live in a world where work is separated from family life, or where courtyards turn us away, or where windows are merely holes in the wall, we experience the stress of these inner and conflicting forces constantly. We can never come to rest. We are living then, in a world so made, so patterned, that we cannot, by any stratagem, defeat the tension, solve the problem, or resolve the conflict. In this kind of world the conflicts do not go away. They stay within us, nagging, tense…The build-up of stress, however minor, stays within us. We live in a state of heightened alertness, higher stress, more adrenaline, all the time. Christopher Alexander, The Timeless Way of Building Fucking up the world