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 true that [the artist], like everybody else, derives remuneration from his work (though not, strictly speaking, profit in the financial sense, of the word, since what he invests in his work is not money but time and skill, whose returns cannot be calculated in percentages). The remuneration is frequently beyond the amount necessary to enable him to go on working. What is remarkable about him is the way in which he commonly employs the escape-from-work which the extra remuneration allows him. If he is genuinely an artist, you will find him using his escape-from-work in order to do what he calls “my own work”, and nine times out of ten, this means the same work (i.e. the exercise of his art) that he does for money. The peculiar charm of his escape is that he is relieved, not from the work but from the money.
What distinguishes him here from the man who works to live is, I think, his desire to see the fulfilment of the work.