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 web in decay is the web by design An Essay by Chia Amisola chias.blog When will there be a guide to best practices for archiving the web? Will the giants responsible for the platformization of the web make the act of digital archival any easier for us? Is it foolish for platforms like Snapchat or Instagram Stories to brand themselves as “temporary” when temporariness is impossible on our internet? Should the web exist as something organic, malleable, and destructible –– or as an eternal timekeeper? Is link rot more of a technological issue or a human one? Do humans want to know themselves forever? The Internet Is Rotting decaywww