Skip to main content

Friends of good software aka Frogs unconference

Attended a week ago the Frogs (friends of good software) online unconference https://frogsconf.nl/.

Unconference type of events are these days pretty much the only type of conference I wish to participate. They almost automatically establish what many more traditional desperately try - discussions and interactivity.

Frogs was no exception, and was also extremely well organized.

It followed a typical unconference/openspace format, of creating the content and schedule of the conference in the beginning, and then people attending the ones they find most interesting. The conference organizers have background in testing/qa type of work, which is why there where a lot of testing minded people attending, but happily there were also a lot of people from different backgrounds. 

We were using Welo as the platform for the unconference and it worked well, allowing you to move virtually between rooms and hangaround places. Depending on the timeslot, there were 3-5 topics happening at the same time. 

I usually pick the topics where there are least people, because that often makes the sessions more conversational and also you get to know the people on the sessions. So my picks for the day ended up being:

- Getting whole dev team involved in e2e test automation (my own pitch)

- Designing reward systems and incentives for teams/orgs that practice co-creation

- Workshop: Playing around with Playwright

- What is my job if I can’t do any testing, choosing not to have access to system under test?

- Embrace failure; revisiting Boehm’s curve in a DevOps world

Very interesting discussions with great people, laving with lots of ideas and spark for next few weeks of work :)

The next Frogs unconference one is gonna happen somewhere in February I heard, and I am definitely going to join it. And waaarmly recommend the same for everyone else.

Frogs unconference - 12 points! 

Comments

Post a Comment

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? After t
Post a Comment
Read more

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
Post a Comment
Read more

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.
3 comments
Read more