Save £12 Million every year > Save £3 Million every quarter   
The Big Agile Toolkit: no Dogma, no Bias, no Accreditation, no Exams & no Fees   
 Test strategy document  Test strategy document   Testing Approach   Testing Approach

The test strategy document will include a list of people involved and their responsibilities. There will be a test manager, to whom all testing issues of whatever type are escalated. There will be testers. They will be guiding the business team on process and running the tests. There will be business team members involved in the tests as well as someone responsible for reporting the results of tests and they should all be identified too.

The test strategy document should list the various assessment environments to be used. It will also list who owns that environment, who will source and load the data for that environment as well as who will set up that environment for use and decommission the same environment when it is no longer needed. This way, you are making the testing responsibilities clear.

You will define the location where you will perform the tests. In the Toolkit, we have a process for converting development output into testable output. This is the Test Handover stage and we suggest you define the process and the responsibilities involved here too. You will have distinct environments for development and test. For the test handover stage, you need acceptance criteria for your development output. You will describe who will be responsible for defining the criteria and who will be responsible for accepting whether the development output has achieved those criteria.

The criteria may be as simple as: all development source code has been unit tested. We feel such criteria are possibly a little light but your project will determine what is fit for purpose and what can be achievable, bearing in mind the cost. Your criteria may involve intense and exacting naming standards for source code, database tables and the rest. Again, we repeat, your project will determine what is fit for purpose and achievable, bearing in mind cost.

Just because we have always had specific handover acceptance criteria for our development code and always used it in the past, does not mean it is fit for purpose now. It just means that our organisation was prepared to spend money on that, in the past. If you need it, then document your fit for purpose development code handover acceptance criteria in the test strategy document and define the responsibilities and move on. Now, let us have a look at the types of testing we might want to perform.

Buffer



 Test strategy document     Test strategy document   Testing Approach    Testing Approach



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 responsibilities






   


The Big Agile Toolkit

 SPADE: Successful Pragmatic Agile Delivery Everytime™ 
   
Topic: 325  Page: 277/444  Progress: 62.4%
 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 (http://www.bigagiletoolkit.com/) 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.