Skip to main content

Mob programming - the heaven of a tester. Part1: the beginning


Have you heard of mob programming? Probably you have. If you haven't I stroooongly recommend you to take a look (https://youtu.be/8cy64qkgTyI) or listen (https://soundcloud.com/cucumber-podcast/mob-programming) to Woody Zuill describing the process.

My team has been doing mob development (we call it rather that than mob programming) now for two years, and it is superb. We don't do it all the time, but when we do it is inspiring to be part of a mob. And I think it is very efficient too! Also in my role I have several reasons to argue Why every tester needs a mob (and ever mob a tester), and I want to tell about what usually happens in our mobs, but those are future blog posts. This time I will tell the story of how and why we started mobbing.

I first heard of mob programming from Woody Zuill in Tampere Goes Agile conference 2014. It sounded kind of crazy, five people working on one machine, but at the same time many of the things I heard really resonated. So I was intrigued, but at that time felt that this was beyond my reach and thus didn't actively pursue it. But the seed was planted.

Forwarding a few years, we were thinking in our rapidly growing team of ways how to continue to work as a team and how to break some silos that had formed. So we came up with this idea of work groups. Kind of dynamically splitting into groups of 3-6 people who would take full responsibility on planning, implementing and releasing specific things. And here I now thought that mob programming could in some way fit nicely into this. 

But how to get there? I was the most experienced one with some reading and participation into a single workshop of Agile Finland, and wasn't too comfortable on leading with that. But then on another meetup, think it was tech excellence, I got to talk about this with Llewellyn Falco who was immediately ready to come by and facilitate a 2 hour try out session. And my great colleagues were all up for that. 

So we did it and people liked it. It was fun! Nobody was thinking of going full fledged extreme mob programming, but curious to learn more. Luckily, we happened to have a team gathering coming up, so we decided to do this there for two days straight - and we did. For two days we broke into groups of 4 people & 1 laptop to work on some features. First discuss why to do it, and then go straight into doing it. 

After the two intensive days we had a little retro and made a pretty much unanimous decision to continue to do this. Every week, at least once, each group would do a mob. So that decision has now held for two years - some weeks we do a lot of mobbing, some weeks little. But we do it. And it is the heaven of a tester

I am not saying that this might be for everything, or everybody. But I believe everybody should at least take a shot at this. And as a first step, I am more than happy to recommend contacting Llewellyn who is a brilliant coach for this. 

Just do it.


Comments

Popular posts from this blog

I don't report bugs

I don't report bugs . Bug is such a loaded word that people understand very differently, that instead of using it and explaining what I mean by it I rather just use other words. Like observations, thoughts, surprises, ideas, alternatives, or something similar. (And no I don't use fault, defect, or error either). Bug has also quite a negative connotation. "Reporting a bug" is kind of like telling someone that they've been served. And as we are actually giving away the gift of information, why wrap it in such a nasty package? And maybe more importantly it is very likely that whatever you might have to say is wrong. If not plain wrong, then at least incomplete. So I like to approach the kind of situations with the assumption that I am probably wrong. Cutting off anything that might sound arrogant makes stuff quite a lot easier. Especially after you realise later on that you have been wrong. I leave plenty of observations unreported . I don't want to waste

Testing drunk

(My first blog writing ever.) I've been thinking a long time that it's funny how many bugs I find by accident. Try to do something, make a mistake and boom - a bug is found.  Making the mistakes intentionally doesn't quite work - that's why they are called accidents I guess.. So I've thought of ways to make myself more prone to accidents, coming up with an apparent one; testing drunk. TUI (testing under the influence). So this I gotta try. More to come on that later.

Testers of past be the IT stars of the future?

Been noticing two a bit conflicting themes lately. 1. Testers getting (or pushed) to be more technical and write test automation code 2. Articles listing future IT core skills as widely non-technical So whereas many testers are moving to work more on test automation, the vital skills of the future may be such as: - Creativity -  Analytical (critical) thinking  -  Activ e  learning  with a growth mindset   -  Judgment and decision making -  Interpersonal communication skills - Complex Problem Solving Which sounds almost like a list of vital skills needed for an exploratory tester.  So we should perhaps remind the ones starting a testing career or moving away from it, that also these skills are something that can be quite valuable in the future as well. Maybe even the most valuable.