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
The Chef Show: Wolfgang Puck A Series from The Chef Show by Jon Favreau, Roy Choi & Wolfgang Puck www.netflix.com If you can't beat the classics
If you can't beat the classics Choi: I love [this contemporary banana cream pie] because sometimes new presentations create that iconic or nostalgic thing, but then they don't taste like nostalgia. But this one tastes like a banana cream pie. Puck: So many young chefs today forget that food has to be delicious. If it's not delicious, why do it? If it's just interesting, you go once, that's it – "okay, I get it, but I don't want to go back." Choi: I hear you chef. That's what I teach my cooks. I say, "You can do anything you want, but if you can't beat a banana cream pie, then the banana cream pie still wins." In most cases they don't. They can't beat the original. foodnostalgiaprogress