Does your company practice Quality Coaching?

Itā€™s poll time to support our next Testing Planet episode on Quality Coaching.

Help us out! Your contributions matter and count towards our ongoing research and creation for the MoTaverse.

Does your company practice Quality Coaching?

  • Yes
  • No
  • Sometimes
  • Something else, please comment
0 voters

:star: Bonus points for any community commentary

3 Likes

We donā€™t practice a specific model or framework, so Iā€™m really interested to see this planet testing episode (well Iā€™ll catch up with it as Iā€™ll be on annual leave :grimacing:)

However, I have been over the last year ā€œmarketingā€ our QA team so that we are involved in quality discussions early so we can influence other stake holders in discovery and design phases to prevent quality issues coming to the QA team in the first place.

I think that is the key lesson Iā€™ve learnt is to stick your foot in the door of these earlier stage discussions to ā€œsellā€ our quality coaching skills so that we become less ā€œthe people that test itā€ and more the ā€œkey quality consultantsā€.

4 Likes

Without knowing what you mean by Quality Coaching I canā€™t tell if we do it.
Can you give an explanation which is independent from the presentation?

1 Like

I, probably as everyone else responding, think of random quality attributes and practices that happen in their company, for which thereā€™s some higher force that watches and coaches :slight_smile:

I wonder what people think of when they see practice quality something?!

1 Like

I am not sure if I have heard that word in my organization, but when it comes to quality, my company and team lead consider it as a team effort rather than an individual goal. Everyone is encouraged to follow standard quality practices and share their ideas, challenges, or anything on teams or meetings or dsm, that can help improve the overall product quality.

I believe while this may not fully align with the formal definition of quality coaching, however, encouraging a collaborative approach toward achieving better quality brings us a step closer to it.

1 Like

Another unfamiliar phrase that apparently Iā€™ve been doing for over a decade in my last two roles. :face_with_monocle::nerd_face::clap::woman_shrugging:

Iā€™ve always found coaching the wider project team and department in quality and testing methods and practices, helps them own their products and increases a desire to deliver better solutions.

As a bonus it also supports better testing through more people with unique perspectives getting involved.

2 Likes

The Quality Coaching definition is probably a good place to start looking. Also this collection on Quality Coaching if you have more time to spare.

1 Like

I was talking at a local QA/test meetup 5 years ago about how we work with QA coaching at King.

Nothing fancy or mind-blowing, and pretty basic and easily implemented.

No, doesnā€™t specifically practice quality coaching, but we believe quality is everyoneā€™s responsibility and each team member plays a role in maintaining high standards and preventing issues.

We donā€™t formally use the term or practice Quality Coachingā€¦But we do have quality practice throughout our development process. Like feedback loops are in place at every phase, ensuring continuous improvement. Teams follow structured checklists before handovers, ask questions to enhance clarity, and align on acceptable quality criteria. Our focus goes is just not reporting and fixing bugsā€¦we enable everyone to take ownership of quality as a shared responsibility across the team.

Iā€™m still having difficulties with it. Just a few of the things that come to my mind:

  • the quality of our coaching in relation to testing methods, processes, behaviors? As a parallel I found an interesting book on that on the US Olympic coaching team site. https://assets.contentstack.io/v3/assets/blt9e58afd92a18a0fc/bltb81075e3a25f4fe8/657217053cd0d7d49478198f/USOPC_Quality_Coaching_Principles.pdf
  • coaching the team on actions that could lead to improvements of the product quality?
  • coaching related to the quality of processes that guide the building actions of a product through software development?
  • quality of the code through guidelines, alignment of setup, configurations of systems, application of standard methods specific to the technical stack?
  • quality of the company according to the international domain specific standards? like ISO 9001:2015
  • quality of the service offered to clients? feedback loops, contact and support center, guidance on product usage, ease and support of onboardingā€¦?
  • coaching related to people in the team in regards to their productivity in their role (quality/ethic of work) and improvements they can make?

To me, what I see in those articles on MoT are characteristics and responsibilities
that someone should be doing in their role as a tester.
If a tester doesnā€™t regularly attend to those tasks, what are they doing there anyway?

'Some of the things done by a quality coach in a typical working day:

  • Attend sprint demos
  • Work with stakeholders to understand upcoming features thoroughly
  • Read the documentation and contribute to it
  • Lead practical workshops for testers and non-testers
  • Teach testing techniques to developers and other people in non-testing roles
  • Participate in bug analysis
  • Take part in triage sessions, such as going over production defects
  • Organize mob-testing sessions throughout the organization
  • Promote pairing
  • Propose and implement quality improvements
  • Use monitoring to obtain data about the use of the product by real-world customers
  • Analyze existing metrics and propose improvements
  • Teach by doing: join the teams in their regular testing activities
  • Take part in regular meetings, such as scrum events
  • Formulate a quality road map for the whole company
  • Practice individual one-to-one coaching with team members
  • Work closely with domain experts
  • Establish new and improve existing processesā€™
    From Quality Coaching: A Road Less Traveled | Ministry of Testing
1 Like

This raises another great question - what do people think are ā€œstandard quality practicesā€?

I hate the term ā€œbest practiceā€ but encourage ā€˜good practiceā€™ in engineering as that relates to skills - where ā€˜bestā€™ is more toned to ā€œthis is how it SHOULD be doneā€ instead of it could be done. Every engineering/delivery team will have nuances in how they work and for agile delivery that needs to be considered.

1 Like

I see your point however with standard quality practices i mean the standard set by my organization and testing team leadership like what should be the acceptance criteria for accepting the quality of build or on what parameter we can decide if the quality of build is ready for deployment, etcā€¦ That word specifically target the rules and standard by my company for the products that we deliver.
And i use the word standard because even though there are different projects and different teams are working on that inside my organization, still same rules are appliable for them when it comes to deciding the quality of the build.

For e.g. if we receive a build and more than 50% ticket fail then we reject the build because it doesnā€™t match the minimum standard that has been set by my organization for quality of build while accepting it for testing.

Great to pull out that list of ā€˜things quality coaches doā€™, that would be good to explore more.

In my experience, QA Engineers often serve as the testing expert and quality coach within their teams. Interestingly, I donā€™t frequently use the term ā€˜Quality Coachingā€™ day to day.

I find it most effective to collaborate with my teams in finding solutions, all while guiding them to take ownership. Emphasising that ā€˜quality is the responsibility of the entire teamā€™ is key. Itā€™s important to clearly communicate expectations and how the team can support these goals, as well as explicitly define ownership for various aspects of testing and quality.