Skip to main content

Start with the End in Mind - My first presentation at a tech meetup!

I was at a football coaching session the other night, and some other coaches put on a training session for us, so that we could learn and critique it. This is not an easy thing to do, to put something on for your peers and open yourself up to criticism is a difficult thing to do. One of the comments from the president of the club was that in order to develop yourself you need to push yourself and step outside of your comfort zone which it was evident that these coaches were doing.

QE Roundabout

I took this to heart in many ways, a few weeks ago I signed up to do a presentation at a meetup that was only a couple of meetups old, The QE Roundabout. I was in contact with Zoe Canning (the event organiser) and I knew it was something I wanted to do, but it's like anything, saying you want to do something and then putting yourself in a position to do it are sometimes two very different things. Anyway, I volunteered to do one, the theme was Automation & Architecture, and we were free to talk about something that aligned to that theme.

18 months or so ago I'd worked closely with one team in particular, and a big piece of that work was building a culture of Continuous Integration, and how things like the build pipeline, the test automation that we had and the deployment process were as fundamental to the software as the software itself. If we couldn't have confidence in the foundations of the software, then how could we have confidence in the software itself.

I decided to do a talk about that, I thought it was interesting, it was something that I was proud of and it was something that I felt tied in nicely to the theme.

This was it now, I'd volunteered to do it, I just had to spend time working on the slides and the presentation itself. This was relatively straight forward, over the course of my time working with them I had given numerous talks to the teams involved on the changes that we had made, why they're important, and what the result of said changes were. It still involved tying it all together in a coherent way, as I had given multiple presentations, there was nothing that tied it all together. So I spent quite a bit of time fine tuning, making sure the theme was present throughout and ended up with some slides that portrayed the message that I wanted, the message itself ended up being "Start with the end in mind" (which is also one of the 7 habits of highly successful people, but I digress).

By understanding where we wanted to get to, we could figure out just how to get there separately, and ultimately by making that visible and clear to everyone, it ensured that we all understood what was required and what the benefits of it were.

Anyway, I was dreading the talk itself, luckily for me I had a public speaking engagement on the Saturday before the meetup, it was my brothers wedding, so I had prepared a speech, I stopped short of giving the presentation to that crowd, as I wasn't sure they'd be too familiar with Applitools, Akamai, Saucelabs and other things I mentioned in my presentation, but nevertheless it was good practice in front of a friendly crowd!

The day came, I'd done a few practice runs in the office to some peers who provided me with some good feedback, I felt I was in a good place to deliver a good talk, that would hopefully showcase the journey that we went on, but also help people understand that by understanding where you want to go, you can figure out how to get there after. Sometimes people get too bogged down with figuring out the how, that they forget just what the end product should be, and that applies to a number of things in life and not just in technology.

Image may contain: 1 person, standing


I gave the presentation, I spoke clearly and as slowly as I could. I think it went okay, I know there were times that I stumbled a bit, but soon picked up again, and I do need to work on my presentation skills (things like body language), but ultimately for a first talk at a meetup, I think it went relatively well. There were more people there than I thought would be (I think there were about 80 people there), but that's not a bad thing! If I were to do it again however, I think I would spend a bit more time actually doing the presenting with peers as opposed to walking them through the slides, but hindsight is a wonderful thing!


The video should be available soon-ish (I think), and hopefully the people who were there enjoyed the talk, there were a good few questions at the end which can be a good sign... or it can be a sign that nobody knew what I was talking to, but I am hoping for the former!

I'd like to thank QE Roundabout for giving me the opportunity, and I would happily do something similar again, which is a good thing!

Comments

Post a Comment

Popular posts from this blog

Treating Test Code as Production Code

It's important when writing automated tests to remember that the code you write should be up to production standards, meaning any conventions that you have in place should be adhered to and that it should follow good design patterns. Too many people often say why does it have to be as good as production code, it's "Only" a test, so long as it passes then that's fine... To answer this we need to look at why we want our tests to be written in such a structured and efficient manner: - Maintainability - by making the test code structured and efficient, it becomes far easier to maintain and in doing so changes in the future can happen quickly as the test isn't linked to anything that it shouldn't be and it's easy to understand for a new set of eyes. - Durability - Again by making the tests structured they should be resistant to changes, if you change a variable name for instance then it shouldn't effect the unit test unless it absolutely has to....

Testers: Be more like a Super-Villain!

Who doesn't love a Super Hero? Talk to my son, and he'll tell you how much he loves them, talk to many adults and they'll say the same! Deep down, we all love to be the Super Hero, we all want to save the day! However, I want to talk about the flip side of Super Heroes, the Super Villains... I often play Imaginext with my son, and I (unfortunately?) am nearly always the Super Villain! Be it Lex Luthor, Joker, Two Face, Mr Freeze or The Riddler! These are all great characters and great Super Villains, but why would I want to write about Super Villains? A while ago where I worked, we had a few Super Heroes, people who would be able to come in and "fix" things that had broken and help deliver projects on time. We then shifted, we decided to do away with the Super Hero culture and try and prevent from being in that position in the first place, whilst we didn't go as far as wanting to hire Super Villains, it's definitely a story that has stuck with me and t...

Using BDD and gherkinising your Acceptance Tests

In my post Testing of Automated tests , I mention about a BDD framework which involves using BDD to drive your acceptance tests. BDD stands for Behaviour Driven Development.  One effective method of writing BDD tests are by using a format known as Gherkin language. These consist of Given, When, Thens. The main advantage of the gherkin language is that it's readable by the business, and in an ideal world forms part of the Conditions of Acceptance around a PBI. Also, using a Visual Studio plugin of SpecFlow , you can integrate your Gherkinised COAs into your solution with feature files, and then drive the automated tests, however, for this post I will focus solely on how to effectively gherkinise your acceptance tests. A Feature file consists of a feature outline, which details what the feature file is testing followed by Scenarios and examples (parameters).  The BDD scenarios are made up of a Given, When, Then... These are effectively an initial state (Given), an action (W...