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
Customers don't know what they want At the end of the presentation someone asked whether he thought they should do some market research to see what customers wanted. "No," he replied, "because customers don't know what they want until we've shown them." Then he pulled out a device that was about the size of a desk diary. "Do you want to see something neat?" When he flipped it open, it turned out to be a mock-up of a computer that could fit in your lap, with a keyboard and a screen hinged together like a notebook. "This is my dream of what we will be making in the mid- to late eighties," he said. They were building a company that would invent the future. Walter Isaacson, Steve Jobs The iMac