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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,556,318
Community Members
 
Community Events
184
Community Groups

Reducing Sprint duration in Portfolio

We are switching from 3 week sprints to 2 week sprints. In Portfolio, in the teams section is where you set sprint duration. Do we need to wait until the move to the 2 week sprint actually starts before making the iteration length change in portfolio so we don't mess up the current sprint which is our last sprint that is a 3-week sprint?

1 answer

1 vote
Earl McCutcheon
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Apr 16, 2018

Hey There Edmund,

 

For the Switch between 3 to 2 week sprints should be fine to do before you complete the current sprint however as the teams are concerned you are going to want to adjust the velocity as well, as this is a direct relation to how many story point the team can complete in a given Sprint.  And if you are adjusting the Sprint length you need to decrease the velocity accordingly.

If you have a active sprint set for 3 weeks, and 3 weeks for the teams iteration with 30 Velocity points available and change the teams iteration length to 2 weeks, the active sprint will maintain the 3 week length as this is committed from the Board when starting the sprint and does not adjust, but any non active sprints are Reduced in length and now have extra capacity, with 30 points each which would overbook your team, as this should be reduced by a 3rd making it 20 point for the velocity to reflect the change to length.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events