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
Rain chains An Object www.rainchains.com Rain chains are a beautiful and functional alternative to traditional, closed gutter downspouts. Guiding rain water visibly down chains or cups from the roof to the ground, rain chains transform a plain gutter downspout into a pleasing water feature. From the soft tinkling of individual droplets to the soothing rush of white water, they are a treat to listen to. Rain chains (‘kusari doi’ in Japanese) in concept are not a new idea. For hundreds of years, the Japanese have used the roof of their homes to collect water, transporting it downward with chains and finally depositing the rain water into large barrels for household water usage. Japanese temples often incorporate quite ornate and large rain chains into their design. Rain Chains & Musical Drains water