Releases with QA
My release cycle does not include a serial QA pass. What I mean is, I don’t block out 1-2 weeks after a “code freeze” to do QA; I want QA being done while the developer’s mind is still fresh on the code and they haven’t already moved on to something else.
A typical release cycle for me will see a QA lead create a test plan for what’s going out the door, and then work with the developer (or dev lead on the project) to cycle through any found defects. The QA test plan is captured directly from our defect tracking system, which is where I log all requirements for a release.
This helps us in a couple of ways. The first being, no one is sitting around waiting for QA to sign-off on a release. The second is development & QA are directly engaged, and talking about the release so defects can be fixed faster. There’s no cycle time between when QA ends and when fixing any bugs they have found begins.
I’d always recommend looking at what happens when you encounter a code freeze in your release cycle. Are you doing all that you can to ensure the process of getting high-quality product shipped as fast as possible?
