Reading Path for Tester
The Tester role is a member of the full Agile team. The team drives the product from a tactical perspective. It is autonomous and self-organizing and is accountable to the Product Owner for committing to and delivering product increments within the duration of the iteration.
The full Agile team works in parallel with all appropriate stakeholders to estimate the size of backlog items, make design and implementation decisions, and transform stories into high quality software assets.
Working with the Team Agility Master, the team tracks its own progress, raises awareness for impediments, and devises options to maintain forward progress. The team is responsible for establishing processes and standards, continuously improving them, and then following those processes and standards.
Quality Assurance focuses more on discovering why defects are occurring than in finding defects. They are guided by two lean principles:
Defining tests up front is an important practice. Help define tests up-front even if you do not write them up-front. It takes no work, increases understanding, and prevents many errors.
Testing involves more than simply discovering bugs. Testing helps discover the causes of errors and eliminating them. Testing helps make explicit the assumptions and requirements that customers have without getting overly technical. Testing ensures code integrity and compatibility with other code modules.
Testing minimizes the risks caused by humans, machines, and environment.
Planning the testing strategy should also begin as early as possible. This requires careful consideration: what will be tested, how much can be automated and what must still be done manually, what the testing environment will include, who will do testing, what they need to know, and what standards they will follow.
The Tester role is responsible for:
To see this role in the context of the work of Lean-Agile, see an example RACI Chart.