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

Your Points Tracker
  • 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
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?
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

How to properly split effort of stories that fall into multiple sprints?

In my project it happens often that a user story "falls" out of the sprint where the most development effort has been put in, due to the testing etc not being completely done. So the effort put into a story in sprint x actually shows up in the next sprint (y) due to the testing being completed then. due to this the sprint reports are off, and it confuses people and makes planning a bit messy with effort estimations. also commitment and completed story points become weird to interpret.

Team set up is:

3 Development squads with 4 devs each, who pick up the first tests,
2 dedicated Testers, who deal with more integration, regression and performance testing.

Alternatives ive considered so far:

1. Splitting up user stories, marking one done in the "old" sprint, one in the "new" sprint

2. Manually track the effort spent at the end/start of the sprints, and keep separate reports (Dont like this at all)

3. Dividing user stories in parts of "as a developer" and "as a tester" to ensure the proper division of effort

To note, we do not follow the perscribed idea of scrum teams that have no specific roles, we do have a distinction between dedicated developers and testers.


Happy to hear your thoughts/experiences!



1 answer

0 votes
Sudarshan TS Community Leader Dec 21, 2020

Hello @Bouke Krediet  welcome

I suggest below points:
1. Make your user stories as small as possible so that they are "DONE" in one sprint 
(this is easy to tell but it takes efforts to get the perfect slicing, but it's fun to work it out with a team)
2. Dont do a dividing story for developer and tester. (this is like the head of a human has a one birthday and the legs have another)
A User Story is a user need, and it is an action which the user does,dividing it spoils it and does not provide valuable feedback.
(what if there is a defect/bug in the story (developed item) which is done will you get back and reopen it?
testing is a part of the development activity finish them with the story.

If there are incomplete item at the end of the sprint (overflows to the next sprint), ask your team to evaluate them again, this will help you realize the amount of work pending and sometime this can be combined into one single activity (a task or something) which will enable a closure for the incomplete items soon.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Marketplace Apps & Integrations

New Cloud Apps Roundup - Spring 2021

Atlassian's marketplace partners have had a very productive start to 2021! Since our last roundup, our developer community has added over 160 new cloud apps to the Atlassian Marketplace to help you...

190 views 3 19
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