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
I recommend eating chips An Essay by Sam Anderson www.nytimes.com Join me. Grab whatever you’ve got. Open the bag. Pinch it on its crinkly edges and pull apart the seams. Now we’re in business: We have broken the seal. The inside of the bag is silver and shining, a marvel of engineering — strong and flexible and reflective, like an astronaut suit. Lean in, inhale that unmistakable bouquet: toasted corn, dopamine, America, grief! We are the first humans to see these chips since they left the factory who knows when. They have been waiting for us, embalmed in preservatives, like a pharaoh in his dark tomb. Looking Closely is EverythingOne brick seeingdetailsfood