How will you deal with the delay delivery of code?
How will you deal with the delay delivery of code? When there is any delay from the development team, what will be your approach
Retrospective meetings prevent such things from happening in the future. As of that point of time, the only option will be to do risk based testing.
My ASQ Certified Software Quality Engineer (CSQE) Certification training batch is starting on July 11 2016. Details and 6 VERIFIABLE RECOMMENDATIONS for my training at www.facebook.com/PickTechnologies
This is where having a official high level test strategy charter really helps. What I have my teams do is create a feature/components matrix.
Originally Posted by mozhi
For each feature / component box, have 2 lists, 1 list of "must test", and 1 prioritized list of "would be nice to test".
That way as delivery window slips, you can communicate to management what testing you expect to cut, or if you have it down to stuff you cannot compromise on, you can start pushing back with how much more time you need with definitive proof to support your claims.
Last edited by dlai; 03-16-2016 at 05:25 PM.
I've written a fairly lengthy blog post on this subject, you can find it here:
Triple Constraint and Test Re-Planning and Optimisation | Intrepid Testing Blog
I completely agree with the statement.
Originally Posted by dlai