Posting of used hours (Story Points)

Benjamin Kapelle

Dear,

I'm struggleing with the new projects and story points. Within our day to day development we're useing weekly sprints. I'm planning sprints with estimated storypoints by our developers. So far so good.

Weekly we've to shift some allready started tasks (ex. 6 h used of 8 h estimated) to the next week. With the Jira standard I'm not able to evaluate the next sprint correctly because I'm not able to post allready used hours.

I've allready searched a lot at the community forum but have not been able to find any satisfactorily solution.

May someone give me a hint?

Thx in advance!

Kind regards

Warren_mz9b4z

Hi @Benjamin Kapelle 

So you get to the end of a 1 week sprint and there are some tickets that are being worked on but not completed. I think you're asking about hours, but you mention story points as well, so I'll try to address both.

Hours

The Remaining Estimate field is now your friend, because in the example you gave above where you've used 6h of an 8h estimate, the Remaining Estimate field should be showing as 2h. But ... what you should also do at sprint planning is to look at each of these tickets that are carrying over, and ask the question whether that value is correct. The remaining value should then be adjusted. By then looking at the total of all the Remaining Estimates, you will be able to better plan the next sprint.

Story Points

Story points are an all or nothing thing - if the ticket isn't complete at the end of the sprint, no story points are "claimed" and they all carry over to the next sprint (even if it is 90% complete). It may skew your planning a bit if you look at velocity and how many story points to take into the sprint, but you can always bring in another ticket towards the end if you have completed everything.

I hope this helps make it all a bit clearer