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 Gifted Listener: Composer Aaron Copland on Honing Your Talent for Listening to Music An Article by Maria Popova www.brainpickings.org The poetry of music, Copland intimates, is composed both by the musician, in the creation of music and its interpretation in performance, and by the listener, in the act of listening that is itself the work of reflective interpretation. This makes listening as much a creative act as composition and performance — not a passive receptivity to the object that is music, but an active practice that confers upon the object its meaning: an art to be mastered, a talent to be honed. Music and ImaginationTo see is to forget the name of the thing one seesThe core assertion musicpoetryartmeaning