24
Stop Maintaining Multiple Test Environments Joel Tosi @joelTosi [email protected]

Stop Maintaining Multiple Test Environments

Embed Size (px)

Citation preview

Page 1: Stop Maintaining Multiple Test Environments

Stop Maintaining Multiple Test Environments

Joel Tosi @joelTosi

[email protected]

Page 2: Stop Maintaining Multiple Test Environments

My Perspective

Design

Deliver

Learn

Page 3: Stop Maintaining Multiple Test Environments

Context is Important

Page 4: Stop Maintaining Multiple Test Environments
Page 5: Stop Maintaining Multiple Test Environments
Page 6: Stop Maintaining Multiple Test Environments

We Stopped Learning About Products

We Started Learning Maintenance

What are you learning about?

Page 7: Stop Maintaining Multiple Test Environments

Simplify before automating

Testable over testing

grow deeper Product Context

own your World

What Can We Do About It?

Page 8: Stop Maintaining Multiple Test Environments

Simplify before automating

Page 9: Stop Maintaining Multiple Test Environments

What we say

Page 10: Stop Maintaining Multiple Test Environments

Reality

Page 11: Stop Maintaining Multiple Test Environments

Every step between your product and your customer separates

learning. Drive outcomes (product), reduce output

(environments)

Page 12: Stop Maintaining Multiple Test Environments

Testable over testing

Page 13: Stop Maintaining Multiple Test Environments
Page 14: Stop Maintaining Multiple Test Environments

Testability is a deep debt

Demoability

Test Isolation

Doubt

Page 15: Stop Maintaining Multiple Test Environments

We need to ask better questions – not just the acceptance criteria but how

will we test this?

Page 16: Stop Maintaining Multiple Test Environments

grow deeper

Product Context

Page 17: Stop Maintaining Multiple Test Environments

Building Common Language

All Product Ideas

Product Choices

Collaborative Chartering

Pragmatic Personas

Story Maps

User Interviews

Market Research

Slices

Page 18: Stop Maintaining Multiple Test Environments

Make Intentional Decisions

To Avoid

Accidental Discoveries & Misunderstanding

Page 19: Stop Maintaining Multiple Test Environments

own your World

Page 20: Stop Maintaining Multiple Test Environments
Page 21: Stop Maintaining Multiple Test Environments

Be clear on values / direction

Let people doing the work solve the problems

Provide them data

Page 22: Stop Maintaining Multiple Test Environments

Don't Promote (and maintain) Through Environments

Pull Through Examples, Tests, and Learning

Page 23: Stop Maintaining Multiple Test Environments

There Isn't One Solution To Rule Them All

Design

Deliver

Learn

Experiment & LearnAre previous assumptions still valid?

What is stopping you?

Page 24: Stop Maintaining Multiple Test Environments

[email protected] @joeltosi www.devjam.com

Questions?

Coaching and Developing Agility

http://devjam.com/coach/

_________________________________________

_________________________________________

© 2015 DevJam - All rights reserved.