What is Sprint planning in Agile project management?

Sprint Planning meeting is one of the key activities in Agile project management. (see Release and Iteration Planning). Generally, Agile teams need to deliver a working product at the end of  each Sprint. However some organizations also use a Sprint Zero. Sprint Zero is used exclusively for planning the first Sprint and no work product is delivered at the end of Sprint Zero. Usage of Sprint Zero is decided by the team and complexity of the project. [Read more…]

What is the difference between Severity and Priority?

There are two key things in defects of the software testing. They are:

1)     Severity

2)     Priority

What is the difference between Severity and Priority?

[Read more…]

When do defects in software testing arise?

Because of the following reasons the software defects arise:

– The person using the software application or product may not have enough knowledge of the product.

– Maybe the software is used in the wrong way which leads to the defects or failures.

– The developers may have coded incorrectly and there can be defects present in the design.

– Incorrect setup of the testing environments.

To know when defects in software testing arise, let us take a small example with a diagram as given below. [Read more…]

From where do defects and failures in software testing arise?

Defects and failures basically arise from:

  • Errors in the specification, design and implementation of the software and system
  • Errors in use of the system
  • Environmental conditions
  • Intentional damage
  • Potential consequences of earlier errors

Errors in the specification and design of the software:

Specification is basically a written document which describes the functional and non – functional aspects of the software by using prose and pictures. For testing specifications there is no need of having code. Without having code we can test the specifications. About 55% of all the bugs present in the product are because of the mistakes present in the specification. Hence testing the specifications can lots of time and the cost in future or in later stages of the product.

Errors in use of the system:

Errors in use of the system or product or application may arise because of the following reasons:

–          Inadequate knowledge of the product or the software to the tester. The tester may not be aware of the functionalities of the product and hence while testing the product there might be some defects or failures.

–          Lack of the understanding of the functionalities by the developer. It may also happen that the developers may not have understood the functionalities of the product or application properly. Based on their understanding the feature they will develop may not match with the specifications. Hence this may result into the defect or failure.

Environmental conditions:

Because of the wrong setup of the testing environment testers may report the defects or failures. As per the recent surveys it has been observed that about 40% of the tester’s time is consumed because of the environment issues and this has a great impact on quality and productivity. Hence proper test environments are required for quality and on time delivery of the product to the customers.

Intentional damage:

The defects and failures reported by the testers while testing the product or the application may arise because of the intentional damage.

Potential consequences of earlier errors:

Errors found in the earlier stages of the development reduce our cost of production. Hence it’s very important to find the error at the earlier stage. This could be done by reviewing the specification documents or by walkthrough. The downward flow of the defect will increase the cost of production.