planning patterns for agile testers
DESCRIPTION
A number of pattern supporting agile testers in contributing to the sprint planning.TRANSCRIPT
![Page 2: Planning Patterns for Agile Testers](https://reader034.vdocuments.net/reader034/viewer/2022051411/547bbfd05806b5e03f8b4677/html5/thumbnails/2.jpg)
What this talk is NOT about
• Tool discussions
• Testing methodology
• Technical aspects of how to create and maintain software tests
![Page 3: Planning Patterns for Agile Testers](https://reader034.vdocuments.net/reader034/viewer/2022051411/547bbfd05806b5e03f8b4677/html5/thumbnails/3.jpg)
What this talk is about
![Page 4: Planning Patterns for Agile Testers](https://reader034.vdocuments.net/reader034/viewer/2022051411/547bbfd05806b5e03f8b4677/html5/thumbnails/4.jpg)
Observations
![Page 5: Planning Patterns for Agile Testers](https://reader034.vdocuments.net/reader034/viewer/2022051411/547bbfd05806b5e03f8b4677/html5/thumbnails/5.jpg)
Conclusions
![Page 6: Planning Patterns for Agile Testers](https://reader034.vdocuments.net/reader034/viewer/2022051411/547bbfd05806b5e03f8b4677/html5/thumbnails/6.jpg)
Pattern
![Page 7: Planning Patterns for Agile Testers](https://reader034.vdocuments.net/reader034/viewer/2022051411/547bbfd05806b5e03f8b4677/html5/thumbnails/7.jpg)
Observations
![Page 8: Planning Patterns for Agile Testers](https://reader034.vdocuments.net/reader034/viewer/2022051411/547bbfd05806b5e03f8b4677/html5/thumbnails/8.jpg)
![Page 9: Planning Patterns for Agile Testers](https://reader034.vdocuments.net/reader034/viewer/2022051411/547bbfd05806b5e03f8b4677/html5/thumbnails/9.jpg)
A common issue: User Stories are not testable
![Page 10: Planning Patterns for Agile Testers](https://reader034.vdocuments.net/reader034/viewer/2022051411/547bbfd05806b5e03f8b4677/html5/thumbnails/10.jpg)
![Page 11: Planning Patterns for Agile Testers](https://reader034.vdocuments.net/reader034/viewer/2022051411/547bbfd05806b5e03f8b4677/html5/thumbnails/11.jpg)
Define Test Data
Create
Test Report
Define Test Cases
Execute
Test Cases
![Page 12: Planning Patterns for Agile Testers](https://reader034.vdocuments.net/reader034/viewer/2022051411/547bbfd05806b5e03f8b4677/html5/thumbnails/12.jpg)
Conclusions
![Page 13: Planning Patterns for Agile Testers](https://reader034.vdocuments.net/reader034/viewer/2022051411/547bbfd05806b5e03f8b4677/html5/thumbnails/13.jpg)
• Testers need to be part of the team
• It’s not about the testers’ workflow, but about value
• Quality is key and not negotiable
• Testers have to contribute to acceptance criteria of User Stories
![Page 14: Planning Patterns for Agile Testers](https://reader034.vdocuments.net/reader034/viewer/2022051411/547bbfd05806b5e03f8b4677/html5/thumbnails/14.jpg)
Pattern
![Page 15: Planning Patterns for Agile Testers](https://reader034.vdocuments.net/reader034/viewer/2022051411/547bbfd05806b5e03f8b4677/html5/thumbnails/15.jpg)
Pattern 1: The Story Workshop
• Responsible: Product Owner
• Goal: Improving the Quality of User Stories
• How to do it:
• Invite your testers to a workshop for writing User Stories instead of writing them alone on your desk.
• Ask your testers for possible acceptance criteria of every User Story.
![Page 16: Planning Patterns for Agile Testers](https://reader034.vdocuments.net/reader034/viewer/2022051411/547bbfd05806b5e03f8b4677/html5/thumbnails/16.jpg)
Pattern 2: Sprint Planning 1.5• Responsible: Team
• Goal: Prepare task slicing after Planning 1
• How to do it:
• The team forms pairs that are responsible for selected User Stories.
• Each pair look for the key aspects of each User Story.
• These aspects are the starting point of slicing tasks in Planning 2.
![Page 17: Planning Patterns for Agile Testers](https://reader034.vdocuments.net/reader034/viewer/2022051411/547bbfd05806b5e03f8b4677/html5/thumbnails/17.jpg)
![Page 18: Planning Patterns for Agile Testers](https://reader034.vdocuments.net/reader034/viewer/2022051411/547bbfd05806b5e03f8b4677/html5/thumbnails/18.jpg)
Pattern 3: Test Driven Planning
• Responsible: The team’s testers
• Goal: Hand over the lead of sprint planning to the testers
• How to do it:
• The testers provide test ideas for each User Story to the team.
• The developers slice their tasks with the goal to make the resulting test cases green as fast as possible.
![Page 19: Planning Patterns for Agile Testers](https://reader034.vdocuments.net/reader034/viewer/2022051411/547bbfd05806b5e03f8b4677/html5/thumbnails/19.jpg)
Pattern 4: The Value-Oriented Scrum Board
• Responsible: Team
• Goal: Visualize the Test Driven Planning
• How to do to:
• Stick the testers ideas in a column for every User Story.
• Stick the developers’ and testers’ tasks beside these test ideas.
![Page 20: Planning Patterns for Agile Testers](https://reader034.vdocuments.net/reader034/viewer/2022051411/547bbfd05806b5e03f8b4677/html5/thumbnails/20.jpg)
Pattern 4: The Value-Oriented Scrum Board
testidea
testtask
testtask
testtask
testtask
testtask
testtask
testtask
testtask
testidea
testidea
testidea
dev task
dev task
dev task
dev task
dev task
dev task
dev task
dev task
dev task
dev task
dev task
dev task
dev task
dev task
dev task
![Page 21: Planning Patterns for Agile Testers](https://reader034.vdocuments.net/reader034/viewer/2022051411/547bbfd05806b5e03f8b4677/html5/thumbnails/21.jpg)
Pattern 5: Honor the test pyramid
• Responsible: Team
• Goal: Create valuable test according to Mike Cohn’s test pyramid
• How to do it:
• Focus on test ideas during planning and simple ways to satisfy tests.
• Discuss a lot about simplicity and be willing to throw away complex solutions.
![Page 22: Planning Patterns for Agile Testers](https://reader034.vdocuments.net/reader034/viewer/2022051411/547bbfd05806b5e03f8b4677/html5/thumbnails/22.jpg)
The test pyramidSource: http://martinfowler.com/bliki/TestPyramid.html
![Page 23: Planning Patterns for Agile Testers](https://reader034.vdocuments.net/reader034/viewer/2022051411/547bbfd05806b5e03f8b4677/html5/thumbnails/23.jpg)
Pattern 6:Don’t distinguish between dev and test tasks
• Responsible: Team
• Goal: Exceed role-based thinking
• Focus on business value and technical excellence.
• How to do it:
• Just stop showing up any kind of difference on your task board.
![Page 24: Planning Patterns for Agile Testers](https://reader034.vdocuments.net/reader034/viewer/2022051411/547bbfd05806b5e03f8b4677/html5/thumbnails/24.jpg)
Pattern 6:Don’t distinguish between dev and test tasks
testidea
testtask
testtask
testtask
testtask
testtask
testtask
testtask
testtask
testidea
testidea
testidea
dev task
dev task
dev task
dev task
dev task
dev task
dev task
dev task
dev task
dev task
dev task
dev task
dev task
dev task
dev task
![Page 25: Planning Patterns for Agile Testers](https://reader034.vdocuments.net/reader034/viewer/2022051411/547bbfd05806b5e03f8b4677/html5/thumbnails/25.jpg)
![Page 26: Planning Patterns for Agile Testers](https://reader034.vdocuments.net/reader034/viewer/2022051411/547bbfd05806b5e03f8b4677/html5/thumbnails/26.jpg)
So geht Software.