Get into bed with QA(and keep testing agile)

simply brilliant thinkersmaking software brilliantly simple

Hi!

Why am I here today?

The great

DIVIDE

Right?

Nope.

- The product will have problems

- The testing will be late

- Changes will be more expensive

Developers vs Testers

Developers vs Testers

“Thrown over the fence”

“Thrown over the fence”

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

test PLAN

plans CHANGE

plans CHANGE

CODE TEST

FEEDBACK

- INDIVIDUALS

- INTERACTIONS

- COLLABORATION

- INDIVIDUALS

- INTERACTIONS

- COLLABORATION

About those battlelines?

About those battlelines?

INTEGRATION

INTEGRATION

Let’s decide...

● At what points will we all come together?

● How are we going to maintain collaboration?

“Collaborative mindset”

At what points will we all come together going forward?

> Daily standups

At what points will we all come together? > Standups

● What did you do yesterday?● What are you doing today?● Any blockers in your way?

At what points will we all come together?

> Daily standups> Ticket kick offs!

At what points will we all come together? > Ticket kickoffs

1. What is the change?2. Do we have acceptance criteria?3. Is the ticket complete? Aka does the ticket have all the relevant

information for development and testing to begin work?4. Will automated/manual test scripts be completed as a part of the

work?5. Have we made any assumptions?6. Do we need any more detail from the client?7. Are you comfortable enough in your understanding of the area to

start working on the ticket or is a handover required?

At what points will we all come together?

> Daily standups> Ticket kick offs!> Storytime

At what points will we all come together? > Storytime

“Introducing the Three Amigos” - Ryan Thomas Hewitt

At what points will we all come together? > Storytime

Business analysts:

RequirementsAcceptance criteria

Developers:

CodeUnit tests

QA:

ScenariosTest cases

Let’s decide...

● At what points will we all come together?

● How are we going to maintain collaboration?

How are we going to maintain visibility and collaboration through the project life cycle?

> Transparency

How are we going to maintain visibility and collaboration through the project life cycle? > Transparency

How are we going to maintain visibility and collaboration through the project life cycle?

> Transparency> Owning decisions

How are we going to maintain visibility and collaboration through the project life cycle? > Owning decisions

How are we going to maintain visibility and collaboration through the project life cycle?

> Transparency> Owning decisions > Get the most out of retros

How are we going to maintain visibility and collaboration through the project life cycle? > Get the most out of retrospectives

So...

Building aCOLLABORATIVE MINDSET

Time. Passion. Results.

Continuous feedback loop

Continuous feedback loop

Less “my”, more “our”

Less “my”, more “our”

KEEP IT UP!Review. Adapt. Collaborate. Repeat.

Reduced product problems and risks

= Happy team

Reduced product problems and risks

= Happy team

A QA Tester is for life…

not just for the end of a project

WithCONTINUOUS COLLABORATION

ComesCONTINUOUS QUALITY

Cheers! Questions?

www.boxuk.com

@boxuk.com

/sophie-hayden-63722192

@thesophiehayden