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

Splitting a task and move it to the next sprint

Hi Community,

I would like to measure the sprint achievement (work done vs work committed) of my team better.

By the end of every sprint, we currently have tasks that are not 100% done and that are needed to be moved to the next sprint.

Can you think of a way to:

  1. Split these tasks so that work done in the current sprint will be included in the current sprint Velocity.
  2. Trace the rest of the work that is moved to the next sprint. We need this data to measure the achievements of the team --> How much of the work committed was actually done per sprint.

Thank you for your help.

Snir

2 answers

No need to split! Count the work when it is done, in whatever sprint it gets to done in.

Velocity is accurate when averaged across 3 or more sprints.

What you are asking for treats the symptom, not the cause. Improve at breaking work down to reliably fit in a sprint and this won’t be an issue.

Hi Kelly,

Thank you for your answer.

Well, we put a lot of efforts breaking tasks to fit them into 1 sprint, but estimations are not always perfect and it's a given fact that not all tasks will be finished by the end of the sprint.

0 votes
Iago Docando Community Leader Aug 05, 2019

You're rigth that 100% accurate estimation might be unreacheable BUT making better and better estimations should be one of your higher concerns going forward so this issue goes away by itself in time (the highest concern being to deliver a good, robust product that meets customer expectations. Of course time to delivery is also a factor to account for when talking about expectations and that's the reason good estimations will be useful not only for internally measuring efficiency but also for the end result).

That being said, if I understand correctly your needs a quick workaround while you work on that point could be using any automation plugin to just duplicate unfinished tasks slightly changing the summary and add those to the new sprint. You could do something like: task 1 (x), then task 1 (xx), task 1 (xxx)... or any other option you like to keep track of how many extra sprints the task was a part of.

Take a look at the market place. I won't endorse an option over another but from a strictly objective point of view, based on popularity, you might want to check first https://docs.automationforjira.com

Hope it helps.

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...

230 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