You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I very much liked the concept of sorting the Backlog into three categories (New Features, Bugs, Technical Debt) and ensuring that each of the three categories are addressed in each sprint.
The concept is exactly what our team needs to sort our growing backlog.
However, I am struggling to understand how the "Fake Sprints" can map into Portfolio... Or if even using "Fake Sprints" is a usable option when using Portfolio. It seems that if a ticket is assigned to one of the fake sprints, then Portfolio won't assign it to an actual sprint.
Perhaps, what I really need to do is to assign the tickets in my "New Features" Backlog, for example to a "New Feature" theme in Portfolio.
How do others handle categorizing the backlog when using Portfolio?