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
barnsworthburning.net A Website by Nick Trombley barnsworthburning.net What this site isColophonContact meShortlist of interesting spacesBehind the scenes Five barns worth burningExtract (n)Kicks Condor: barnsworthburningNodal pointsMonoskop collectionsnotetakingconnection
What this site is A kind of commonplace book. A kind of digital garden. A kind of Zettelkasten. The front end to a brain. Part research, part dissertation, part art project. A kind of essay, in the sense that it is an attempt. ...but at what? What is a commonplace?A Brief History of the Digital GardenZettelkastenare.naHighlighterThe Art of Looking SidewaysReading DesignEssayerGlaspMaintenance and Care gardens
Colophon airtable stores the majority of the content for the site. the front-end is written using svelte and its companion toolset, sveltekit. it is hosted as a digital ocean app. figma was used for some of the design – the rest was done in code (as I increasingly believe it should be). it is typeset with IBM plex sans Designing with code
Contact me You can reach me using this Airtable form – I would love to hear from you. I'm also on LinkedIn.
Shortlist of interesting spaces craftworkwalkingwwwnotetakingwordseuphonymelancholyzendarknessgardens