More information at:
ALM Tools | A Scenario Based Approach to Agile Test Planning and Design
We all agree that the quality of releases is only as good as the quality of requirements and the quality of your test design. Whether your requirements are stated in the form of User Stories or other more detailed form, they do not provide the level of details and precision required for developers to write complete and correct code or for testers to write tests that cover enough of the code or enough of the functionality. Even when developers in some agile projects use Test-Driven Development, the problem remains the same and, in some cases, becomes even worst; poorly-written requirements – poorly-written test cases – poorly-written code. When User Stories do not provide enough details to the development and test process, developers and testers will always make assumptions regarding those details without even realizing they are making assumptions. This creates a major gap between what developers have implemented in the code and what tester are planning to test. In my 35 year experience, this gap has caused a major decline in the level of code coverage and requirement coverage. This presentation will provide an overview of a scenario-based development and testing process by which scenarios can be derived from those user stories and/or requirements. Those scenarios will be used as the basis for test-driven development as well as for planning and designing system level tests. The approach has proven to maximize code coverage and User Story coverage. In addition, it has proven to archive a major reduction in defects release to customers.