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

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
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published Thursday in Jira Service Desk

How the Telegram Integration for Jira helps Sergey's team take their support efficiency to the bank

...+ reading Fantasy). The same is true for him at the bank he works for: Efficiency is key when time literally equals money. Read on to learn how Sergey makes most of the time he has by...

351 views 2 4
Read article

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