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
Men are not an abstraction Placing work and commerce near residences, but buffering it off, in the tradition set by Garden City theory, is fully as matriarchal an arrangement as if the residences were miles away from work and from men. Men are not an abstraction. They are either around, in person, or they are not. Working places and commerce must be mingled right in with residences if men, like the men who work on or near Hudson Street, for example, are to be around city children in daily life—men who are part of normal daily life, as opposed to men who put in an occasional playground appearance while they substitute for women or imitate the occupations of women. Jane Jacobs, The Death and Life of Great American Cities 9. Scattered Work genderwork