We want to get a feel or a number really for the distractions we have on completing our Sprint goal.
One of the things that distracts us are incidents and other unplanned but high prority things that cannot be delayed and that will have impact on the Sprint goal.
Incidents are added to the Sprint Backlog, but I dont see an easy way to differentiate between Planned work and incidents.
Is there an eay way in Jira do to this?
Best regardsm
René
I am not sure if putting incidents into sprints it is a good idea. I am working on support for many years and for me Kanban is the only solution. If there is other work being done outside support and planned (like maintenance) it might be handled by sprints but should already include team velocity in estimation - how many hours might be missing for handling incidents etc.
You could simply add the, to the active sprint. If the team is doing unplanned work during the sprint then it should be captured in the sprint and discussed during postmortem. If you can begin to trend this work then you can plan it into the sprint. For example you can create a single “unplanned activity” issue and say estimate it to 10h. Each unplanned activity can record time against that task.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.