Any business that builds software has to rely on quality to keep their clients satisfied. Many people believe that code quality suffers when software development companies use agile methodologies, but this does not have to be the case. Creating a full life-cycle practice for code quality could be the key to solving this issue.
Instead of relying on your QA team you need to make sure that your entire project team is aware and looking out for code quality. The failure to do so will lead to late detection of unknowns, unmet user requirements, options readiness, and gaps.
One article on this topic, interviewed Karthik Ravindran of Microsoft and he had this to say about testing.
In testing, techniques such as continuous acceptance testing to make sure software meets criteria as it is being developed; continuous validation from other stakeholders; test automation during continuous integration to ensure build quality; and exploratory testing for finding defects can eliminate the post-development logjam and create a culture of building quality into the application throughout its life cycle, Ravindran said. Read more:
You have to have an end-to-end testing practice in place so that you do not have logjams at the end of the project. This practice will also save you a lot of time and keep you from having to redo work. For more on this read our blog about The Role of Quality Assurance.