There are cases when a story or 2 hangsover in an iteration. In next iteration I just change the iteration on the story. How do i record that this is a hangover from past iteration. it also gives a wrong impression on Iteration scoreboard. Check the image below. one column is for Planned size and the other one is the velocity. Looks like ours is perfect team, we plan for certain points and finish all of it.
But in reality, we have had hangover a couple of times. I want that to reflect and also want to go back and see which stories got hung over in which iteration.
Comments
1 comment
Hi Roohi
At first I thought this was a very seasonal question - never considered using mingle to track the outcome of too much festivities over the holidays
But seriously it depends on what properties you have for tracking card planning and when they get updated. For instance I think 'Added to scope' is a typical property to derive story TTL, and if this is set when you allocate a story an iteration then you can use this to see which iteration it was planned for, but more likely this is used to record when it entered the overall backlog ( with status of 'New', for instance), so you may need another property, say 'Added to iteration' which is set when you add the story to an iteration backlog (could use a transition to help you set a number of other properties too).
Assuming that you have a proprrty, Iteration, that captures which iteration the story is currently in, then you could compare Total planning estimates for 'Iteration' and 'Added to iteration' properties to see how your planned velocity compares to your actual velocity.
Merry Christmas
Ian
Please sign in to leave a comment.