Principles Behind Agile Testing Manifesto

Behind the Agile Testing Manifesto are the following principles which some agile practitioners, unfortunately, fail to understand or implement. We urge you to go through each principle and digest them thoroughly if you intend to embrace Agile Testing. On the right column, the original principles have been re-written specifically for software testers.

                                   

We follow these principles:

                       

                                   

What it means for Software Testers:

                       

                                   

Our highest priority is to satisfy the customer through the early and continuous delivery of valuable software.

                       

                                   

Our highest priority is to satisfy the customer through the early and continuous delivery of high-qualitysoftware.

                       

                                   

Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.

                       

                                   

Welcome changing requirements, even late in testing. Agile processes harness change for the customer’s competitive advantage.

                       

                                   

Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.

                       

                                   

Deliver high-quality software frequently,   from a couple of weeks to a couple of months, with a preference to the shorter timescale.

                       

                                   

Business people and developers must work together daily throughout the project.

                       

                                   

Business people, developers, and testers must work together daily throughout the project.

                       

                                   

Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.

                       

                                   

Build test projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.

                       

                                   

The most efficient and effective method of conveying information to and within a development team is a face-to-face conversation.

                       

                                   

The most efficient and effective method of conveying information to and within a test team is a face-to-face conversation.

                       

                                   

Working software is the primary measure of progress.

                       

                                   

Working high-quality software is the primary measure of progress.

                       

                                   

Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

                       

                                   

Agile processes promote sustainable development and testing. The sponsors, developers, testers, and users should be able to maintain a constant pace indefinitely.

                       

                                   

Continuous attention to technical excellence and good design enhances agility.

                       

                                   

Continuous attention to technical excellence and good test design enhances agility.

                       

                                   

Simplicity–the art of maximizing the amount of work not done–is essential.

                       

                                   

Simplicity–the art of maximizing the amount of work not done–is essential.

                       

                                   

The best architectures, requirements, and designs emerge from                            self-organizing teams.

                       

                                   

The best architectures, requirements, and designs emerge from self-organizing teams.

                       

                                   

At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

                       

                                   

At regular intervals, the test team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.