In this article, Davide Noaro discusses the software testing phase of Scrum projects with a final Waterfall interaction. As Scrum’s adoption is often incremental inside an organization, both approaches can coexist for a while. Compared to a full Scrum approach is that, in this situation you are obliged to rerun the tests for the whole functionality to qualify the product before going to production. In the article, he presents how software testing has been integrated into his organization’s process and then analyze the objections that are sometimes raised on the software testing choice made, mainly that running tests for every user story is inefficient because they have to rerun them for the whole functionality during the Waterfall at end phase.

Related Content:

• Transitioning from Traditional to Agile Testing
• Using Behavior-Driven Development (BDD) for Backlog Refinement in Scrum
• Making the Sprint Backlog Ready for Testing