Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

To track planning & burndown chart

Brindha Ravichandran September 30, 2019

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
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 1, 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?

 

Screenshot_1.jpg

Suggest an answer

Log in or Sign up to answer
TAGS
atlassian, loom, loom for training, loom for teaching, video training, async learning, online education, screen recording, loom tutorials, loom use cases, atlassian learning, team training tools, instructional video, virtual training tools

🛗 Elevate Your Training and Enablement with Loom

Join us June 26, 11am PT for a webinar with Atlassian Champion Robert Hean & Loom’s Brittany Soinski. Hear tips, stories, and get your burning questions answered. Learn how Loom makes training and enablement easier. Don’t miss it!

Register today
AUG Leaders

Atlassian Community Events