Back to Forum

Sprint Stories waiting for Testing Approval in Sprint

Last post 09:40 pm July 13, 2016 by Ian Mitchell
3 replies
Swapnil Dhoke
01:16 pm July 11, 2016

Hi All,

I passed my PSM 1 exam last month, our organisation is using 'ServiceNow' for Scrum Development, I am in a situation where as per the tool I need to get a testing pass approval for my stories from the customer (stakeholder).

I really can't close my stories without testing approval, but, this is affecting my Sprint and BurnDown Chart as it still shows stories as open, but, my developers indicate that they don't have any work left on these stories.

Please help how should I handle this situation!
Thanks in advance.

Timothy Baffa
09:44 pm July 11, 2016

What does your Definition of Done contain?

What can your team members do to help each story meet your Definition of Done?

Alan Larimer
08:38 pm July 13, 2016

Does the definition of "Done" include customer testing? If so, I would question, "Why?" Testing (does it meet the understood requirement) should be a Scrum Team concern; Sprint Review is the the time for the customer to express feedback on if that was truly the desired functionality.

Ian Mitchell
09:40 pm July 13, 2016

The Development Team should have all of the skills and resources needed to satisfy the Definition of Done. If there is a dependency on a third party then Scrum is being improperly implemented.

Why does this dependency on external testing exist in your team's case? What value does it add? Is it compensating for a deficiency in the team's quality assurance practices? If so, how can the deficiency be addressed and the dependency removed?

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.