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
Eyes on the ground A Quote by Akira Kurosawa www.youtube.com When you go mountain climbing, the first thing you’re told is not to look at the peak but to keep your eyes on the ground as you climb. You just keep climbing patiently one step at a time. If you keep looking at the top, you’ll get frustrated. I think writing is similar. You need to get used to the task of writing. You must make an effort to learn to regard it not as something painful but as routine. writingexperienceskill