Agile is often mis-sold to senior management as a way of achieving quicker time-to-market, when the objective is really more accurate delivery to market. Teams are releasing more often, but it ultimately takes longer to get the complete functionality to market. As the team focuses on validating the new functionality implemented, a lack of understanding of the indirect impact of code changes causes detection of defects late in the release cycle – when they are complicated, time-consuming and costly fix.
What is needed is a way to understand the impact of the changes and identify where to focus testing efforts (unit testing, automated functional testing, and manual testing) to validate that existing features are not negatively impacted by the most recent changes.
• Apply testing practices to speed up quality during iterations, by focusing on changes in the code base between builds
• Prioritize creation of new tests on the changed lines of code not covered by existing regressions
• Leverage intelligent analytics, including Change-Based Testing, Modified Code Coverage, and Risky Code Change, to prioritize your agile testing activities