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

What is a PBI?

After my last post, I had the question of what is a PBI... so I thought i'd write a short blog post about what they are and why they are used.

A PBI is an acronym for Product Backlog Item. It is a description of a piece of work that your SCRUM team will develop and deliver. When you have a list of Product Backlog Items, you then refer to that collective list as a Product Backlog.

The product backlog is often prioritised and yourteam will work through each PBI, and release on a regular schedule... I am however going deep into the world of Agile development, which isn't entirely what this post is about, so I will stop myself now.

A Product Backlog Item is made up of the following:

Title - This is often a one liner that gives the team an idea of what the PBI is about, although it can just be an ID for the item and the team work off of that.

Description - Breaks down the PBI in a bit more detail, and can be written in any style, however I prefer it to be written as follows: 



By writin…

Dealing with Selenium WebDriver Driver.Quit crashes (Where chromedriver.exe is left open)

We recently came across a problem with Selenium not quitting the webdriver and this would then lock a file that was needed on the build server to run the builds.

We were using Driver.Quit() but this sometimes failed and would leave chromedriver.exe running. I looked around and found this was a common issue that many people were having. We (I say we, as we came to the solution through paired programming), came up with the following, that would encapsulate the driver.quit inside a task and if this task takes longer than 10 seconds, then it will clean up any processes started by the current process, in the case of the issue on the build server, it would kill any process started by Nunit.

[AfterTestRun]
        public static void AfterTestRun()
        {
            var nativeDriverQuit = Task.Factory.StartNew(() => Driver.Quit());
            if (!nativeDriverQuit.Wait(TimeSpan.FromSeconds(10)))
            {
                CleanUpProcessByInheritance();
            }
       }

        private s…

Famous Movie Quotes applied to Software Engineering - Jaws

You're gonna need a bigger boat? How can that relate to Engineering?

Firstly, let me ashamedly admit, that I've never seen the whole of Jaws all the way through. It's on my list of films to watch, but whether I get round to it, is another matter!



Anyway, to apply this to engineering, it's almost like "you're gonna need more testers/developers"...

We hear this all too often when trying to push releases out the door, let's throw men at it... However, as we all know, a bigger boat/more men... isn't always the answer, it's not a guarantee of quality, or even a guarantee of getting things done quicker.

If you have a task that will take 2 hours, simply having 2 people work on it doesn't mean that it is halved, in fact often, the time taken to do the task remains at 2 hours, but the maintainability and the knowledge around that area is increased, so it's a price, in my opinion that is often worth paying.