burndown chart and original estimate for work prior to activating sprint?

as we are conducting technical grooming session for user stories planned for next sprint, we require some departments to avail some design documents so we can start to readify our APIs in order for development to be ready by front-end.

now, we discuss each user story and create all needed sub-tasks per story, but the sprint is not active yet, if i ask the team to start logging their working hours, and then activiate the sprint wouldn't this make data in burn-down chart not accurate? should we put original estimates to begin with? or shall we not log any work that takes place before the activation of sprint? don't know the best approach

1 answer

This widget could not be displayed.

Team supposed to work only on issues which are part of its active sprint.

If team during sprint can take new issues , they should be added to active sprint and it will be reflected in your burndowm

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted yesterday in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

76 views 0 1
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you