Category: Conference (Page 3 of 3)

Decisions on conferences

This afternoon I read an interesting post from my colleague and fellow DEWT member Jean-Paul. In his post he askes the question: “What do you, or rather what does your manager, see as valid justification to attend a conference?”. The funny thing is, that I am manager at the same company Jean-Paul works at so I am one of those manangers who have to decide if testers can go to conferences or not.

While I was thinking about this, I realised that to express my opinion I need to answer 3 questions:

1) Why should testers attend conferences?
2) What are the criteria I use to justify if somebody can go to a conference?
3) What do I expect from testers who go to conferences?

To answer question 1: I fully agree with Jean-Paul: “Conferences typically are the place where you can learn the latest developments and opinions, submerge yourself into the testing mindset, confer with your peers, refresh your ideas and expand your network.”. So that is why I think every tester who is serious about learning and becoming a better tester, should attend conferences.

Before I can answer question 2, I must explain something first. There are a lot of conferences nowadays and I wonder why people always want to go to EuroStar. I admit that it is one of the best known conferences around (in Europe) and it has been one of the few international highly regarded conferences until a couple of years ago. But there are more conferences so why go to EuroStar? I am not saying you should never go to EuroStar, but maybe there are other interesting events or conferences around? In the Netherlands we have quite a few, so maybe a tester can attend those first before going to fly around Europe to visit EuroStar?

The criteria for attending conferences I use are almost the same I use for courses. Roughly these criteria are: do we have budget, does the testers need the course and is this the best way to gain the knowlegde? So if a tester can tell me why he wants to go and what he is going to learn at the conference he is halfway in getting a green light. The exact justification differs per person, so it is hard to describe them here. But it needs to fit in the testers development plan, the departments strategy and again in the budget. But the justification isn’t fully “hard”. There are soft criteria which can’t be measured easily. I mean things like: do I think the testers earns this? Do I grant this to the person? There are a lot of other ways to learn and to become a better tester. And if someone, for example, would read books, read or even write blogs or is busy learning by not only working or attending courses payed by his boss, he makes a good chance with me to get a green light.

The last question is even harder to answer. But yes, as a manager I expect something in return: a good learning experience! So you can expect that we’ll discuss what you have experienced and learned afterwards. I expect that you ask yourself some critical questions like: what did I take home from the conference? What can I use? Where can I improve? Which topic is interessing for further study? For yourself but also for your colleagues and for the organisation you work for. There is always some benefit and what is it? Sure it is hard to really use something from a conference in your daily work. By discussing it with the people who didn’t go, this will become much easier! And if you saw presentations you didn’t like or you maybe even thought they were complete nonsence, explain yourself why and discuss this with your peers. Maybe even find the presentor after the talk and tell him why you didn’t like his talk. The same counts for courses you attend. If you only go there and do nothing with it, the learning benefit is relatively low. So work with it!

Other benefits you can have from conferences are the ones Jean-Paul mentioned: a boosted testing mindset, good discussions with peers and networking. And I think testers should be aware of these “side effects” and be ready to explain them to your manager. This might help you convince him (or me) to let you go.

First DEWT peer conference

Pre-conference drinks

After a long and instructive week of RST, I picked up Michael at his hotel on Friday evening and we drove to Driebergen for the first DEWT peer conference (#DEWT1). We checked in and went to our rooms for a small powernap waiting for the others to arrive. Since the conference would only start the next day, we had the inevidiable drinks and fun. You can imagine that putting 7 testgeeks in the same room will end up in enjoyable stories about our craft. The bar closed at 23:00, but we found the night porter happy to bring us more drinks. Somewhere around 2 a.m. we went to bed after a very entertaining evening/night.

Opening by morning chair Ruud Cox

On Saturday Michel and Jeanne joined us after breakfast and our DEWT conference could finally start. Ruud being the chairman in the morning kicked off thanking everybody for being there.

Artful Testing
Zeger did his “Artful Testing” talk. A very well done talk using a amazingly beautiful prezi. Although he had 15 minutes according to the program he managed to keep us facinated for triple the amount of time. He must have paid Ruud to get his extra time ๐Ÿ™‚ Or was it because his talk kept us all from looking at the clock?

Zeger Artfully in action

Zeger’s talk was about (without giving away too much) the connection between testing and art. The ingredients were:

  • how testers can benefit from arts
  • some good comparisons between art and software, testers and art critics
  • some nice “artful testing” heuristics, too bad they are still without a nice mnemonic, but Zeger might change that over time.
  • a good testing challenge
  • nice photo’s and other pieces of art
  • Ambiguities, mystification and anagrams (nope no Da Vinci Code here)

I don’t know what Zeger loves more: art or testing, but he sure did a good job combining them. This talk is on the program of the Belgium Testing Days and I suggest you go and see this talk! I hope Zeger will also send in his talk for the TestNet fall event as well.

 

Michael Bolton on Transpection

Transpection
Michael Bolton was up next on the topic transpection. We asked Michael to help us explore the intruiging “tool” of transpection. After a short introduction, referring to several post by James Bach and himself we started an exercise. We did the exercise in pair, where we were to collect information on the subject. Michel and I searched some articles and then tried a little transpection of our own. In the round up we collected all information in a nice mindmap.

BTW: See Zeger’s blog for more information on how we studied transpection.

Lighting Talks

After lunch Jeanne took over as conference chair and lighting talks were on the program.

Jeroen Rosink

Jeroen Rosink: Testing Pyramid, about testers in the classic career path (test analyst – test coordinator – test manager) getting more senior in their job and there are only a few places at the top of the pyramid.

Me: The power of knowing nothing, about people without knowlegde asking lots of good questions, not being biased. And the usefulness of telling people why instead of how. Inspired by my first days in a new job and this video of Simon Sinek.

Zeger van Hesse: Bader Meinhoff-phenomenon, about the advantage of knowing a lot. Since the phenomenon says that when you have seen it once, you start recognizing it more often. A powerfull thing for testers.

 

Introducing RST in Dutch projects
Ray talked about his experience on how he tried to introduce his take aways form the RST training in his projects. An interesting discussion followed Ray’s short talk and we made a mindmap on how to make the case for Rapid Testing. At the end a discussion from the RST class in the week before the conference about giving release advices popped up again.

Credibility

The last talk was done by Ruud on Credibility. Ruud referred to a presentation on this subject by Randy Rice which inspired him. Credibility is build on trust and is one the most valuable assests a tester has. If you lose your credibility you will have a though time doing your job. Ruud showed a cool heuristic he uses to keep reminding himself on the key factors of credibility. He also made a nice design he can put on his monitor so he is reminded whole day.

 

STYLE by Ruud Cox

STYLE

  • Safety language
  • Two ears one mouth
  • Yes but
  • Lighten up a little
  • Empathy

After this topic the conference was officially over and we had some drinks (with nice testing games), dinner together (with some yes/no question mysteries and lifting my parrot jokes to perfection) and we left for home. This conference was excellent!! Why? It was great fun, I learned a lot, got to explore some really interesting topics with cool colleagues and went home with a lot of new ideas. Thanks guys!

Ray Oei, our technician, at work

This conference was attended by: Jeroen Rosink, Ray Oei, Jeanne Hofmans, Michel Kraaij, Huib Schoots, Jean-Paul Varwijk, Ruud Cox, Zeger Van Hese, Michael Bolton. Peter โ€œSimonโ€ Schrijver and Anna Danchenko could not attend.
Ray filmed the whole day, I’m curious about the movies he made….

Newer posts »