a chase of - nordic testing days › files › files › 09-alfa-maaret_pyhajarvi-a... · @maaretp...

@maaretp http://maaretp.com

A Chase of Incremental Improvement

by Maaret Pyhäjärvi


A Recent Past

No Written Bug Reports Release Daily without Test Automation One Computer for a Group


Catalyst Conscience

Cheerleader Critical thinker


An Unusual Hiring Experience

http://visible-quality.blogspot.fi/2016/09/how-i-was-interviewed-as-tester.html


“Just Do What I Say…”


We all like a dramatic story. But things don’t happen out of the blue, and it’s so interesting to get a true picture of why change happens, rather than this phony all of a sudden picture. –Linda Hirshman on Freakonomics, In Praise of Incrementalism


10 Years has passed….


I.  Capability to Release II.  Self-Organized Teamwork III.  Agile Requirements


Capability to Release A Journey Towards Continuous Deployment


[Team Capability] Turn 4 day release to

4 hour release We believe that ability to make our client releases with shorter duration will result in saved time in making multiple releases. We will know we have

succeeded when team does not feel need to escalate release-making as a threat to features.


This fundamentally changes the testing I do. It enables me to test each change, isolate it and see its impacts all the way through production. It supports small, human-sized discussions on changes together in the teams and gives us an ultimate definition of done - production value over task completion. It makes developers care about the feedback I give, and enables the feedback to be more timely. And it makes way for the necessary amount of thinking and manual work to happen in both coding and testing so that what we deliver is top-notch without exerting too much effort into it. http://visible-quality.blogspot.fi/2017/05/incremental-steps-to-continuous-releases.html


Self-Organized Teamwork

From Co-Creation to Collaboration


"All the brilliant people working on the same thing, at the same time, in

the same space, on the same computer." -- Woody Zuill


(Exploratory) Tester

(Application) Programmer

Test Automator / Programmer


Breaking Established Communication

Patterns


6 Months without Logging a Single Bug

Report


I don't need to be assigned responsibility

to be responsible


Agile Requirements Making Sense into the

All-Knowing Product Owner


We aren’t here to make a great product or a great company, but rather to make our customers awesome at whatever they do with our products or services. –Kathy Sierra, Badass: Making Users Awesome


I.  Capability to Release II.  Self-Organized Teamwork III.  Agile Requirements


Every day when I come to work, my goal is to be better after the

day.


Overhead Compound

interest Timing

145 000 100 000

839 2124

8333 8402

100 100

10x https://www.youtube.com/watch?v=1Bv1-6EX70s


Pretend it is possible and ask for it. Don’t let

yourself tell you it can’t be done.


Maaret Pyhäjärvi Email: [email protected] Twitter: @maaretp Web: maaretp.com Blog: visible-quality.blogspot.fi (please connect with me through Twitter or LinkedIn)

a chase of - nordic testing days › files › files › 09-alfa-maaret_pyhajarvi-a... · @maaretp...

Documents