Story points by developers

[Thiago Cunha]

Hey Guys! 

I'd like to know,  the easiest way to know how many story points each developers delivered by sprint. 

Considering also, carryovers from other sprints and additional scope. 

No problem with the acquisition of add-ons! 

[Bill Sheboy]

Hi @Thiago Cunha 

Would you please describe the problem you are trying to solve by doing this measurement?  What would you do differently if you had that information right now?

You appear to be describing a team using the Scrum Framework, and such teams usually collaborate and share the work to deliver value.  Measuring the individuals may create unintended consequences, such as discouraging people from collaborating to meet the sprint goal, focusing only on themselves.

Kind regards,
Bill

[Thiago Cunha]

Top Down performance demand. I'll try to change in the future, but right now that my need. 

[Bill Sheboy]

Thanks for that information.  Some follow-ups:

1. How often do assignees change during work?
2. How will you see when two, or more, people collaborate and only one is assigned?
3. How often are issues in multiple sprints?

If your answers to the above are closer to: #1 never, #2 n/a, and #3 never, you could filter for your project issues and export for analysis in a spreadsheet, and consider adjustments for edge cases, such as rolling up data for sprint carry-overs.

[Nic Brough -Adaptavist-]

Story points are a bad measure of performance, especially for individuals.