Agile Testing Days 2016: Wrap Up!

It’s a good thing Pete Walen was attending ATD again, because my live blogging efforts weren’t up to par this year. I posted two blogs so far, but they were neither live nor very detailed. It’s just that I didn’t attend a lot of talks this year. It seems that every year I go to less talks. Don’t assume that I do less learning that way! Instead, I spend my time pursuing certain goals. This year my goals were: pairing with someone, getting to know certain people better and explore making new connections. This is what makes the conference valuable and fun to me. So, did all these things happen? Continue reading

Agile Testing Days 2016, Day 2

In the morning I was having the all too familiar fight with nerves again (every time I am about to give a presentation this happens). I stayed sober the night before, but I had very little sleep. I was already ‘busy’ with my talk in my mind. At breakfast, I struggled with a small egg sandwich again and I just went upstairs and practiced a little. So, no keynotes and other talks for me yet, I wouldn’t hear a thing anyway.

The talk itself went quite alright. I had some technical difficulties. Payed 80 bucks for PollEverywhere and it didn’t even work on dual screen. Yeah, I’m gonna try and get my $$ back. Also, I had tested it on my room and apparently, my session wasn’t closed so the audience saw the last question somehow? It was pretty weird.

Anyway, after the rough start the rest of the talk went smoothly. I had fun and I hope people went away with a little more knowledge and a lot more inspiration. I feel very relaxed now and I’m going to drink a few beers with some people tonight. Cheers, already!

All the information from my talk and resources can be found in Google Drive

During the lunch break we played Eddy’s game Gameception. It’s a really fun game that he designed himself. I’m looking forward to the gaming tonight! Continue reading

Agile Testing Days 2016, Day 1

Never have I ever….Been hungover before a conference even started. Oops, guilty.

I have never started a conference on such a weird note. I guess I have to tell what happened. The short version is: IF you cannot handle a lot of alcoholic beverages, THEN don’t drink a lot of said alcoholic beverages. Seems easy enough, right. Somehow, this little bit of reasoning was too much for me to comprehend.

It all started on Sunday evening, in the bar. This conference is secretly starting on Sunday evening, when some of the people already arrive. It was so nice to see a lot of people again, hugging all over the place! Meike even brought her dog, Hagrid. Such a beautiful animal. We played board games all evening and had a good time. Continue reading

Exploratory Testing with the Team: The Sequel!

As luck would have it, one of the developers I worked with during the time I was doing experiments with getting my whole team hooked on exploratory testing is now also working at my current client. He came to my desk and asked if I was interested in teaching his team about exploratory testing, because he felt it would be very useful. Great to hear, of course! I was faced with a new challenge though. How do you set up an exploratory test session without any domain knowledge? Would it even be an issue? In this blogpost, I’ll walk you through what I did to make the session a successful event. Continue reading

The Thing with Quality at Speed

For the first time ever I’ve had to start writing a blog for the third time over. A new experience to me, because usually the words come flowing. Not this time! The topic is a difficult one in the sense that I have a hard time finding the right words to express myself. It’s so easy for people to misunderstand what you mean.

I already asked a question on Twitter about this topic: “What, according to you, are prerequisites for making Continuous Delivery (CD) successful for a company?”. I got a variety of different responses, which was great to expand my own thought process.

As you can probably guess, I have an ‘issue’ with how CD is implemented in its current form. As always, I feel that people are quick to jump on the ‘tool as solution’ bandwagon, without really assessing what problem they are trying to solve and what the downsides of said solution are. Continue reading