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
Be A (Re)Visitor An Article by Rob Walker robwalker.substack.com I was thinking about this not long ago while reading in Petapixel an essay by a photographer named Scott Reither, “Long Form Study: Why Photographers Should Repeatedly Revisit A Scene.” In it, he described photographing one particular stretch of beach, over and over, throughout his career. Of course that landscape has changed over time, and of course he’s had moments when he felt he’d captured the same territory so many times there was nothing left to see. But there was always something more to see — maybe because of a change in Reither’s life, rather than in the physical environment. seeingchangephotography