Agile endeavors seek to deliver quality working software sooner than traditional approaches. Knowing how much effort to place in capturing requirements in an agile world can be challenging. Too much, and you risk paralyzing progress; Too little, and you risk building the wrong thing.
This two-day instructor-led course guides participants in optimizing agile requirements and tests with user stories and acceptance criteria. Through hands-on labs and discussion, the course demonstrates how acceptance tests are so much more than tests. They replace traditional requirements, they seed developer tests (unit tests), and they are another valuable productivity metric.
Anyone interested in optimizing requirements and QA on an agile team.
Participants will learn to
- Write requirements suitable for an agile team
- Describe how agile requirements are different
- Describe the role of QA on an agile team
- Write good acceptance tests
- Effectively work with different formats of acceptance tests
- Elicit acceptance criteria from customers
- Understand how acceptance criteria aid agile planning and estimation
- Apply best practices around creating and maintaing acceptance criteria
- Seed developer tests in the context of Test-Driven Development
- Automate acceptance tests
Customers also viewed