Save £12 Million every year > Save £3 Million every quarter   
The Big Agile Toolkit: no Dogma, no Bias, no Accreditation, no Exams & no Fees   
 Testing on Agile Projects  Testing on Agile Projects   V Model testing   V Model testing

There are two areas of interest to testing quality: quality definition and quality acceptance. It is the responsibility of the business team to define the level of quality they will accept for the project. It is the responsibility of the business team to determine whether specific outputs have achieved that level of quality and then to accept them or reject them.

The testing team is important in both these activities. However, this is precisely the point at which the tester needs to adjust their influence. We have to remember, the business team are responsible for quality and the testing team act as a professional mentor and catalyst to that process. So, the tester needs to determine how much of their influence and experience to bring to bear. This needs to be done almost on a test by test basis.

Let us look at an example we used elsewhere in the Toolkit. Date processing (the processing of calendar days, months and years) is one of the most intensive areas in computing systems applications development and one of the areas that demands the most testing. Whether your project decides to buy an off-the-shelf component for the processing of calendar dates or whether you use a pre-existing component from another project, you will still need some level of validation involving calendar dates inside your date processing application.

So, you have to decide in liaison with the business team, what level of quality you will accept from your output and thus what level of testing needs to be performed to validate that. The validation of calendar dates is no exception. Professional training in computer application testing, followed by years of intense experience, has taught your testing teams many skills in the testing of components. Most often, this uses the V Model.


 Testing on Agile Projects     Testing on Agile Projects   V Model testing    V Model testing

Glossary:     a  »   b  »   c  »   d  »   e  »   f  »   g  »   h  »   i  »   j  »   k  »   l  »   m  »   n  »   o  »   p  »   q  »   r  »   s  »   t  »   u  »   v  »   w  »   x  »   y  »   z

#personas  »   #artefacts  »   #archetypes  »   #patterns  »   #change  »   #personas  »   #increasingoutput  »   #reducingvariation  »   #improveefficiency  »   #abstraction  »   #predictionandcontrol  »   #management  »   #organisations  »   #socialnetworktheory  »   #failfast  »   #quality  »   #waste  »   #complexity  »   #learning  »   #adapt  »   #inspect  »   #improvement  »   #models  »   #complexadaptivesystems  »   #informationflow  »   #sytemsthinking  »   #butterflyeffect  »   #unpredictability  »   #chaos  »   #emergence  »   #emergentbehaviour  »   #distributedcontrol  »   #continuousimprovement  »   #complexityscience  »   #gametheory  »  
 Agile In 6 Steps    |    Projectivity    |    Instant Agile    |    Risks    |    Auditing Agile Projects 
Big Agile Toolkit Book (Amazon Japan)   |   Big Agile Toolkit Book (Barnes and Noble)
Buy the Big Agile Toolkit Book   |   Buy the Big Agile Toolkit Kindle eBook
Testing quality definition and quality acceptance


The Big Agile Toolkit

 SPADE: Successful Pragmatic Agile Delivery Everytime™ 
Topic: 321  Page: 273/444  Progress: 61.5%
 About    |    Author 
Follow @BigAgileToolkit

This content can be copied to third parties for personal use if you acknowledge the source of the material with website URL ( and Twitter hashtag (#BigAgileToolkit).
In all other cases, no part of bigagiletoolkit or associated text or website may be copied reproduced or redistributed in any form or by any means without prior permission in writing from the author.
Agile Project Governance for Cost Conscious Companies™

All rights reserved.