Fired for Saving the Release | Inflectra

Fired for Saving the Release

I knew a QA director, this was a dedicated guy. He worked day and night to make sure they released quality code to their customers. He understood the value of QA on making a company shine. The company had a scheduled release on Monday; it was major and had been promised. This guy worked all weekend to QA the new release and found several stopper defects - Severity 1, the really bad kind!

How many of you have been there? You have to make a major decision that could negatively impact the entire company. In your mind you are weighing, is it really a Sev1? Could we release with notes? What should we do?

Making the Call

Being that it was late on Sunday, Yes he had worked all weekend to do the cycle, he had no choice but to stop a release scheduled for Monday morning.

That was the right call.

There was no one who could rewrite the release notes. There were several Sev1 defects that affected major business processes. Sure, management would not like it, but stopping the release was better than souring the customers with an unworkable release.

Monday came, the QA director went in, and was promptly let go, yes fired for stopping the release. Unexpected, YES. The right thing to do, NO!

What is the real problem?

I would propose that the real problem here is not a stopped release, but a fundamental breakdown in the SDLC.

  1. There was no time to test, the QA director was in on the weekend testing a Monday release.
  2. Testing was too late in the cycle, with found Sev1 defects, there was no time for correction and a retest cycle.
  3. Expectations of quality were not equal. Management was willing to release an unworkable build to meet a deadline, the QA director was not.

The moral of the story, talk to management; let them know the real cost of a bad release. Let them know when testing should be done. Stay informed as to release cycles and by all means, participate in the planning. QA input on a release should not just be at the end, It should be everywhere from inception to release.

This is a real story, the names have been omitted to protect the innocent (and the not so innocent!).

quality assurance release integrity