I had an opportunity to attend a training class recently, and someone I admire, dismissed the practice of giving bugs 'zero' points as, flat out 'Wrong'.
I have worked with several teams that embrace velocity as pure mean to manage the backlog (long term planning) and when bugs are identified, they track those bugs as zero point items for a number of reasons.
1) The teams took credit for velocity when a new item was pulled into a Sprint. Period. If a bug is identified, then they didn't do the work correctly, which showed up downstream as a bug, they don't want to take credit for doing the same work twice.
2) By showing a reduced capacity within the sprint (shorter term - release planning) they also use this as a trigger - an opportunity to review and evaluate the TYPE of bug they are working, to determine if there is a larger - refactoring opportunity they need to explore - ultimately in order to recoup capacity which will allow them to work on new features (velocity).
I feel like this meets the criteria of 'measuring the right thing' and hey, if the team buys in and it aids in their ability to improve, how can this be wrong?
My own takeaway - the self organizing team should discuss what works for them - understand the 'why' and inspect/adapt. If it helps the team grow their quality practices, and increase value, I consider it 'right'.
Interested in your thoughts.
Thanks http://Blog.aha.io for the info being shared below. It summarizes the differences and purpose of each nicely!
The biggest difference between product roadmaps and project roadmaps is the overall purpose of each roadmap and how these purposes relate to organizational goals.
A product roadmap is used to communicate theproduct’s strategic path to achieve business goals. Product roadmaps can be used by Product teams at diverse organizations. Software companies and toy companies both produce products. So, Product teams within both companies can use product roadmaps to plan their work. The core similarity between product roadmaps is that they are typically used for products and services that are sold to customers.
On the other hand, a project roadmap is more tactical in nature and used chiefly to communicate the tasks needed to complete the project. “Project” in this case can refer to anything. Project roadmaps can be used to implement a new recruiting service or deploy an email server. The core similarity between project roadmaps is that they are often used to plan internal efforts.
For the full blog on the topic, from Roadmap software experts: