Skip to main content

Making new members of your team feel welcome

Where I am at currently, we are recruiting a high number of new QA and it seems that every QA meeting there is a new face, and sometimes more than one. I'm beginning to think how can we make them feel welcome, and at the same time how can we keep some form of team spirit. So in no particular order...

Firstly, to ensure that they feel welcome it's important to have things set up and ready for them to use from their first day. This can be anything from hardware, to user permissions to even providing them with a notebook and pen. I've seen it all too often, and experienced it myself on some occasions, turning up to my first day in a new role, and not having a pc, and on one occasion not even having a desk. In order to feel part of a company, and welcome, then it is extremely important that the company is ready for you to start, not only from a financial aspect (ie. you sitting around doing nothing and getting paid, generally isn't productive for the company), but I love starting a new job and getting my teeth into something and hitting the ground running.

Secondly, introductions to people you will be working with, be it other members of the QA team, other members of the Dev team, or even other members of the Business who you will be liaising with on a regular basis. This does work both ways, if, as a new starter, you don't know someone, don't be afraid to ask who they are and introduce yourself, 9/10 the other person will be wondering who you are too!

Next up, is to let the new starter aware of any training that they are entitled to, if you let them know that there is training in place, and you can progress, it will instantly make someone feel at home and a part of the team.

Often, a good way of getting someone to know about the business and any training that is offered, can be in the form of buddying, this doesn't have to be in relation to QA specific queries, but any query that the new starter has (from something mundane as where can I get good coffee to something work related) can be answered by the buddy, or the buddy will more often than not know who to ask to get an answer. If this buddy system is in place over a prolonged period of time, the new QA will eventually be in a position to be able to do buddying themselves and help new members of the team feel welcome and at home in their new role.

Also, an induction pack is invaluable. This can be in the form of a wiki, or a hard copy of a document. This can include company specific things, but to generalise, it would be useful to include things like release processes, information on a regression pack, an overview of systems architecture, any third party services that are used, information around any automation pack and how the test environments are set up in your company. If the new starter wants to be involved/learn more around any of the areas then at least they have a starting point at which to begin with.

And finally,  and the one that is often most enjoyed..... Drinks :) Nothing makes someone feel more welcome than going out and having a drink with them, or even a lunch if they don't drink. Speaking to people outside of work definitely adds another dimension to a work relationship, and will almost certainly make the new starter feel welcomed :)

As a side note, when creating this blog, I decided to start messing around with MindMaps, and found it extremely useful... I'll definitely be trying to use it where I can when it comes to test planning etc. I'll share my mindmap for this post here:


I'm sure you can expect a blog post on mindmaps in the near future!



Comments

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...