Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Best way to run a sprint planning session

  • How long is a sprint planning session on average? My session is usually 3-4 hours on average. Is that about right.

Does the product owner  and scrum master decide on the user stories and backlog before the sprint planning meeting? 

1 comment

Interested to follow this. My take is that the Product Owner uses data analysis and local knowledge and works with the scrum master to prioritise tasks from the backlog. All the while trying to keep a future focus about what new resources our country market will look for that isn't already on the backlog. User requests also need to be taken into consideration and I am fortunate enough to have an experienced and knowledgable team who offer insight into the amount of work different types of resources will take. I have been working without a scrum master lately, so have 'drafted' a scrum prior to the planning meeting and then worked with the team to refine this.  I am still learning and find the biggest challenge at the moment to be ensuring the number of resources at each stage for the development team is correct... too much at any early stages causes a bottle neck where the work backs up and doesnt get through to the rest of the team.... but not enough leaves the team out of tasks.... tricky business this! 


Log in or Sign up to comment
AUG Leaders

Atlassian Community Events