Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
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

Need help with KANBAN throughput on roadmap (SIMPLE EXAMPLE)

What is behind this auto calculation?   (NEED HELP)

  • I have set up a test team under a test program with a throughput of 1.
  • I have two features, each with 6 stories 
  • I have 6 sync sprints per PI
  • I have my 2 features prioritized
  • I have my 12 stories prioritized
    • top 6 stories in feature 1
    • bottom 6 stories in feature 2
  1. I would expect to have 1 story line up under each sprint based upon a throughput of 1?
  2. Target completion dates look good based upon priority for feature 1
  3. Why are target completion dates in lower priority stories in feature 2?

 

Screenshot 2023-10-21 at 9.12.48 AM.png

BELOW ARE FOR FEATURE 1

Screenshot 2023-10-21 at 9.14.44 AM.png

THESE ARE FOR FEATURE 2

Screenshot 2023-10-21 at 9.16.51 AM.png

 

STORY IDTARGET COMPLETION DATE
110/27/23
211/3/23
311/10/23
411/17/23
511/24/23
612/1/23
710/27/23
811/3/23
911/10/23
1011/17/23
1111/24/23
1212/1/23

1 answer

0 votes
Allan Maxwell
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 22, 2023 • edited

Throughput is measured in Team Weeks, not Team Sprints.  If I am understanding your question correctly, it sounds like you are expecting a throughput of one to result in the forecast completion of one Story per Sprint, but it is (correctly) showing two Stories per Sprint.  I'm also assuming your Sprints are the typical two weeks long.

 

EDIT: After further investigation, I see what appears to be a bug.  I created this issue with support: ALIGNSP-21429

Ahh, so I am not crazy?  Yes, I do know that KANBAN measures in weeks, thanks.  Can you give me access to the bug so that I can share with my team?

Allan Maxwell
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 24, 2023

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events