November 25, 2015
We often think of a release as a simple idea, you have a new version (say 1.0) of a product and you plan on releasing it on a specific date. You might then divide up that release into either iterations or sprints if you're using an agile approach or perhaps phases if using a waterfall one. You then want to be able to report at the project, release and iteration level. Well after much feedback from customers, we found that customers need more than that...
July 10, 2014
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! Read More