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
The inventive process was often a nonverbal one Through the ages, the professional users of tools by and large have not needed to, been able to, or wanted to talk to outsiders about their implements. They did not need to because tools themselves are used to make other tools, and thus users could very often fashion a new tool with their old ones. If they did need to communicate the design for a new tool to someone outside their trade, they could do so without having to reveal the tool's intended use...Besides, the inventive process of conceiving a new tool was often a nonverbal one. Finally, craftsmen were unwilling to share information about their specialized tools because to do so would have been to give up their competitive edge and their value to those outside the craft. Henry Petroski, The Evolution of Useful Things Focal awareness tools