Incrimental Agile QA

An Article on how QA. Incremental QA is highly desirable in Scrum. Scrum does not distinguish between development and QA as in waterfall model. It expects that the product feature you are working on is designed, developed and tested by the end of a sprint – One sprint does it all.

This article touches on the background that all Development and QA should happen within the one sprint. I can relate to some of this article. I have found that by using scrum we in QA are involved in close communication with developers on how products are progressing through the Daily Scrum and being part of the team alongside the developers rather than being a separate entity as we were before. We communicate better with the developers, find out which areas of functionality are available for test and any areas require special attention.

By working as part of the team we are also able to start our automated tests earlier. We previously used QAWizard for this but we have progressed to selenium which is more efficient and better suits our needs.

 I would say that a lot of the good points that are highlighted within the article are evident in the way that we work as a team. See how much this relates to your team.

Incrimental Agile QA