Testbash Australia: Next Level Teamwork - Pairing and Mobbing

•

3 likes•365 views

This document discusses techniques for effective teamwork when developing software, including pairing and mob programming. It emphasizes that creating software is as much of a learning problem as a coding problem, and that experts are those who learn the fastest. Pairing involves two developers sharing a workstation and collaborating on a task, with traditional pairing having one developer primarily typing while strong-style pairing rotates that role. Mob programming takes this further by having the entire team work as one unit with a shared display and single codebase, with roles like driver and navigator. Both pairing and mobbing aim to accelerate learning through collaboration, sharing of knowledge, and exposure to different perspectives.

Software

@maaretp http://maaretp.com
Next Level Teamwork
Pairing and Mobbing
by Maaret Pyhäjärvi

@maaretp http://maaretp.com
SEEKING RELICANTH
SMART INDIVIDUAL
VICTIM TO A PROCESS

@maaretp http://maaretp.com
Creating software is
not a typing problem
but a learning problem

@maaretp http://maaretp.com
From SOLO…
… to PAIR …
… to MOB.

@maaretp http://maaretp.com
On being the best…
vs.
LinearViewpoint
I know
everything
you do!
You have
nothing left
to teach
me
Reality
I know more
than you do!
There is still so
much more I
can learn from
you

@maaretp http://maaretp.com
Experts are not the
ones who know the
most but ones who
learn the fastest

@maaretp http://maaretp.com
Pairing
Traditional vs. Strong-Style

@maaretp http://maaretp.com
Individual work

@maaretp http://maaretp.com
Traditional Pairing
Traditional Navigation
I have an idea – GIVE ME the
keyboard!

@maaretp http://maaretp.com
Strong-Style Pairing
Strong-Style Navigation
I have an idea –YOU take the
keyboard!

@maaretp http://maaretp.com
Different Skillsets –
Unequal at a Task

@maaretp http://maaretp.com
My Pairing Pitfalls
Hijacking the session
Giving up to impatience
Working with them

@maaretp http://maaretp.com
1st week with a
15-yo intern

@maaretp http://maaretp.com
“I never knew
testing was this
much fun”

@maaretp http://maaretp.com
“It only took 40 seconds
for your second test
automation pull request
to get approved!”

@maaretp http://maaretp.com
Mobbing
Mob Testing
Mob Programming

@maaretp http://maaretp.com
Mobbing Basics
Understanding what it is about better

@maaretp http://maaretp.com
Driver
(no thinking)

@maaretp http://maaretp.com
(Designated)
Navigator

@maaretp http://maaretp.com
Retrospectives

@maaretp http://maaretp.com
If everyone is contributing or
learning it’s the right size

@maaretp http://maaretp.com
Two ideas, bias to action and
do both!

@maaretp http://maaretp.com
https://leanpub.com/MobProgrammingGuidebook

@maaretp http://maaretp.com
Mindshare
Similar Enough to Get Along,
Diverse Enough for Better Impact

@maaretp http://maaretp.com
(Exploratory)
Tester
(Application)
Programmer
Test Automator
/ Programmer

@maaretp http://maaretp.com
We raise our collective
competence, allowing
individuals to use
specialized skills

@maaretp http://maaretp.com
When you work on
Hard problem è Solution
Easy problem è Innovation

@maaretp http://maaretp.com
The 5-Year Rule

@maaretp http://maaretp.com
Building
Your Wizard

@maaretp http://maaretp.com
Learning in a Mob
Moving towards Serendipituous Learning

@maaretp http://maaretp.com
Exploratory Testing
Test Automation
Unit Testing
Application Programming
Performance Testing
Security Testing

@maaretp http://maaretp.com
Accidental Learning
by being Intentional
about Learning

@maaretp http://maaretp.com
Cognitive
Dissonance

@maaretp http://maaretp.com
People change their
minds when their
experience conflicts
with their beliefs

@maaretp http://maaretp.com
Correcting
Mistakes without
Egos in Play

@maaretp http://maaretp.com
Knowing what is
relevant

@maaretp http://maaretp.com
Slow allows for
thoughtful
thinking

@maaretp http://maaretp.com
Stealth
Exploration

@maaretp http://maaretp.com
I had great ideas even if
I did not know how to
turn them to code –
removing the distance
is worth the struggle.

@maaretp http://maaretp.com
Maaret Pyhäjärvi
Email: maaret@iki.fi
Twitter: @maaretp
Web: maaretp.com
Blog: visible-quality.blogspot.fi
(please connect with me through
Twitter or LinkedIn)

Many different roles contribute to building software: product owners, business specialists, testers. Yet knowledge of programming keeps these roles at a distance. In this talk, we will discuss a new powerful way of removing this distance for the benefit of our teams: mob programming. We’ll walk through my lessons: the pains of joining a mob as a non-programmer, and the gains of what a tester brings into a mob. This talk serves as an inspiration to learning together, immersed in the experience of creating software as we’re learning. Diversity of thoughts and skillsets improved everybody and created a better product.

Programming Assignments in Tester Interviews

Maaret Pyhäjärvi

While we draw parallels to Queen's Gambit the series on Netflix and Software Testing, this talk is not about how substance abuse is like testing. Instead, the movie guides us to to its name and figuring out what is this gambit. With exploratory testing, we have the opening moves, the midpart and the end game. The start can be anything but it builds our platform for the end game. And while exploratory testing, automation is part of that way of staying in tune with learning to win in the end game.

Geekle QA: Automationist's Gambit

Maaret Pyhäjärvi

HUSTEF '21 Keynote: Hands Off Exploratory Testing - Managing at Scale

Maaret Pyhäjärvi

Breakpoint 2021: Contemporary exploratorytesting

Maaret Pyhäjärvi

Selenium Summit 21: Contemporary Exploratory Testing

Maaret Pyhäjärvi

MoT Sarajevo: How to get better at Exploratory testing

Maaret Pyhäjärvi

Agile2016: Exploratory Testing an API

Maaret Pyhäjärvi

AppiumLite Keynote: Many Hats to Make a Tester

Maaret Pyhäjärvi

Hands off Exploratory Testing - Managing Testing at Scale

Maaret Pyhäjärvi

Mimmit Koodaa - Testiautomaatio on testauksen dokumentointia

Maaret Pyhäjärvi

Agile India: Working without Product Owner

Maaret Pyhäjärvi

AGRS2019: Breaking illusions with Testing

Maaret Pyhäjärvi

Tampere Testing Days: Exploratory Testing an API

Maaret Pyhäjärvi

Selenium Conference India: Intersection of Automation and Exploratory Testing

Maaret Pyhäjärvi

Testing United - Social Software Testing Approaches

Maaret Pyhäjärvi

What's hot

AgileTD: Learning through osmosis

Maaret Pyhäjärvi

AgileTD: Mob testing Training Day

Maaret Pyhäjärvi

AgileTD Scandia: Mob Testing

Maaret Pyhäjärvi

SLASSCOM: Breaking illusions with Testing

Maaret Pyhäjärvi

Talentum: Testiautomaation tekemisen taito

Maaret Pyhäjärvi

ATAGTR Keynote: I have a rock in my shoe - Navigating Improvement

Maaret Pyhäjärvi

Testbash Philly: A Mob Testing Experience

Maaret Pyhäjärvi

EuroSTAR '21 Keynote: Automationist's Gambit

Maaret Pyhäjärvi

Geekle QA: Automationist's Gambit

Maaret Pyhäjärvi

HUSTEF '21 Keynote: Hands Off Exploratory Testing - Managing at Scale

Maaret Pyhäjärvi

Breakpoint 2021: Contemporary exploratorytesting

Maaret Pyhäjärvi

Selenium Summit 21: Contemporary Exploratory Testing

Maaret Pyhäjärvi

MoT Sarajevo: How to get better at Exploratory testing

Maaret Pyhäjärvi

Agile2016: Exploratory Testing an API

Maaret Pyhäjärvi

AppiumLite Keynote: Many Hats to Make a Tester

Maaret Pyhäjärvi

Hands off Exploratory Testing - Managing Testing at Scale

Maaret Pyhäjärvi

Mimmit Koodaa - Testiautomaatio on testauksen dokumentointia

Maaret Pyhäjärvi

Agile India: Working without Product Owner

Maaret Pyhäjärvi

AGRS2019: Breaking illusions with Testing

Maaret Pyhäjärvi

Tampere Testing Days: Exploratory Testing an API

Maaret Pyhäjärvi

What's hot (20)

AgileTD: Learning through osmosis

AgileTD: Mob testing Training Day

AgileTD Scandia: Mob Testing

SLASSCOM: Breaking illusions with Testing

Talentum: Testiautomaation tekemisen taito

ATAGTR Keynote: I have a rock in my shoe - Navigating Improvement

Testbash Philly: A Mob Testing Experience

EuroSTAR '21 Keynote: Automationist's Gambit

Geekle QA: Automationist's Gambit

HUSTEF '21 Keynote: Hands Off Exploratory Testing - Managing at Scale

Breakpoint 2021: Contemporary exploratorytesting

Selenium Summit 21: Contemporary Exploratory Testing

MoT Sarajevo: How to get better at Exploratory testing

Agile2016: Exploratory Testing an API

AppiumLite Keynote: Many Hats to Make a Tester

Hands off Exploratory Testing - Managing Testing at Scale

Mimmit Koodaa - Testiautomaatio on testauksen dokumentointia

Agile India: Working without Product Owner

AGRS2019: Breaking illusions with Testing

Tampere Testing Days: Exploratory Testing an API

Similar to Testbash Australia: Next Level Teamwork - Pairing and Mobbing

Selenium Conference India: Intersection of Automation and Exploratory Testing

Maaret Pyhäjärvi

Testing United - Social Software Testing Approaches

Maaret Pyhäjärvi

SEETest: Making Teams Awesome

Maaret Pyhäjärvi

STARWest: Make Your Team Awesome, Yes You Can!

Maaret Pyhäjärvi

StarEast 2018: Making Teams Awesome - Yes You Can!

Maaret Pyhäjärvi

Mob Testing: Better Products Through Diversity

TEST Huddle

Many different roles contribute to building software: product owners, business specialists, testers. Yet knowledge of programming keeps these roles at a distance. In this webinar, Maaret will discuss a new powerful way of removing this distance for the benefit of our teams: mob programming. She’ll walk through her lessons: the pains of joining a mob as a non-programmer, and the gains of what a tester brings into a mob. This webinar serves as an inspiration to learning together, immersed in the experience of creating software as we’re learning. Diversity of thoughts and skill sets improved everybody and created a better product. view webinar recording - https://testhuddle.com/mob-testing-better-products-through-diversity/

ATAGTR '20 Keynote: Building status

Maaret Pyhäjärvi

Testing Portugal: Making Your Team Awesome as Just a tester

Maaret Pyhäjärvi

Practices Change - Moving to Delivering Continuously by Maaret Pyhajarvi at #...

Agile Software Community of India

Delivering continuously - easier said than done. As I joined my team delivering Windows Desktop products two years ago with the aspiration of implementing continuous delivery, I was told it cannot be done. It started from the fact that making a single release was five-day effort, and continued with “no user would allow us to deliver frequently”. Two years later, making a release takes us two hours and the way we work together looks very different. With the principle of fixing maintenance issues in the latest release has resulted in improved flow forward and savings of effort in supporting small number of releases. This talk goes through our lessons learned on the journey of shortening release cycles to a continuous daily flow. We’ve experienced three essentially different sets of practices, with the core difference coming from release frequency. The good place is when we deliver continuously. The soulsucking place is when we deliver on two week cadence. And the insane asylum is when we deliver just once at the end of the project. Think of it like this: a pool is not just a bigger bathtub. The things you can do in a pool are different to those you can do in a bathtub. While both are containers of water, they serve different purposes. It is the same with release frequency. While it is all still releases, the continuous ones enable different practices. More details: https://confengine.com/agile-india-2019/proposal/7961/practices-change-moving-to-delivering-continuously Conference link: https://2019.agileindia.org

Agile India: Practices Change - Moving to Delivering continuously

Maaret Pyhäjärvi

Oredev: An Exploratory Tester's Lessons on Security Threat Modeling

Maaret Pyhäjärvi

Working without a Product Owner by Maaret Pyhajarvi at #AgileIndia2019

Agile Software Community of India

For a decade of software product agile, we had worked in a structure where business responsibility of what to build was allocated to a product owner and the responsibility of how to build it was allocated to a development team. Product owner would maintain a backlog, act as voice of the customers. Until one day we realized that the choice of what to build or fix is hard, and critical to everyone’s success. If we wanted to do it poorly, we delegated it to a single product owner. We started a no product owner experiment. For three months, we experienced the development team delivering multitudes of value to what we had grown to expect, and innovate customer-oriented solutions in direct collaboration with customers. Team satisfaction and happiness bloomed. The experiment turned into a continuous way of working. Customer-focused team directly in touch with their customers performs better without a proxy. Join me to learn how the decision power shared for everyone in the team transformed the ability to deliver, and how collaboration is organized with product experts and business representatives. More details: https://confengine.com/agile-india-2019/proposal/7963/working-without-a-product-owner Conference link: https://2019.agileindia.org

AST Webinar: Teaching and Coaching Exploratory Testing with an Example

Maaret Pyhäjärvi

Session on Contemporary Exploratory Testing by Maaret Pyhäjärvi

Agile Testing Alliance

Maaret Pyhäjärvi delivered a session on "Contemporary Exploratory Testing" at #SeleniumSummit21 Maaret Pyhäjärvi is a feedback fairy with a day job at Vaisala, where she works as Principal Test Engineer. She identifies as empirical technologist, tester and programmer, catalyst for improvement, author and speaker, and community facilitator and conference organizer. She was awarded as Most Influential Agile Testing Professional Person 2016, listed on 100 most influential in ICT in Finland by TiVi 2019, and has spoken at events in 25 countries delivering over 400 sessions. To know more about #SeleniumSummit21 please check : https://seleniumsummit21.agiletestingalliance.org/

React Finland: Intersection of Automation and Exploratory Testing

Maaret Pyhäjärvi

AxiomSummit 2022: A Practitioner's Guide to Contemporary Exploratory Testing

Maaret Pyhäjärvi

A new generation of testing is emerging, led by testers who believe test automation is an inseparable part of how we do exploratory testing. Yes, you read that right: exploratory testing with test automation, and on unit, api, ui and e2e levels all at our reach with team collaboration. We work on acceptance criteria and examples in our short increments, yet people are at their most creative on what could go wrong when they use the product or a piece of the product as their external imagination. When we’re creative, we need to do things we can’t do by hand, using programming to extend our reach. When we’re learning, we need to take notes now and to keep for later, again using programming to replenish information we deem worthwhile. We want to work on exploring a category of bugs before implementing, and a category of bugs before releasing, and a category of bugs after releasing. Last year I worked with a team that was transforming from a traditional manual test case + test automation -based approach to contemporary exploratory testing. This year I work with another team that takes this style of testing further than we’ve taken it before with whole-team testing. Let’s learn from a practitioner’s examples of ideas leading into this, changes enabling this, and results we are seeing with contemporary exploratory testing.

MoT Cork: Exploring Realities of Testing - From Theory to Practice

Maaret Pyhäjärvi

Similar to Testbash Australia: Next Level Teamwork - Pairing and Mobbing (17)