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
Irwin Volumes Show image 0 Show image 1 Show image 2 Show image 3 Show image 4 Black Line Volume, String Line-Light Volume, Corridor String Piece, Line Rectangle "The resultant black rectangle was not what you "looked at" – there was actually nothing to focus on – but soon it brought the space into focus with a distinct visual snap. From inside, the light in the area seemed different, more substantial, and the wall color began to shift ambiguously. From outside the area, the tape seemed to lift the plane of the floor upward in your field of vision, and it also made the room seem wider and shallower than it really was." — Roberta Smith Robert Irwin, Robert Irwin: A Conditional Art You are the one that is changed