We keep running into the same issue: How can you know what stories are (were) in play in a given iteration? To show correct numbers on our Iteration cards, for instance.
The Agile Hybrid template shows:
table query: SELECT number, name, ‘story status’ WHERE ‘type’ = ‘story’ and ‘Iteration’ = THIS CARD
This is good if all stories are finished in that same iteration, but not if there is hangover. The Agile Hybrid template supports a process where you would change the card’s iteration if it was not finished. In which case, you would lose the fact that that story had already been planned for the previous iteration.
How do you do it? How do you show cards that are/were in play in an iteration?
Counting story points planned in an iteration
Comments
1 comment
Hi Olivier,
Typically, the way we recommend that you do this if you have work spanning multiple iterations is to have card properties that signify the iteration that different activities were completed in (e.g. analysis completed in iteration, dev completed in iteration, qa completed in iteration). That way you can tailor your reports to show what work may have been scheduled and completed versus that which was started and not finished (e.g. dev completed in iteration = not set).
Let us know if this works for you.
Cheers,
Adam
Please sign in to leave a comment.