It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

To track planning & burndown chart

Our sprints are 3 weeks length, starting on a Tuesday and ending on third week Monday.

Sprint Planning->Week1-> Tuesday - Thursday

Sprint Execution->Week1-Friday-Week 3 Monday

If I put Sprint 1 Tuesday as my 1st day of the sprint then I won't have my sprint backlog ready by week1 Thursday so the burndown chart will look like I added additional scope and it won't reflect the true data. How do I handle the start date in Jira so the burn down reflects the true scope?


1 answer

0 votes
Warren Community Leader Oct 01, 2019

Hi @Brindha_Ravichandran 

See below from the Scrum Guide - you shouldn't be spending 3 days planning! for a 3 week sprint, you should only be spending 3 - 6 hours of the first day planning, then your sprint backlog is complete on the first day and your burndown will be fine.

Why are you spending so much time planning?



Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Opsgenie

Authentication Options for Atlassian’s Opsgenie

What’s New as of May 21, 2020 Hi there! We recently made some changes to the way you can leverage Single-sign on and authorization within Opsgenie. Based on customer preference and feedback we intr...

94 views 1 1
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you