Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Planned vs Actual sprint figure history view

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

2 answers

1 accepted

0 votes
Answer accepted


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.


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

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

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Agile

Join us LIVE: Atlassian & Experts Talk Research & Insights @ Scale

Hello all! What have you learned from your customers lately? Our live-streamed series continues by exploring CX, UX, and the power of research & insights at scale with Leisa Reichelt, Head of R...

251 views 3 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you