We use Stories and Story Points to estimate work and track Velocity in our Sprints.
However, our Backlog also contains a number of stand-alone Tasks and Bugs, which do not warrant their own Stories.
When we plan our Sprints we want to be able to plan for some of these stand-alone Tasks and Bugs to be included in our Estimation process (and later when tracking Velocity).
One idea we had was to create a Miscellaneous Story, which we could use for the Estimation/Story Points, but the exsting Tasks and Bugs can't be assigned to the Story; the best we could do would be to link the Story and the other tickets as related.
That feels like a really clunky solution to a problem that many teams must be facing.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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