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
Design with courage Make a bold decision (that is controversial). Make a mistake (as a result of a bold decision). Challenge “conventional wisdom”. Challenge authority (that preaches conventional wisdom). Challenge hierarchy (that perpetuates conventional wisdom). Ignore the committee (and the need to converge). Decide who your clients are (and aren’t). Ignore clients that aren’t (especially those who pay the most). Cultivate clients if none exists (instead of compromising your design). Be a generalist (and ignore your job title). Be a specialist (who specializes in being a generalist). Design things from scratch (and build them yourself from scratch). Design things that no one wants (yet). Design freely (and think freely). Chuánqí Sun, The vanishing designer The boldest decisions design