Planning Pattern for Agile Testers
Gerrit Beine
gerrit.beine@saxsys.de
What this talk is NOT about
•

Tool discussions

•

Testing methodology

•

Technical aspects of how to create and maintai...
What this talk is about
Observations
Conclusions
Pattern
Observations
A common issue:
User Stories are not testable
efin
D

ases
st C
e Te

ute

Exec

ases
est C
T

Defin

ata
est D
eT

eate

Cr
port
t Re
Tes
Conclusions
•

Testers need to be part of the team

•

It’s not about the testers’ workflow, but about value

•

Quality is key and no...
Pattern
Pattern 1: The Story Workshop
•

Responsible: Product Owner

•

Goal: Improving the Quality of User Stories

•

How to do ...
Pattern 2: Sprint Planning 1.5
•

Responsible: Team

•

Goal: Prepare task slicing after Planning 1

•

How to do it:
•

T...
Pattern 3: Test Driven Planning
•

Responsible: The team’s testers

•

Goal: Hand over the lead of sprint planning to the ...
Pattern 4: The Value-Oriented Scrum Board
•

Responsible: Team

•

Goal: Visualize the Test Driven Planning

•

How to do ...
Pattern 4: The Value-Oriented Scrum Board
test


dev


dev


test


dev


dev


dev


idea

task

task

task

task

task

...
Pattern 5: Honor the test pyramid
•

Responsible: Team

•

Goal: Create valuable test according to Mike Cohn’s test pyrami...
The test pyramid
Source: http://martinfowler.com/bliki/TestPyramid.html
Pattern 6:

Don’t distinguish between dev and test tasks
•

Responsible: Team

•

Goal: Exceed role-based thinking
•

•

F...
Pattern 6:

Don’t distinguish between dev and test tasks
test


dev


dev


test


dev


dev


dev


idea

task

task

tas...
So geht Software.
Planning Patterns for Agile Testers
Planning Patterns for Agile Testers
Planning Patterns for Agile Testers
Planning Patterns for Agile Testers
Upcoming SlideShare
Loading in …5
×

Planning Patterns for Agile Testers

1,380 views

Published on

A number of pattern supporting agile testers in contributing to the sprint planning.

Published in: Education, Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,380
On SlideShare
0
From Embeds
0
Number of Embeds
732
Actions
Shares
0
Downloads
15
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Planning Patterns for Agile Testers

  1. 1. Planning Pattern for Agile Testers Gerrit Beine gerrit.beine@saxsys.de
  2. 2. What this talk is NOT about • Tool discussions • Testing methodology • Technical aspects of how to create and maintain software tests
  3. 3. What this talk is about
  4. 4. Observations
  5. 5. Conclusions
  6. 6. Pattern
  7. 7. Observations
  8. 8. A common issue: User Stories are not testable
  9. 9. efin D ases st C e Te ute
 Exec ases est C T Defin ata est D eT eate
 Cr port t Re Tes
  10. 10. Conclusions
  11. 11. • 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
  12. 12. Pattern
  13. 13. 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.
  14. 14. 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.
  15. 15. 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.
  16. 16. 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.
  17. 17. Pattern 4: The Value-Oriented Scrum Board test
 dev
 dev
 test
 dev
 dev
 dev
 idea task task task task task task test
 dev
 test
 dev
 test
 test
 dev
 idea task task task task test
 dev
 test
 test
 dev
 task task dev
 idea task task task task task test
 dev
 dev
 test
 test
 dev
 idea task task task task task dev
 task
  18. 18. 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.
  19. 19. The test pyramid Source: http://martinfowler.com/bliki/TestPyramid.html
  20. 20. 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.
  21. 21. Pattern 6:
 Don’t distinguish between dev and test tasks test
 dev
 dev
 test
 dev
 dev
 dev
 idea task task task task task task test
 dev
 test
 dev
 test
 test
 dev
 idea task task task task test
 dev
 test
 test
 dev
 task task dev
 idea task task task task task test
 dev
 dev
 test
 test
 dev
 task task idea task task task dev
 task
  22. 22. So geht Software.

×