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
To build a folly To build a folly is essentially to do something a second time, something at an inopportune moment. That something is always the memory of something forgotten, about which we can paradoxically say "There it is again." Follies were misunderstood, purposeless constructions. They were often only small, extravagant gestures in a garden, easily whisking off the imagination to distant lands, a sort of time capsule built to awaken the memory and induce surprise in passers-by. They marked locations, organized secondary paths in a park, or simply predicted the arrival of better times—a demarcation, a sacred spot, a mysterious trail, a hill whose tragic rocky nature begged for a tower, a party, or the arrival of summer. Smiljan Radić, Death at Home Designed to be ruinsFolliesThermal aediculae meaningpurposeconstruction