The online community for software testing & quality assurance professionals
Calendar   Today's Topics

Lost Password?


Quality Engineering >> Quality Methodologies

Pages: 1

Reged: 12/25/06
Posts: 5
Loc: Bangalore
Testing in SCRUM process
      #365653 - 03/13/07 06:44 AM

Can anyone guide me about how the testing is carried out in SCRUM?


Post Extras: Print Post   Remind Me!   Notify Moderator  

Reged: 09/14/01
Posts: 4281
Loc: Boston, MA
Re: Testing in SCRUM process [Re: mantest]
      #365697 - 03/13/07 08:19 AM

can you narrow your question down more? Which part are you confused about or would like information on?
I'm currently work on projects using scrum.

Corey Goldberg

Post Extras: Print Post   Remind Me!   Notify Moderator  
Advanced Member

Reged: 09/16/04
Posts: 491
Loc: Riga, Latvia
Re: Testing in SCRUM process [Re: Corey_G]
      #365885 - 03/14/07 02:23 AM

maybe this one could help you organize your ideas and ask the specific question(s) you want to learn
Theoretically SCRUM is management methodology not engineering. You could do testing however you want, but manage testing tasks, planning, etc. according to SCRUM.

Post Extras: Print Post   Remind Me!   Notify Moderator  
Junior Member

Reged: 04/20/00
Posts: 8
Loc: Toronto
Re: Testing in SCRUM process [Re: Ainars]
      #368648 - 03/27/07 07:52 AM

I have been involved in Agile and Scrum for over a year now.
It's much more different then testing in "waterfall".

Some pointers for you:

-you are a part of the team (collective responsibility)
-your work is much more transparent then in "waterfall"
-your role as the tester is to do whatever is necessary to get the job done by the end of the iteration (finish coding and testing the vertical slice your team is building)
-you could run out of time to finish your regression tests by the 2nd, 3rd or 4th Construction phase. Ask the team for help (testers are coders and vice versa).

This is my individual experience, your Scrum setup could be different.

Post Extras: Print Post   Remind Me!   Notify Moderator  

Reged: 04/12/07
Posts: 6
Re: Testing in SCRUM process [Re: ivanm]
      #678218 - 07/12/11 03:33 AM

See detail on SCRUM at

Post Extras: Print Post   Remind Me!   Notify Moderator  

Reged: 02/08/11
Posts: 24
Re: Testing in SCRUM process [Re: Jaswal]
      #678410 - 07/12/11 09:51 PM

The so called testers in intial phases carry out the REquirenment gathering along with Biz analyst and then challenge some requirements if he senses ridiiculousness therein. By the time first sprint cycle gets over he has to even complete the test execution. Normally the test estimation is expected to have 40% time frame requirement as of the dev, but in agile we get it lesser, also in case defects going unfixed in the sprint one needs to be taken higher priority task in next phase and validation in subsequent would be done. But in all cases , agile works well only in maintenance projects, wherein experienced product specialists are available.


Post Extras: Print Post   Remind Me!   Notify Moderator  

Reged: 07/13/11
Posts: 11
Re: Testing in SCRUM process [Re: ViplavAnand]
      #678523 - 07/13/11 04:35 AM

SCRUM does not define anything about testing. Hence this is something that you will need to figure out depending on many criteria related to the project.

However, my experience showed that in SCRUM projects:
- testers should be more involved in unit-testing,
- test-driven approach is often a good thing,
- automation should be used as much as possible
- and exploratory testing is used for manual testing

my 2 cents,

Post Extras: Print Post   Remind Me!   Notify Moderator  

Reged: 01/06/09
Posts: 37
Re: Testing in SCRUM process [Re: Maike]
      #685043 - 09/13/11 04:37 AM

Here are my 2 cents...

1. Good quality starts with the requirements - QA should involve as a active participant while reviewing the requirement/user story

2. Write test cases before the coding starts - The team should take the user story and AC as a starting point.

3. testing - Work closely with the development team and find the issues as early as possible. QA need not have to file the issues found during the testing but communicate with the developers on the issues.

4. Manual/Exploratory QA - Manual QA should be happening in the sprint before anything is marked done

5. Incremental regression testing - You need to do incremental regression testing along the way, probably every sprint. This takes careful collaboration with the developers to figure out what to release to the test lab every sprint so that it can be regression tested


Post Extras: Print Post   Remind Me!   Notify Moderator  
Junior Member

Reged: 05/02/06
Posts: 1041
Loc: CA, USA
Re: Testing in SCRUM process [Re: skumars25]
      #685143 - 09/13/11 04:14 PM

I never read the book on the official definition of the SCRUM process. But I've been in 2 different companies who call their process SCRUM. 1 has Engineering Scrum teams, and one has a dev team, and a QA team. As your can see from other posts above, having an Engineering SCRUM team is ideal in that acceptance criteria will include fully tested, bug free, before a story is accepted as done.

When there are separate dev team and QA scrum teams, the dev team usually only have to pass unit and integration level tests, and the QA team will work through a back log of regression stories. The regression stories will often be a testing plan/charter, an acceptance criteria (testcases run, areas touched, coverage level).

I'm not a big fan of the latter organization. It tends to become a blame game the month before a major release.

David Lai
Sr. QA / Test Lead
LinkedIn profile

Edited by dlai (09/13/11 04:17 PM)

Post Extras: Print Post   Remind Me!   Notify Moderator  

Reged: 02/25/12
Posts: 6
Re: Testing in SCRUM process [Re: dlai]
      #699561 - 02/25/12 06:39 PM

True Scrum projects tend to be very development focused and focused on testing new features. The key thing to manage in a scrum process is the continuous collection and planning of the regression tests.

Developers will continue to develop features and the testers need to create the test plans for the new features and make sure that they are stored in a Test Management system for a later regression cycle.

I've seen many scrum/agile based project neglect regression testing, which is extremely dangerous, before shipping all of the tests that where done through all the scrum sprints have to be re-executed.

Post Extras: Print Post   Remind Me!   Notify Moderator  

Reged: 01/16/07
Posts: 6
Re: Testing in SCRUM process [Re: QAScaler]
      #711226 - 07/02/12 05:22 AM

2 principles apply:
1) Design a definition of Done that includes testing activities
2) User stories are not complete if the Definition of Done is not reached

What's in the Definition of done is agreed by the full scrum team.

Post Extras: Print Post   Remind Me!   Notify Moderator  

Reged: 07/06/12
Posts: 12
Re: Testing in SCRUM process [Re: Augusto]
      #711615 - 07/06/12 09:31 AM

Process Software Testing in agile development method (in portuguese):

Post Extras: Print Post   Remind Me!   Notify Moderator  

Reged: 09/07/12
Posts: 3
Re: Testing in SCRUM process [Re: mantest]
      #716063 - 09/07/12 02:28 AM

We do it (simplified) like this:

Week 11-14 (sprint 10):

* Coders solve bugs from previous sprint(s) and develop new functionality for current sprint.

* Testers test sprint 9 and report bugs continually. If something important comes up it is mentioned during daily meeting.

* Requirements are produced and validated for sprint 11 so team can plan for next sprint.

That means:
After each sprint, application is built to test servers and not updated. That is what is mainly being tested.

There is also a daily build so testers can go there and check what is current.

Bug reports must include what sprint (version) of the app it was discovered in.

Each sprint includes a rough estimate of bug-solving by devs. That way the team can estimate team velocity and determine how much new functionality the team can take on.

Test team reports test progress at the sprint demo.

If bugs keep building up, it can be good to run a sprint dedicated to bug fixing without much new functionality. Too many bugs and no time to fix them kills team morale.

Post Extras: Print Post   Remind Me!   Notify Moderator  
Pages: 1

Extra information
0 registered and 6 anonymous users are browsing this forum.

Moderator:  blueinatl, AJ, michaeljf, swt88 

Print Topic

Forum Permissions
      You cannot start new topics
      You cannot reply to topics
      HTML is disabled
      UBBCode is enabled

Topic views: 25436

Rate this topic

Jump to

Contact Us | Privacy statement SQAForums

Powered by UBB.threads™ 6.5.5