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
Aedicula Front of the Library of Celsus with aediculae in Ephesus. In ancient Roman religion, an aedicula (plural aediculae) is a small shrine. Many aediculae were household shrines that held small altars or statues of the Lares and Penates, household gods guarding the entire house. Other aediculae were small shrines within larger temples, usually set on a base, surmounted by a pediment and surrounded by columns. In ancient Roman architecture the aedicula has this representative function in the society. They are installed in public buildings like the triumphal arch, city gate, and thermae. From the 4th century Christianization of the Roman Empire onwards such shrines, or the framework enclosing them, are often called by the Biblical term tabernacle, which becomes extended to any elaborated framework for a niche, window or picture. Wikipedia en.wikipedia.org Thermal aediculae