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
It's dark outside As soon as Te Shan crossed the threshold he said, "Long have I heard of Lung T'an (Dragon Pond), but now that I've arrived here, there's no pond to see and no dragon appears." Master Lung T'an came out from behind a screen and said, "You have really arrived at Lung T'an." Te Shan bowed and withdrew. During the night, Te Shan entered Lung T'an's room and stood in attendance till late at night. Lung T'an said, "Why don't you go?" Te Shan bade farewell, lifted up the curtain, and went out; he saw that it was dark outside, so he turned around and said, "It's dark outside." Lung T'an lit a paper lantern and handed it to Te Shan; as soon as Te Shan took it, Lung T'an blew it out. Te Shan was vastly and greatly enlightened. Yuanwu Keqin, Thomas Cleary & J.C. Cleary, The Blue Cliff Record In a state of reverberation