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 state of energetic repose Read the text before designing it. Discover the outer logic of the typography in the inner logic of the text. Make the visible relationship between the text and other elements (photographs, captions, tables, diagrams, notes) a reflection of their real relationship. Give full typographic attention even to incidental details. Invite the reader into the text. Reveal the tenor and meaning of the text. Clarify the structure and the order of the text. Link the text with other existing elements. Induce a state of energetic repose, which is the ideal condition for reading. Robert Bringhurst, The Elements of Typographic Style The inner nature of material typography