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 Innovation Funnel A Comic by Tom Fishburne marketoonist.com Most organizations use some version of an innovation funnel to bring ideas to life. It starts with lots of ideas at the front end and then launches whatever survives all the way to the back end. Yet this Darwinian process of bringing ideas to life doesn’t necessarily lead to survival of the fittest ideas. If we’re not careful, the innovation funnel leads to survival of the safest ideas. Organizations are good at spotting risks. In an effort to improve success rates, organizations tend to put sharper teeth in the funnel. As ideas run the organizational gauntlet, they can get pruned, sheared, shaped, and watered down beyond recognition. On the way, they can lose the essence of the idea. They may lose their point of difference and reason for being. innovationideasnovelty