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

Periodical retrospectives are lame

  "You got nothing, not a single thing?! Well lets just end this here then." I remember well when I said this, being very frustrated. About ten years ago I had been working as a Scrum master for a team some months, and putting quite a lot of effort into planning our scrum teams sprint retrospectives. Lot of work also because I felt we were not getting too much out from them; not very good discussions, very few actions, and even the few actions we did come up with did not stick.  And then it happened: a retro where none of the participants came up with anything to say about the sprint. Regardless of the retro topic boxes, reading of books on retrospectives, getting inspiration from tools like retromat.org, having them in different places, using all kinds of different formats and rainbow coloured post-it notes. Not a single thing. Blank.  So then I said the words, out of frustration, mainly to myself. Why couldn't I get this thing everyone is so hyped about to work? Af...

Testers doing test automation - is that the most important thing for you to do right now?

I've been thinking quite a lot about tester's moving to do test automation.  Lately beause of these three things: 1.  European testing conference , a great testing conference I attended couple of weeks ago. It is very cool due to many things; the way the speakers get compensated, the focus on the conferring side of conferences making it very easy for people to discuss stuff, the way the talks are chosen, and because there are also a lot of developers joining. So anyway when I was talking with several of the attendees, it was a bit strange how it was easier for me to talk about the product development as a whole with the developers, where as with the testers it more naturally moved into talk of automation and tools. Also on the open space, I think the majority of the topics pitched was automation or tool related. And quite little on the process or on the customer facing side of product development.  2. In my company there are a lot of different products and...

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.