How a Quality Engineer can contribute in a Sizing session
Sizing session is a recurring event for agile development teams, where PO and Engineers work to have a better comprehension about stories, refine the acceptance criteria and define the story time. One of the goals from a backlog grooming session is to ensure the next few sprints worth of user stories in the product
This session starts with a discussion about functionalities that feature must include from user perspective. Software Testing process starts here, because team should start to Plan user features validation, including test scenarios and the data need to test. This is the phase of Test Coverage definition. Follow more details about how Quality Engineer can contribute for this session:
- Why: Understand New feature and collect information about flow and how to Test;
- Who: Business Customer, PO, Developer and Quality Engineer/SDET/Tester;
- When: Refinement/Grooming and Planning. “Three Amigos” join a meeting and from each perspective they understand and ask the customer about the new feature;
- How: Meeting for a better User features understanding:
- Ask about examples and scenarios;
- Check happy path and alternate paths
- Suggest improvements when possible
- Ask How to validate the new feature
- Ask about data need to validate new feature
- Request swagger, endpoints, payloads when available
- Analise if you need to update your test framework to cover these new functionalities
- Result of this Phase
- Stories and Acceptance Criteria
- Test Plan and Design (Test Strategy definition)
- Test Scenarios
- Updates on automation test framework
As you can see, the Sizing session is an important event in agile teams. This is the first contact the Quality Engineer has with new stories, so enjoy this session to ask all question possibles and start to plan the best coverage possible for your automated tests.
