Planned vs Actual sprint figure history view

[Pierre Goussard]

How can we see an overview of completed sprints still displaying the Planned figure compared to the actual figures? After we have finished/missed a sprint we move the incomplete(open) tasks either to the next sprint or the backlog depending on the new priority. Moving the stories affects our historical view of the sprint which prevents us to see the planned vs actual details of each sprint. Is there anyway we can take a snaphot or something for a completed sprint before moving the open items out?

Thank you

Pierre

[MatthewC · Accepted solution]

Hi Pierre,

It sounds like if this is a regular occurrence then there is a problem with the work estimation and how much the team agrees to take on in the sprint. The long term solution would be to fix this but you probably need a solution now rather than later.

We often run into a similar problem because our team is split between project work and BAU support which means you can never guarantee the amount of time a developer can spend on a project. If, at the end of the sprint, you move the unfinished work to the next sprint (using greenhopper) , you are fundamentally changing the data set on which the graphs are built as it removed the previous sprint allocation.

If however, you edit the issue and just add a new version to the FixVersion field, the issue becomes part of two sprints & will contribute it's effort to the second sprint. Just make sure that you get the start dates correct for the 2nd sprint, otherwise the work spent on the issue in Sprint 1 will creep in.

It's not clean but it works. The only other solution is to take screenshots of the work & save it in Confluence before moving the open issues across to the new sprint.

[Renjith Pillai]

When you release a version (Sprint) from the Greenhopper Version view, the existing snapshot of the charts are indeed captured by Greenhopper for future reference.

Read http://confluence.atlassian.com/display/GH/Using+the+Released+Board

[Pierre Goussard]

Thank you very much for your responses. I will try this for our next release. We hit the mark more often than not :) just the first time we use jira, i knew it sound have a feature to preserve planned details.

Thanx,

Pierre