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 )
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ā.
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
I wonder what people think of when they see practice quality something?!
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.
Another unfamiliar phrase that apparently Iāve been doing for over a decade in my last two roles.
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.
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.
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
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.
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.
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.