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
Life as Protest A Fragment by Craig Mod craigmod.com I’ve written this before but I constantly need to remind myself of it, so, once again: A certain kind of work, lifestyle, mode of living — in and of itself — is protest. That is, work that is curious and rigorous is implicitly an antipode to didactic, shallow bombastity. It is inherently an archetype against bullshit. That to be committed to this work or life of rigor (be it rigor focused on “art” or, as they say in Japanese, sakuhin, or family or athleticism or whatever), and to share it with the world is to opt-out of being paralyzed by idiocy, and help others who may be paralyzed find a path back to whatever fecundity of life it is that they deserve. lifeworksociety