Previous parts of series:
Part 1: Integrating new joiners
Part 2: Daily routine
Part 3. Continuous improvement
3.1. QA Teams retrospectives
Retrospectives could be important not only for product/scrum teams but for guilds too.
That’s why we realized that we need to have them once every 2-3 months at least.
Usually things we discuss on QA retrospectives are following:
- Sharing non-blocking issues. Retrospectives are a great time to bring up any non-blocking issues that testers are dealing with. By sharing these challenges, we might find that others have faced similar problems, and together, we can come up with solutions.
- Improving QA processes. We should regularly look at how we can improve our QA processes. Whether it's refining our checklists, enhancing our documentation, or tweaking our review processes, these discussions help us work more efficiently and effectively.
- Brainstorming new ideas. Retros are a perfect opportunity to share ideas that we might not usually bring up. Even if they seem tough to implement, discussing them as a team can help us figure out their potential impact and how we might make them work.
- Giving kudos. It’s always good to acknowledge the hard work of our teammates. During the retro, we can give a shoutout to those who’ve gone the extra mile. A little appreciation goes a long way in keeping the team motivated.
In addition to enhancing our QA team’s practices, retrospectives also open the door to broader, company-wide improvements. These sessions allow us to step back and consider ideas that can positively impact not just our team but the entire organization. By addressing both team-specific and larger-scale opportunities, we contribute to a more efficient work environment across the company.
For example, in a previous retrospective, we came up with the idea of creating a 'Before Going on Vacation' checklist, outlining what needs to be done to ensure a smooth absence and to avoid being disturbed while on vacation. This initiative not only improved the individual experience for team members but also helped the company maintain productivity and minimize disruptions during employee absences.
3.2. 1-1 meetings
Communication is key to establishing a positive relationship, and we always try to be open and approachable to encourage people to speak up and share their thoughts. Creating a safe space for open communication makes team members feel heard and valued, ultimately improving morale and productivity.
To support this, we hold regular 1-1 meetings between the Lead and each QA engineer every month. These sessions provide a dedicated time to discuss any work-related matters in a focused and supportive environment. During these meetings, we make sure to cover several key topics essential for individual growth and team success, including:
Personal well-being: checking in on the individual's current state and ensuring their comfort within the team.
Progress on long-term goals: assessing the journey towards annual objectives, ensuring alignment and providing support.
Task blockers: identifying and resolving any things that hinder progress of current tasks.
Feedback сhannel: discussing feedback from Product Owners and Line Managers, enabling continuous improvement.
Motivation changes: addressing any non-work-related issues that might affect motivation.
These meetings are a very useful tool for improving relationships within the team. It helps you to track a person's progress toward yearly goals, understand what a person feels currently, motivate and encourage them or help with blockers.
And it’s also important to remember having fun with your direct reports. This doesn’t mean that you have to be best friends, but it does mean that you should be approachable and easy to talk with.
Celebrate successes, acknowledge challenges, and offer support and guidance when needed. This is how we create a positive work environment and build trust.
Part 4: Beyond work is coming soon.
Top comments (0)