> ## Content Index > Fetch the complete content index at: https://www.annemariecharrett.com/llms.txt > Use this file to discover other available public pages before exploring further. # Moving to a Quality Coach Role - URL: https://www.annemariecharrett.com/moving-to-a-quality-coach-role/ - Published: 2022-01-29T23:01:48.000Z - Updated: 2022-07-31T00:56:10.000Z - Description: The HoQE performs the role of change agent. It's their job to create a space and framework so that the software tester will achieve a successful transition. - Author: Anne-Marie Charrett - Tags: Tech Leadership, Quality coaching in your back pocket, Quality Coach Role, #60c1d1dd5b103d003bb28239, #60c1d1dd5b103d003bb281bc, #60c1d1dd5b103d003bb28156, #60c1d1dd5b103d003bb2818f, #60c1d1dd5b103d003bb2816a, #64324ade31c943003d684eca, #60c1d1dd5b103d003bb2816c, #60c1d1dd5b103d003bb2823e, #60c1d1dd5b103d003bb28171, #60c1d1dd5b103d003bb281dd, #60c1d1dd5b103d003bb28202, #60c1d1dd5b103d003bb281ca, #60c1d1dd5b103d003bb281f2, #60c1d1dd5b103d003bb281df, #60c1d1dd5b103d003bb28165, #60c1d1dd5b103d003bb281b4, #60c1d1dd5b103d003bb281cf, #60c1d1dd5b103d003bb281c0, #60c1d1dd5b103d003bb2823f, #60c1d1dd5b103d003bb2814f I posted the following on Twitter... > "I'm moving to a quality coach role, how do I ready my team for the transition" is a question I often hear. Anyone got any answers? > > — Anne-Marie Charrett | Number all boxes (@charrett) [January 28, 2022](https://twitter.com/charrett/status/1486963678331035649?ref%5Fsrc=twsrc%5Etfw&ref=annemariecharrett.com) The perspective in mind was a software tester transitioning to the role of quality coach. The responses though offered many different perspectives (the power of diversity)! By correlating these perspectives to stakeholders impacted by the transition, I was able to identify user stories. I enjoy writing user stories with quality in mind. I find it clarifies the why a lot more, something we often forget to do when we think about quality. ### Quality Professional > " As a software tester I want to ready the team so that I can perform the role of quality coach instead of doing the testing". Some great suggestions were put forward in this space and I'll summarise: - Perform a self-reflection (how ready am I for this transition, what do I know, what do I need to know) [@StuC](https://twitter.com/StooCrock?ref=annemariecharrett.com) - Encourage the team members to try the role of a software tester.[@Lanooba](https://twitter.com/Lanooba?ref=annemariecharrett.com) - Speak to the team on the transition and repeat the reflection at a team level (Follow up a week later to allow people additional time and space to reflect as this may be new territory for them and they won't have immediate answers). [@Magnus](https://twitter.com/Mange046?ref=annemariecharrett.com) - Imagine you were going on holiday for six weeks, what information would the team need to do your job? > Assumpt. is they’ve readied themselves 1st. I’d ask how well they know their own craft to take others on a journey. Once they know what they know and decided what’s important, they can start looking for little seeds to sow in conversation and share a map of things to come. > > — Stu C (@StooCrock) [January 28, 2022](https://twitter.com/StooCrock/status/1486967549338259458?ref%5Fsrc=twsrc%5Etfw&ref=annemariecharrett.com) > I’ve found it helpful for the QC to encourage Devs to try their roles for some time; builds empathy. [https://t.co/VMenSqfPOd](https://t.co/VMenSqfPOd?ref=annemariecharrett.com) > > — Nivia \*always\* uplifts Black & LGBTQIA+ Women (@Lanooba) [January 28, 2022](https://twitter.com/Lanooba/status/1487061201448312840?ref%5Fsrc=twsrc%5Etfw&ref=annemariecharrett.com) > Also, since it's not easy for everyone to think about, and process things like this on the spot, I would have a similar meeting about a week later where the team can bring up expectations and questions that has come up. > > — Magnus (@Mange046) [January 28, 2022](https://twitter.com/Mange046/status/1486965591789481984?ref%5Fsrc=twsrc%5Etfw&ref=annemariecharrett.com) ### Delivery Lead > "As a delivery lead, I want to know when and when the team and the quality coach will interact, so that the team will know when and where to perform software testing" When there's loads of uncertainty and no one quite knows where to start, focusing on the delivery process allows the team to have practical conversations about when and where software testing should be performed, and when and where a quality coach might check in with the team. This won't uncover all that 'glue' work performed outside of the delivery process that a software tester typically does, and it doesn't help with improving software testing skills. It's the 'Shu' in the [Shu Ha Ri of learning](https://www.annemariecharrett.com/habits-and-shu-ha-ri/), and so makes it an excellent starting point. > Yes, the formal structure and functional agreement on how to operate helps provide guardrails. Thank you! > > — Anne-Marie Charrett | Number all boxes (@charrett) [January 28, 2022](https://twitter.com/charrett/status/1487184114117939200?ref%5Fsrc=twsrc%5Etfw&ref=annemariecharrett.com) ### Team members > "As a team member, I want to know what how to do software testing well so that I can confidently make decisions about what to test" The more you create and do software testing, the more confident you become in your choices. Software Testers don't have a special magical skill that helps them find bugs, it's years of practice of experimentation. We have a hypothesis, we try out it, and if we're right, we find a bug, or we create a good test. We already know that pairing is a powerful tool when transferring skills and so the suggestion by [Joep Schuurkes](https://twitter.com/j19sch?ref=annemariecharrett.com) got a big + from people. > Transition from doing things yourself to pairing as navigator to pairing as driver. And/or ensemble sessions. So slowly ease off being a team member and move into the quality coach role. > > — Joep Schuurkes (@j19sch) [January 28, 2022](https://twitter.com/j19sch/status/1486966241432686599?ref%5Fsrc=twsrc%5Etfw&ref=annemariecharrett.com) ### Engineering Manager > "As an Engineering manager I want to understand the nature of the role so that I can assess if they're performing the role well, and can reward appropriately" This is critical for senior management who need to be confident that the role is more than waving your hands around encouraging people to "do more testing". Mark Tomlinson explains it well: > Yeah, I 💯agree Mark. It’s a great point. > > — Anne-Marie Charrett | Number all boxes (@charrett) [January 28, 2022](https://twitter.com/charrett/status/1487183705785651200?ref%5Fsrc=twsrc%5Etfw&ref=annemariecharrett.com) Creating career pathways, [creating role descriptions](https://www.annemariecharrett.com/define-the-quality-coach-role/) is important to ensure buy-in and that people are properly compensated for a role that requires leadership skills and nuance in its application. ### Who drives the change? A final stakeholder is required. Someone with the capability to speak to what success looks like has the comm skills to speak to people at all different levels of the organisation, has the power to influence and change. I call this person the Head of Engineering, but it also could be an external consultant. Nicola Lindgren touched on this. > I’m assuming the person is currently a tester in the team. > > Would tell them: > Why it’s happening > What will change > How long the transition period is > > Would ask them if they have any concerns > > Would check in after a while to see how it’s going > > — Nicola Lindgren (@NicolaLindgren) [January 28, 2022](https://twitter.com/NicolaLindgren/status/1486966904099123208?ref%5Fsrc=twsrc%5Etfw&ref=annemariecharrett.com) They have a user story too. ### Head of Quality Engineering (HoQE) > "As a Head of QE, I want to provide support (either directly or indirectly) so that the software tester has the tools and capability to be successful in their transition" 💡 The HoQE performs the role of change agent. It's their job to create a space and framework so that the software tester will achieve a successful transition. A successful transition requires the HoQE considers: - A vision of the future, what does an engineering division with quality coaching look like? - Communications to different groups on the why its impact and the benefits this change will bring. - A roadmap on the steps involved, how long the transition might take for the software tester and the team(s). - Coaching/Support for the software tester as they work through the transition The HoQE creates scaffolding (can be taken down when the structure is complete) for the software tester to apply as they see fit. Scaffolding can include: - a high-level delivery process that identifies touchpoints and rituals related to quality that the software tester can experiment with their team - Strategies for skills-based transferral. Examples could be formal training or guides on how to execute a pairing session. - Reporting methods, quality health monitors etc These guidelines are intended to give the software tester some way of focusing and structuring their work. They are not mandated must do's. Rather the HoQE is providing a set of tools within a toolbox for the software tester to draw upon. How much this is used typically depends on the experience and confidence of the software tester in taking this new role. Like this post? [Subscribe](#/portal/signup) to my quality coaching book [4 weeks free access to quality coaching book](https://www.annemariecharrett.com/intro4)