Skip to main content

Sprint planning and Testing for Tasks and User Stories.

Last post 06:33 am September 26, 2017 by Julian Bayer
6 replies
12:30 pm September 22, 2017

Many of my clients are experiencing trouble completing sprint due to the task/story are completed on last day of sprint.

 

How to complete testing and get it done from developers within the Sprint duration? The idea is to complete the sprint with ready to deploy User Stories.


02:49 pm September 22, 2017

Have you done any root-cause analysis around the reasons why some story development is not being completed until the end of the sprint?   How large are the stories?


03:49 pm September 22, 2017

Are the team sufficiently focused on completing one story at a time, so that testing occurs early and throughout the Sprint?


07:18 am September 23, 2017

If the team is only designing the work for the first days ; then coding the next days ; then trying to test the last days, they are just working in small waterfall cycle with phases, but not as a whole rugby scrum team carrying the ball forward for a try.


05:52 pm September 23, 2017

Are they discussed in Retrospective meetings about any impediments causing delay in testing to last day.


08:37 am September 25, 2017

Thank you Timothy, Olivier and Ian for always replying my post.

The team is struggling only for those User Stories which are completed on last two days of sprint completion, as testing remain pending for those User Stories.

If we keep buffer for testing coverage, the other developers are not utilized for that last days.

Thank you Timothy for suggesting RCA.

Thank you Ian for suggesting focused work.

Thank you Olivier. We will find out if we are doing small waterfall cycle.

 

 

 

 

 

 

 


06:33 am September 26, 2017

If we keep buffer for testing coverage, the other developers are not utilized for that last days.

How so? If the testing is not done yet, the team hasn't finished the product increment. So all the tea embers must collaborate to finish it.


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.