We are developing a product that requires 3 teams to work together: my team works on web-development, team B works on embedded system and team C bridges us together (to put in a simple way). There is a product owner who is responsible for the overall product (business, technical) and a project manager who manages the project progress. We do monthly releases.
So I will say it is a typical cross functional product development teams. One thing that bothers me from the project management point of view is that the project manager will send out the stats about everyone's "productivity" at the end of each release, e.g. the work hours (according to his spreadsheet), the bug fix rates (how many bugs you fixed), how many bugs you introduced when implementing a new feature, etc.
For me, as the manager of team A I don't see the usefulness of that. I understand he is doing his job and in this case maybe he wants to keep the stakeholders, each one of us, informed the project progress. Maybe he wants to reminds everyone what we did well or poorly in this release. I know scrum has a burn down chart and in theory we should try to make our burn down chat look like a straight line. But from my own experience that rarely happens. But scrum is another topic I don't want to get involved in this question.
So is sending out stats like this typical? What are the pros and cons of it?
---- update ---
As I already said "I don't see the usefulness of that". But since he will keep doing that I need to see is there any "silver lining" of it. That is one of main reasons I asked this question. We did have some monthly releases that had mores bugs than other months. So would the stats reminds everyone we need to do better next time (although I highly doubt it)?