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.
In a natural landscape, each element is part of the greater whole, a sophisticated and intricate web of connections and energy flows. If we attempt to create landscapes using a strictly objective viewpoint, we will produce awkward and dysfunctional designs because all living systems are more than just a sum of their parts. Our culture has tried to define the landscape scientifically, by collecting extensive data about its parts.
These methods are much like the group of blind mullahs in the Sufi tale, who try to describe an elephant.