Skip to main content

Test Planning?

Last post 10:36 am September 8, 2014 by Anke Maerz
3 replies
10:18 am September 4, 2014

Hi all,

I am new to Scrum and have been using to plan a new project.

After quite a bit of research I am still not understanding how testing fits into the lifecycle.

I understand that I could take an extreme programming approach and do the testing as part of the development in an iterative way.

Alternatively, what is the norm? Do you generally release the development from one sprint into a test sprint?
or is testing done at the back end of a sprint? or is it handed off to a testing team as soon as the story is fulfilled?

I am probably missing something fundamental in my knowledge here. Would appreciate any feedback.

Many Thanks

03:29 am September 5, 2014


The result of a Sprint is a potentially shippable increment.
The increment is coded/tested/documented inside the Sprint.
A Sprint is not a mini-waterfall, with testing task at the end "if we have enough time"...

Even the PO doesn't actually ask for a release, the increment has to be "done" and not just "tested"

04:36 am September 5, 2014

Traditionally, testing is done in order to discover errors. In agile and lean ways of working however, errors are recognized to be a form of "waste". The focus of testing therefore shifts away from the discovery of defects and towards their actual prevention. That's why a "test first" approach is favored using TDD and BDD. A level of assurance can be provided by these tests, and it may contribute to the Definition of Done for the Sprint Increment.

10:36 am September 8, 2014

Hi Leonidas,

perhaps another helpful perspective is that the development team does all the work to create a potentially releasable Increment of “Done” product at the end of each Sprint and accountability belongs to the Development Team as a whole.

Therefore, the Development Team has to know what "Done" means and it has to test the created Increment-to-be against this Definition of "Done".
So, in the Definition of "Done" there should be some quality requirements included.

Perhaps also useful: "Individual Development Team members may have specialized skills and areas of focus" (Scrum Guide)
--> It is possible for the Development Team to assign some Development Team members as testers as long as the whole team still feels responsible for ALL tasks, testing included.

Best regards,

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

Please note that the first and last name from your 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. does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, 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 may have their access revoked at any time, without warning. may, but is not obliged to, monitor submissions.