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
Five basic rules Five basic rules: (1) Record your work as notes to your future self and colleagues. Write notes so that someone fifty years from now (or more) will understand and be able to use the factual information you collected, perhaps for purposes quite different from the original reasons. Clearly separate facts from interpretations so these are not confusing to a future reader. (2) Establish a clear and consistent notebook format and process. I always include the data, place, main activities or events, weather conditions, and other people involves. The day, month, and year is the most important link between that particular point in time and other people’s records, separate data sheets that I filled out myself, photos, and most important, collected specimens. Documenting collecting strategies and protocols receives special attention. In the moment, these may seem like common knowledge for the field team, so sometimes no one bothers to write them out. (3) Don’t lose your field records! (4) Pack a camera, create a visual record. No matter how many words you write to describe a fossil locality, you can’t beat an actual photo, taken on the spot, annotated in pen, and pasted into your notebook. There is no substitute for a photograph you actually mark in “real time” in the field as the best way to preserve a lasting, accurate record for yourself, or for someone who has never seen the site or object in question. (5) Learning through sketches and diagrams. Photographs are great, but drawn what you see is a more powerful way to learn about spatial patterns and relationships. Even if you are not an expert at drawing, you can make sketches that are much more informative than words would be. Always include a scale, an orientation, and labels in your diagrams. Anna K. Behrensmeyer, Linking Researchers Across Generations Best practices