As an esteemed team member, you will need to be involved in welcoming a new team member to an existing team. You have to make them feel welcome and productive. Consider these following ideas to make the first few weeks great.
The Basic Plan
By failing to prepare, you prepare to fail - Benjamin Franklin
- Initial Preparation - When you know a new teammate will be joining you, you ensure that all the hardware and software are ready to go (Office equipment, emails, network access, project documentation)
- A day’s worth of meetings - Plan the first day of the employee with meetings. Introduce him to everyone, schedule a few one-on-one meetings to discuss how their role will be fulfilling the company goals.
- Assign a buddy - The buddy will be the one showing the new member around, sit next to him to get grips, be available for answers, and just be generally helpful
- Welcome with food - If the budget allows, food is always a nice welcome.
What is your mission?
He who has a why to live can bear almost any how - Friedrich Nietzsche
The new team member should understand the mission of the company.The mission is a way to direct a business in the right direction and play a huge part in making business decisions. Without a mission, there is no way to plan to progress.
Before starting any project, the team members must understand the purpose. Why does your company exist? How will this project contribute to the company mission? How will this project benefit my self-development? If you don’t answer these questions, you may find yourself without any direction.
Familiarising with the product
When one encounters enough strangeness, then what is strange ultimately becomes familiar - John Connolly
The member of your team is new! He may or may not be experienced in testing. In their first few weeks of familiarising with the product, it would be good to have them test if the testing documentation makes sense.
It’s worthwhile to have the new member of your team to look and act out what the testing documentation is telling them to do. They might even find some glaring issues with the system or the documentation.
Have the new tester open bugs and fixed bugs.
For each of the reports, the new member will test if the bug can still be replicated, the version of the software, any hardware and software configuration tested with. The bug might also not be reproducible so the ticket may need further investigation or be closed
The tester will look at closed reports to check if old bugs are still appearing. Perhaps a new entry can be recorded when a bug appears again and any further details.
Familiarising with the workflow
Once the user is familiar with the mission and what the product is meant to do. The new member should be given time to try out the product. When a person looks at something for the very first time, they tend to be very intrigued so have them list out all questions he has, what are their suggestions on improving the workflow, and what they would do with the product?
The goal of acting out the documentation and familiarising with the workflow is so that they can be a more informed and effective critic to have the mindset of finding failures and shortcomings of the product!