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
Phenomenal: California Light, Space, Surface A Book by Robin Clark www.goodreads.com Phenomenal: An IntroductionPhenomenal: Exhibited WorksStealth Architecture: The Rooms of Light and Space Seeing Is Forgetting the Name of the Thing One SeesRobert Irwin: A Conditional ArtThe Finish Fetish Artists art
Phenomenal: An Introduction An Essay Aesthetic palate cleansingUntitled (Light Canvas)Little Blank Riding HoodNot intended to be read until you have seenA vaporous middle-world+5 More
Phenomenal: Exhibited Works A Gallery Untitled (Light Canvas)EindhovenStuck RedZero MassLittle Blank Riding Hood+4 More
Stealth Architecture: The Rooms of Light and Space An Essay by Michael Auping To absorb it or build your ownA stealth architectThe measuring unit of all spaceThe walls are reserved for the sunA little too something+1 More