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 Abode of the Unsymmetrical The decoration of our classical interiors was decidedly regular in its arrangement. The Taoist and Zen conception of perfection, however, was different. The dynamic nature of their philosophy laid more stress upon the process through which perfection was sought than upon perfection itself. True beauty could be discovered only by one who mentally completed the incomplete. The virility of life and art lay in its possibilities for growth. In the tea room it is left for each guest in imagination to complete the total effect in relation to himself. Since Zennism has become the prevailing mode of thought, the art of the extreme Orient has purposely avoided the symmetrical as expressing not only completion, but repetition. Okakura Kakuzō, The Book of Tea Beauty and compression perfectionbeauty