Reality Driven Testing in Agile Projects

Many agile teams rework previously deployed stories, even after plenty of in-sprint testing. Well groomed, refined, stories framed with typical, alternate and error scenarios, gracefully described in well formed gherkin, continue to encounter all sorts of bugs. Software engineering consultant, Rob Sabourin, often sees rework in over 20% of deployed stories. In this presentation Rob shows how agile teams can drive rework down dramatically, often achieving near Zero rework after a story is DONE. Rob teaches teams to identify and implement relevant testing activities above and beyond those derived from well formed requirements. Rob shows agile team members how to identify tests based on reality. He seeks out relevant testing ideas based on what is really being changed in the technological solution. He finds ideas based on what the user really does in the workplace and he discovers rich test ideas based on the real target environments. Delegates learn many excellent strategies to identify, prioritize, and implement reality driven testing. They will ferret out important bugs that really matter eliminating the need for downstream rework.