Back to Forum

Incompleted Tasks in Story

Last post 01:46 pm January 5, 2018 by Ian Mitchell
2 replies
NANDAKISHORE BEHARA VENKATA
08:32 pm January 4, 2018

Hi All - Wanted to check how to approach on the below issue which we have in the team. Story consists two tasks (e.g. Dev & SIT) and Dev got completed and SIT wasn't completed. PO decided to move next sprint due to business priority. How to account the effort for the Dev task which got completed?

  1. Move the entire story to next sprint without any change in story points & tasks estimations?
  2. Close the story with what ever task completed with re-estimation and create another story for remaining tasks to complete with new story points? to me its like story for each task

 

Nils Hyoma
10:17 pm January 4, 2018

Hi Nandakishore,

why is the effort so important to you?

but here my answers. In my opinion, you maybe want to use the story points for calculation of the velocity of that team. In that case only "reward" and use sprint backlog items which hit the Definition of Done and are potentially shippable has advantages. Using the story points of the finished tasks for calculating the teams velocity could lead to false assumptions of the team performance.

In the Sprint Planning the team could discuss the whole story again, but would only use the actual work as base for an re-estimation. More important than the story points is that the team selects how much work they can do in the sprint, story points can help of course. 

Don't forget to ask why nobody was performing a SIT in the Retrospective. Maybe the team has an idea to solve the problem. Eventually the User Story was to big, to less dev team members are testing, or are in your team different roles like developer and tester? 

Be careful with using the story points and velocity as base as a report. If your team gets better, the estimation of the same user story could get less in another estimation round.

Nils

 

Ian Mitchell
01:46 pm January 5, 2018

Why not just re-estimate the work which is now thought to remain on the Product Backlog? The size of the Product Backlog ought to be a fair and accurate reflection of this.

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.