A Case Study in Extreme Quality Assurance (XQA)

Quality Practices that Keep Pace with Extreme Programming (XP)
Member Submitted

Extreme Programming (XP) is all the buzz these days. Business' motivation is to decrease time-to-market, maximizing revenue opportunities. Without quality practices that keep pace, new releases deliver defects just as quickly! Quality testing also often fails to provide complete identification of the launch risk, making enterprises vulnerable upon launch. Often there's no time to test, and automation doesn't seem to shorten time-to-market. Jim explains how he escaped this dilemma at Egreetings.com, a top 50 website.

About the author

TechWell Contributor's picture TechWell Contributor

The opinions and positions expressed within these guest posts are those of the author alone and do not represent those of the TechWell Community Sites. Guest authors represent that they have the right to distribute this content and that such content is not violating the legal rights of others. If you would like to contribute content to a TechWell Community Site, email editors@techwell.com.

About the author

Jim Canter's picture Jim Canter

Jim Canter has 20 years of experience, both as manager and developer. He implemented advanced QA practices for Wells Fargo Bank's CORBA application.

AgileConnection is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, TechWell.com is the place to go for what is happening in software development and delivery.  Join the conversation now!