Velocity Chart - Issues Completed Outside Sprint - Included in Commitment but not Completed

[Paddy Corry]

Hi guys, 

I have been able to reproduce this a couple of times, just wanted to ask if it is a known issue. Here is the scenario:

• Sprint 1 completes on Tuesday at 5.30. 
• Sprint Planning starts at 9.30 on Wednesday for Sprint 2.
• At 2pm, before Sprint 2 is started in Jira, an issue is closed.
  • It has an estimate of 8 Story Points on it.
  • It was part of the Sprint 1 commitment, but not completed before the end of that Sprint.
  • When Sprint 1 completed, the issue went into the backlog for Sprint 2.
• At 5pm, Sprint 2 is started, with a start time of 5pm, and a commitment of 100 SP.
• The Burndown shows the starting commitment of 100 SP.
• The Sprint Report for Sprint 2 shows that an issue was completed outside the Sprint, with 8 SP. This was completed in the 'dead zone' while sprint boards were not available..
• Sprint 2 rolls on, and the team eventually hits their target, closing all 100 story points.
• However, when Sprint 2 completes, the Velocity Report looks a little off:
  • Commitment is 108 SP
    • This was increased by 8 SP for the issue closed outside the sprint. 
  • Completed is 100 SP
    • This was not increased by the same 8 SP

(?) Is this a known issue with the Velocity Report?

(?) Or should I set the start time of the Sprint to be 9.30 am?

All input welcome!

Many thanks,

Paddy

[Mhasan]

Hello Paddy

This is normal in velocity report. You have added 108 SP to the sprint and completed 100 SP in the sprint duration. In order to prevent this problem, you had two options:

• As you said you could set the start of the sprint to an earlier time.
• Remove the task form sprint and then mark it as done and then continue the sprint.

But as the original velocity of the team is 100 SP, I would recommend the second option.

Mhasan