How to measure unplanned work post sprint

[Sharon Sahar]

Hi,

We are small startup which started using SCRUM in managing our development. For us,  every task which was not defined during sprint planning is an unplanned task (from production bug to small tasks that arise during daily ).  We create a ticket for it without estimation (not to effect velocity) and assign it on current sprint for post sprint track.

Is there built-in field in JIRA to specify the size of such items and sum them up?

Is there another best practice for unplanned tasks that you do decide to handle during current sprint?

[Walter Buggenhout]

Hi Sharon,

What we do is use story point estimation for stories, but not on any other issue types. So bugs, tasks and spikes are estimated with the Original Estimate field (in hours) whereas we use story point estimations for feature development (stories, as I already said)

[Sharon Sahar]

Thanks.

So how, after sprint ends, you:

1. Aggregate it

2. Translate to how many SP did you invest in all these tasks