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
A concept of style It is a concept based not on the classification of various physical features of architecture and urban design but on the problem-solving process itself. We have seen that the final outcome of a design process is strongly determined by at least three aspects of that process: the subject matter of the organizing principles which are adopted, the manner in which these principles are interpreted and reinterpreted in the context of the problem at hand, and the sequent of applying such organizing principles. Consistency in style among the output of designers can thus be understood as a habitual way of doing things, of solving problems. Peter G. Rowe, Design Thinking It was all change until the very last second style