Is the bug to the left a large bug or a small bug? It looks HUGE to me! Well, in reality it is probably between .5 and .75 inches long. Not really a very big bug at all. Why do we care? Because trying to size the fixing of software “bugs” is at least as hard as figuring out how big this bug is!
When I teach an Agile or Scrum course someone will almost always ask a question like “How do you handle bug fixes in iterations or sprints?” When I ask “How do you want to handle them?” we get into a pretty interesting discussion. Most people say something similar to “We should prioritize them with the user stories, size them like we do user stories and then see what fits into each iteration.” I usually smile and ask any developers if they know ahead of time how long it will take to fix a defect. They ALWAYS say “Sometimes.” And THAT is the problem! [Read more...]
What’s wrong with the user story on the card? It seems to have everything we need: a) short title, b) a size (in this case 2), and c) a well-written story using the standard “As a … I want … so that …” format. So what’s wrong? Nothing! Well, almost nothing. The user story card is a great STARTING POINT, but it is not sufficient by itself.


Yesterday’s blog post dealt with 
Bear with me on this blog entry. It takes a bit of setup until I get to the main point.
James Shore










