Strategy 8: Don’t extend deadlines
Perhaps the easiest and hardest tip to follow from this list for any company is simply not to extend deadlines.
However, I hear you saying, “not so easy”.
But this, perhaps singlehandedly, creates the most challenging situation for QA.
There are so many excuses:
- Designs were wrong
- Scoping wasn’t done correctly.
- Developers off sick
- 3rd party integration challenges
- ‘Jim’ is on holiday
And many more. But frequently these delays don’t move the release date, or if they do, not to a sufficient degree.
This creates a squeeze on QA and an intense pressure on QA to fix the ‘short-term’ release problem.
Time and time again, the QA team are put under pressure to ‘deliver’. This leads to:
- Reduced coverage
- Long hours, even weekend working
- Stressed staff
The above all lead to one thing. Less testing.
Even if the window isn’t compressed, things will pop up in the testing window leading to reduced time available.
In fact, it is paradoxical. Because the test team can’t complete everything, they will be concerned about what they might not have done, and typically, for a tester, this is done through increased documentation, in essence, documenting what hasn’t been done.
This leads to sometimes, more time spent on what hasn’t been done, than been spent on doing what needs to be done.
So, this strategy says that it is vitally important to maintain the window that testing scheduled. No doubt there will be delays of one form or another, and you really did want that coverage that the QA proposed that they could deliver.
Ultimately, with a potential loss of £000’s or maybe millions of £’s, it’s just too big a risk to skimp on the testing.
Which leads onto our 9th strategy.