Dealing with Technical Stories
One of the first thing they tell us about stories, is that they should be valuable. That’s what the ‘V’ in INVEST stands for: Taken from: http://en.wikipedia.org/wiki/INVEST_(mnemonic): V – Valuable – A user story must deliver value to the end user. That suggestion usually sits quite well with business side people, which nods in agreement when they […]
Revising Estimation
Many teams feel the need to go over finished stories and update their story points in order to reflect the amount of effort needed to complete them. They general notion is that it’s a good idea to fix the original estimates in order to reflect the “true” velocity of the team. Which later on will […]
If you Want to Scale up – Use Small Stories
Much has been written about the importance of working in short cycles, and the need to cut and slice your stories to small pieces that will fit inside of a single sprint. I’m not going to repeat all this. What I would like to write about is something that might seem counter intuitive at first […]