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 indie web manifesto A Definition web.archive.org While commercial websites display more and more agressive messages, target and track their users, the indie web respects the individuals, their intelligence and their privacy; it’s an open forum for thoughts and debate. While purely commercial websites turn into information and entertainment magazines, while tycoons of media, telecom, computing and military agencies fight for the control of the Internet, the indie web offers a free vision of the world, bypasses the economic censorship of news, its confusion with advertising and infommercial, its reduction to a dazing and manipulating entertainment. www