Slides for a workshop and demonstration to check how testing teams can be engaged from the very first day of software development.

1. Day 1 Test Engagement? Are you kidding me?

2. Driving the future
of content
Apparatus
– 3 participants per group (BA, DEV, QA)
– Post-its, Pen or Pencil
– 1 dice per group
– Scissors (shared resource)
– 1 rupee coin

3. Driving the future
of content
– Follow the rules of the iterations
– The dice must be shaken at least 5 times before
you throw it 
– Adhere to the timelines
– Don’t cheat and Have fun!
General Guidelines

4. Driving the future
of content
– BAs to roll the dice 10 times
– Each time create a post-it and add circles equal
to the number on the dice
– Each circle represents a story point
Create a Backlog

5. Driving the future
of content
– Each team runs a 3 day iteration (13 minutes)
– 1 min of sprint planning (commit stories)
– 2 min of day 1 execution
– 0.5 min of daily stand-up
– 2 min of day 2 execution
– 0.5 min of daily stand-up
– 2 min of day 3 execution
– 5 min of review and retrospective
Execution

6. Driving the future
of content
– Create pipes that can pass through the circle
drawn by the BA
– During the iteration:
– The DEV makes the pipes
– The QA checks for acceptance
– For every six rolled on the dice, BA adds a story
– Roll dice again for the story points (draw)
Objective

7. Driving the future
of content
– DEV can work on only one story at a time
– QA can accept only completed stories
– QA can create holes on the story card for testing
– In case of defect, send story back to DEV
Iteration 1 Rules

8. Driving the future
of content
– DEV can work on only one story at a time
– QA can accept partially completed stories
– QA can create holes on the story card for testing
– In case of defect, send story back to DEV
Iteration 2 Rules

9. Driving the future
of content
– BA to refine the story for coin sized circles
– QA can create a task post it to replicate acceptance
– QA can accept partially completed stories
– QA can create holes on the story card for testing
– In case of defect, send story back to DEV
Iteration 3 Rules

10. Driving the future
of content
– How can team agreements help? (e.g.: identifiers)
Learning

11. Get in touch!
- Vishal Prasad
www.VishalPrasad.in