When you are working in a large development team it can often be a challenge to get everyone to agree on simple things... When it comes to testing there are a lot of factors that drive whether or not the total team is ready. This is something that the team really needs to agree on, and if they don't, you can find youself with uncommitted stakeholders, an unstable product, and other things that can drive up cost, nevermind drive you mad in the process. With that in mind, consider defining Test Readiness criteria that can be agreed to by all stakeholders. With that defined, everyone can have a more objective view of what is expected during team planning/scheduling sessions. Prior to each scheduled testing event, hold a short meeting and review the criteria with all stakeholder to detemine whether or not you are actually ready. Test Readiness Reviews (TRR) are generally designed to assess the teams readiness based on a variety of information, here are examples of things you may review in this type of meeting:
-
Software requirements changes
-
Design Changes
-
Standards Compliance
-
Security
-
Test Plan(s)
-
Test procedures
-
Unit test procedures and results
-
Problem/Defect/Change reports (pending test/verification)
-
Any changes to associated software products
-
Etc, etc, etc...
Whatever you decide to do, remember to write it down, publish it, and refer to when building Agenda's for test readiness reviews...
Tags: processes