Save £12 Million every year > Save £3 Million every quarter   
The Big Agile Toolkit: no Dogma, no Bias, no Accreditation, no Exams & no Fees   
 eXtreme Feedback Devices XFD  eXtreme Feedback Devices XFD   Testing on Agile Projects   Testing on Agile Projects

Lifecycle   »   Agile Testing   »   Testing Introduction

Testing is a huge, massive, enormous, tremendously important part of agile. You can develop all the products you choose and build whatever project you require, but if you do not get the testing correct you have wasted valuable time and money on all the other sections.

Did we say testing is important? We hope so because agile methods fail miserably to do so.

Testing is the area that is transformed in all agile methodologies. This is because, in many ways, the testing process is turned on its head.

In agile processes, you are ready to start the testing process from the beginning of the project rather than waiting for the development team to hand you the baton before testing begins. This transformation requires new approaches and techniques.

There are new skills to learn and adopt as well as some conventional skills that require some delicate repositioning. You do not unlearn your professional testing skills; rather they are judiciously reined back when business demands conflict with your own.

Traditionally, we have a testing manager. The testing manager is responsible for the testing team and for delivering the testing strategy, test plans as well as the tests and the results of the tests. This is the same.

However, the way that we achieve this is totally different.

In traditional projects, the testing team get involved as early as they can in the project to find out what areas of the business are impacted and how this will be tested. This will be input into the testing strategy document. Then there is an intervening lull. The next set of serious work arrives once all the requirements are understood, documented, designed and subdivided into system elements that can be tested and validated. This work can start, in earnest, once the requirements and systems design documentation are stable and agreed.

This is approximately where the systems strategy document is updated and the test plans are developed. The test plans keep in line with the system development using change control procedures and test packs of test data are created. Then there is an intervening lull. Once stable and releasable code is achieved, the system testing can commence using the test data prepared earlier. Lists of system testing defects are produced and passed to the development team. Then there is an intervening lull. Periodically, the teams meet to debate the status of the development and the status of repaired defects. Then there is... get it?


 eXtreme Feedback Devices XFD     eXtreme Feedback Devices XFD   Testing on Agile Projects    Testing on Agile Projects

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 Introduction


The Big Agile Toolkit

 SPADE: Successful Pragmatic Agile Delivery Everytime™ 
Topic: 319  Page: 271/444  Progress: 61.0%
 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.