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?
Today, we are renaming the Marketplace add-on Portfolio for Jira to Advanced Roadmaps for Jira. In the year since Portfolio for Jira 3.0 was introduced for Server and Data Center customers, custome...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events