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

Coding something simple.... or not! Taking a screenshot on error using Selenium WebDriver

I recently wrote a little function that takes a screenshot at the end of a test if it has errored. What sounded very simple at the start turned out to be quite a bit of work, and quite a few lines of code to handle certain scenarios! It's now over 50 lines of code! I'll start with what I had at the beginning, this was to simply take a screenshot in the working directory, we are using SpecFlow and Selenium to run the tests, so we are going to check if the ScenarioContext.Current.TestError isn't null, if it is, then using Selenium, take a screenshot (note the below code is a simplified version of what I had at the beginning). [AfterScenario]         public static void TakeScreenShotOnError()         {             if (ScenarioContext.Current.TestError == null) return;             var screenshotDriver = Driver as ITakesScreenshot;             if (screenshotD...

How to manage resources within new teams?

Working where I work we are constantly spinning up new teams to take on new workloads as business come up with new demands and new features they want developed and tested. The problem with this is how do we ensure the work of the newly spun up team is of sufficient quality. One method is by taking people from other established teams and placing them on the new team. This works great for the new team, but unfortunately it will oftenl eave the established team lacking in a resource whilst they try and fill the gap left by the person who has left. We are seeing this often with our offshore teams, it can be damaging to the team structure and the teams velocity, but try as I might, I can't think of another way around it. It's far easier to take 1 person from a team that is established than it is to build a whole new team from scratch. At least by leaving the core of a team in place, you should be guaranteeing that the new team are aware of any coding standards or any QA standard...

Considerations when creating automated tests

We recently released to a number of teams our automated regression pack that has been worked on over the past few months. This regression pack tests legacy code, but contains a large number of tests.  As a bit of background, a number of teams are working on new solutions whilst some are still working on legacy code. With this in mind we constructed an email with a list of guidelines when creating new tests that need to be added to this regression pack.  I figured that these can be quite broad so should apply for any organisation, so thought it would make an interesting blog post...  So here goes,  when creating automated tests, it's important to consider and adhere to the following: - Think about data . The tests need to retrieve or set the data they need without any manual intervention - This should help them be more robust and easier to run without manual intervention. - The tests need to be idempotent - By making it so that each test is standalone and does...