I'm not entirely sure I understand what you mean by rating, but this sort of information may vary based on team context and processes. For example an agile team might look at a burn down or burn up chart to see what was committed to in a sprint, and what hasn't gotten done. I generally don't favor in putting blame on one aspect of the process though, teams need to work together to unblock and fix bugs when they arise. That's not always easy if the focus is always new feature, new feature.
Thank you for the reply.
Certainly, I agree with your points and its true. if you think on the real time work environment " Team work is more effective in this to achieve the goal
StickyMinds is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.