Day 1 test engagement? Are you kidding me?

11
Day 1 Test Engagement? Are you kidding me?

Transcript of Day 1 test engagement? Are you kidding me?

Page 1: Day 1 test engagement? Are you kidding me?

Day 1 Test Engagement? Are you kidding me?

Page 2: Day 1 test engagement? Are you kidding me?

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

Page 3: Day 1 test engagement? Are you kidding me?

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

Page 4: Day 1 test engagement? Are you kidding me?

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

Page 5: Day 1 test engagement? Are you kidding me?

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

Page 6: Day 1 test engagement? Are you kidding me?

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

Page 7: Day 1 test engagement? Are you kidding me?

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

Page 8: Day 1 test engagement? Are you kidding me?

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

Page 9: Day 1 test engagement? Are you kidding me?

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

Page 10: Day 1 test engagement? Are you kidding me?

Driving the future of content

– How can team agreements help? (e.g.: identifiers)

Learning

Page 11: Day 1 test engagement? Are you kidding me?

Get in touch!

- Vishal Prasad

www.VishalPrasad.in