Impacts to Sprint
In our daily use of Kunagi we encountered the Problem, that impacts without a pre-estimated stories can not be brought into the Sprint as tasks. As explanation image a real whiteboard where we use yellow sticky notes for our planned sprint tasks and for impact/interrupt tasks (not planned in sprintplanning) we use red sticky notes. So you can determine at the end of a sprint how many impacts/interrupts where generated and disturbed the sprint to reaching it's goal. In our daily work on a global operating company this happens more than you may believe.
Statement from Kunagi Team
Please see sto238.
We will likely avoid introducing "interrupt" Stories, becuase Sprints in Scrums are not supposed to be interrupted. While it's clear that reality may be different, it is perfectly fair that it feels like cheating in both real life and Kunagi.
Status
Issue is closed.
Comments
Fri, Mar 1, 2013, 09:33 by Witek (SM,T)
I like the idea, we will discuss how this could be integrated into Kunagi.
We are currently working on a feature to pull Issues into a sprint, so they are visible on the burndown. Everything pulled into a sprint after the first burn (stories or issues), could be marked somehow to visualize not planned changes to the sprint.