Gain knowledge and experience in modern requirements engineering techniques that are crucial for the successful execution of an agile software project. Participants will learn to translate business requirements into correctly formulated user stories including acceptance criteria for testing. They will understand the link between stories and testing activities and be able to adapt stories accordingly.
Duration
2 day
Topics
Part1: Agile requirements and high level analysis:
What is the role of the agile analyst?
What is the role of the product owner?
What is a user story?
What is a spike?
What should be done in the high level analysis?
What are techniques to gather business requirements of the customer?
What are techniques to define the target group of your product?
What are techniques to explore product possibilities?
Part 2: Slicing product backlog features in user stories, organizing the product backlog, preparing user stories for a sprint:
A good use story is 'INVEST'. What does this mean?
What are possibilities to split (slice) a user story?
When do you need to write a user story?
What are the benefits of writing stories?
What are the benefits of story mapping?
What are MVP and MMF?
Part 3: Acceptance criteria and agile testing:
What are good acceptance criteria in user stories?
What is agile testing?
How to deal with independent testing in an agile process?
What kind of tests are used in an agile process?
What are the agile testing quadrants?
Where is testing integrated in the agile process?
What tests should be automated and how?
What are exploratory tests and how are the organized?
Participants
8-12 participants
Target audience
Teams, business teams, product owners and product owner team members.
Prerequisites
Classroom with beamer and whiteboards. Participants have followed the course 'Agile Introduction'.
There are no trainings available at the moment. Let us know if you are interested in the training to set a custom date.
