Learning Resources
 

Scope

The scope of software testing often includes examination of code as well as execution of that code in various environments and conditions as well as examining the aspects of code: does it do what it is supposed to do and do what it needs to do. In the current culture of software development, a testing organization may be separate from the development team. There are various roles for testing team members. Information derived from software testing may be used to correct the process by which software is developed.

Every software product has a target audience. For example, the audience for video game software is completely different from banking software. Therefore, when an organization develops or otherwise invests in a software product, it can assess whether the software product will be acceptable to its end users, its target audience, its purchasers, and other stakeholders. Software testing is the process of attempting to make this assessment.

 

Plan For Scope Creep

Scope creep is the weed that grows from seeds of unclear planning. The kick-off meeting is the event where the rules for handling scope creep are addressed. Scope creep should be managed through a formal change control document. Change control refers to modifications to the business or technical requirements once sign-off has taken place.

Poor planning does not create change control. The identification of additional requirements is quite common beyond the planning stage. It is nearly impossible to anticipate all the requirements during planning, development and even into testing. In many instances the testing phase is where gaps in requirements become most apparent.

There are situations when change control is imperative for the success of the project, but planning and communicating the process for change will reduce the element of surprise for all project participants.