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
Narrative Strategy An Article by Tom Critchlow tomcritchlow.com An unfolding network of associations
An unfolding network of associations We know strategy is an unfolding network of associations: The evidence from the case suggests that the concept of strategy can be reappraised. From strategy as a static set of choices made at a specific point in time to strategy as an unfolding network of people, shared experiences and artifacts that is constantly being remade. And we know that only 30% of employees can articulate a company’s strategy. And I believe in the hyper-connected age we live in both of these things are becoming more true - that strategy is increasingly “in motion” and that most organizations are realizing their OODA loops are too slow for the modern world. This causes the articulation of strategy to stall and get left behind - how do you articulate something in motion? It’s easier to write strategy down when it doesn’t change right? As a result - there’s a widening gap between the perspective on strategy that the executive team has and the received ideas of the company’s direction that teams and employees have. work