Attributing Story Points for Partially Complete Rollover Stories

[Paul Volk]

Background:

I'm looking for some advice or suggestions as to the optimal approach for partially complete rollover stories and velocity calculation.

Scenario:

Let's say a developer picks up a 5 point story near the end of Sprint 1. At the end of the sprint, they estimate that they have completed 2 out of the 5 points. However, when the sprint is ended, the story (and all 5 of it's points) will be moved in to Sprint 2. Assuming this is the only story in Sprint 1 the velocity for this developer according to JIRA will be:

• Sprint 1: 0 points
• Sprint 2: 5 points

Issue:

This is causing the following problems

1. The developers velocity is not accurate from sprint to sprint. The reality is they completed 2 points, then 3 points in each respective sprint. But JIRA considers it 0 and 5 respectively.
   1. This also causes inaccurate reporting at the end of the sprint, making it appear that this developer did literally nothing in sprint 1.
2. It's not clear how many points are actually in Sprint 2 at the start of the sprint, forcing capacity calculation to occur manually.  e.g. It appears to be 5 points but really, it's only 3 points.

Solution:

• That's what I'm hoping the community can help with! Hopefully it's an obvious solution that I've simply overlooked :) -- Thanks in advance!

[Cheney Ma [Go2Group]]

From project management respective, it is obviously that resources are not allocated well in your team. You are lack of testing resource and testing task cannot be done by just 1 tester. You need recruit new testing resources and then think about how to improve your testing process and test management tool. 

Hope it helps.

[Warren]

Hi

This is more of a general Scrum question than a Jira one. Is there no way that the developers can help with the testing? We occasionally do that, where the developer is obviously not allowed to test their own work.

You need to discuss internally (at your retrospective to start) how to resolve this, because the situation is only going to get worse if you stick with one tester. If no solution comes out of the retrospective, then management will need to get involved as well.

I hope this helps