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 Wind-Up Bird and Tuesday's Women A Short Story from The Elephant Vanishes by Haruki Murakami Who I was supposed to beQuittingA regular wind-up toy world this is
Who I was supposed to be Probably, the seed of a schism had been there all along, however microscopic. But in time the gap widened, eventually taking me out of sight of who I was supposed to be. In terms of the solar system, if you will, I should by now have reached somewhere between Saturn and Uranus. A little bit farther and I ought to be seeing Pluto. And beyond that—let’s see—was there anything after that?
Quitting But stay on I didn’t. I don’t know exactly why I up and quit. Didn’t even have any clear goals or prospects of what to do after quitting.
A regular wind-up toy world this is A regular wind-up toy world this is, I think. Once a day the wind-up bird has to come and wind the springs of this world. life