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
Input as collage An Article by Austin Kleon austinkleon.com Your output depends on your input, but a lot of your input is random: you’re interested in lots of different things, and those things, occasionally, will talk to each other in your work. Lately I’ve been thinking about being more intentional with input. Thinking about input as collage. Taking the principle of juxtaposition (1+1=3) and using that to guide your input: what weird, seemingly disparate things can you feed your brain that will come out later in a new mix? The input collage can be subject or genre based and even better if it’s multi-media. ...There’s a balance here between feeding your brain intentionally and then backing off and letting your brain do the subconscious work of mixing your inputs together. creativityintent