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
Senior craftsperson A Fragment by Wilson Miner staff.design The thing that you’re talking about though, which I’ve never seen a mature company really have a sustainable space for, is the “senior craftsperson.” They’re not pivoting at some point in their career to saying “I’m going to take what I know and leverage it through other people.” They’re saying “I want to get better infinitely at the thing that I do.” I believe that that’s possible. You see it more in pure-art kind of careers. Like “I’m an illustrator” or “I’m a concept artist” or something, and there’s a need for that person being really fucking good at that one thing, and continuing to do that one thing. I think a lot of people can intuitively understand why that would be really satisfying for someone as a career path. The dual ladder craftwork