Using Jira backlog and Jira Portfolio, what is the best way to plan the release cycle beyond the pure features & epics, first in our project backlog but also as part of the Portfolio so that we can take those into account when we study the what if scenarios ?
As such those release cycle are moment when we think that some features can be shared for early testers (Alpha), when the scope if fixed (Beta) and when the quality is getting higher (RC) etc .... So maybe we should not represent those as part of the backlog but this means that an epic would span over multiple releases : X-Alpha, X-Beta ......
Has anyone a recommanded best practice ?
Since launching the Jira Software 8.0 and Jira Service Desk 4.0 platform releases in February, many of you have been asking when the next Enterprise release will be so you can take advantage of the m...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs