QA process in agile

QA Process in Agile: Avoiding Silos, Pro Whole-Team Approach

The QA process in agile differs greatly from QA in traditional testing, such as in Waterfall. Agile has changed the way we think of software quality. In fact, I have read rumblings in the blogosphere that Agile has killed QA. I promise you Quality Assurance is alive and well on agile teams. It just looks different than what most of us are used to. I think people who have promoted the “death” of QA in agile are not looking closely enough at what is really happening. Traditionally, testing was the only task people associated with measuring quality.

Quality Software QA Team

Building a Quality Software QA Team: Quality at Every Level

In the last blog, we made the case that everyone on the agile team owns quality and provided some ideas on how team dynamics can help build quality into the product. In today’s post, we will discuss some additional ideas on how your software QA teams can work together and ensure quality is on the forefront of everyone’s mind when building a product.

sheriff badge that reads quality assurance (QA) on it

A Case for Quality… We Don’t Need No Stinkin’ QA

After 20 years in quality assurance, I’m still surprised to hear about companies that don’t have formal QA processes. Even more surprising are the companies that say having a QA function is not necessary. Maybe they are a newer tech company with a tiny, tight-knit development team and the software complexity hasn’t reached a level where defects reach a critical mass or perhaps the company doesn’t support a formal process even though it’s happening in some manner. For me, it is akin to saying breathing is not necessary.