Get your own customer support community
 

I accept stories but they aren't moving into the "done" area - why? It is driving our team nuts and we aren't feeling very productive.

Why aren't my stories moved from "current" to "done" after they are accepted?

We are posting stories in the icebox and backlog, but nothing is moving to 'done' once we've accepted it. Very frustrating!

 
sad I’m frustrated
Inappropriate?
1 person has this question

The company marked this question as answered.


  • Inappropriate?
    Margot, the Done panel is for iterations that have been completed, not stories. When your next iteration starts at midnight Monday, Feb 9th, iteration 1 will move to the done panel along with all the completed stories in iteration 1. Any stories still in progress will become part of iteration 2.
     
    happy
    Sprite_screen 2 people say this answers the question
  • Comment_icon
    Thanks Sean. I realize now that we are using this tool for a different use than it is intended for. We run a small production shop where we have many different tasks "stories" coming through and we need to track what gets done. Is there a way to force things to get into the done category or reduce the iteration cycle?
  • Inappropriate?
    Margot, thanks for your quick and thorough response. I think we might both be saying "done" but meaning something different. Let me try to explain what the concepts in Tracker mean as I think about them.

    When stories are completed by being accepted, they turn green to indicate they are done. Those stories were completed in that current iteration, so the story stays in that iteration. That is independent of the iteration or week passing by on the calendar and into the Done pane, which could also be called the Past pane or some other similar chronological name. The Done pane doesn't indicate that the stories there are done, it indicates that the iterations there are over and done with.

    When the iteration ends at the end of the week (midnight Sunday/Monday from the screenshot you've provided), that iteration moves to the Done pane. As you complete stories and as iterations tick by, Tracker calculates a running average of how many points worth of stories were completed in the last 1 to 4 iterations. It then uses that running average to divide up the stories in the current and backlog panes into iterations of the same average total points, thus giving you a predictable time-line if your team does roughly the same amount of work each week. The running average calculation is why stories must stay grouped by iterations. The amount of completed points per iteration is the important number for predicting future velocity.

    As for reducing iterations to less than a week, Tracker only supports iteration lengths of 1-4 weeks. In our experience developing software, the statistical variance of how many points are completed in any given day is too high to yield a meaningful running average, unless the running average is stretched across many weeks worth of days. That said, we are always looking for ways to make the tool flexible enough to support many users without compromising its simplicity. If you still think single day iterations would be more appropriate, I encourage you to help us understand how that makes Tracker work better for you and your workflow.
     
    happy
    Sprite_screen 1 person says this answers the question
User_default_medium