Spira v5.1 is now out! This blog gives
you some insight into the release and discusses our accelerated release
strategy going forward.
Today we look at whether test-driven development (TDD) a good technique for specifying how a user story should operate, and whether it means that user story is fully tested (hint: these do not have the same answer!) (Read More)
This article discusses some of the earliest attempts at crowdsourced QA and extreme agile development that predate the agile manifesto and where they went wrong. (Read More)
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)
I have often been presented with the argument that QA is not cost effective. It seems like a throwback to years past, but it happens all too often. With the advent of Agile, and other rapid development cycle methodologies, the mindset of "we will fix it once it is reported" has made a comeback. I know the MVP process, and it does include a specification, and can therefore be tested. (Read More)
The testing function in Agile projects should not be confused with the Quality Assurance function. If we are not careful, the Agile philosophy will conflate the two, with potentially disastrous results. (Read More)