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.
It is so easy to fall into the trap of contemplating a city’s uses one at a time, by categories. Indeed, just this—analysis of cities, use by use—has become a customary planning tactic. The findings on various categories of use are then put together into “broad, overall pictures.”
The overall pictures such methods yield are about as useful as the picture assembled by the blind men who felt the elephant and pooled their findings. The elephant lumbered on, oblivious to the notion that he was a leaf, a snake, a wall, tree trunks and a rope all somehow stuck together.