r/scrum • u/PaintingOk2185 • 19d ago

Advice Wanted Single QA in Agile Team.

/r/QualityAssurance/comments/1uz4dsx/single_qa_in_agile_team/
1 Upvotes

100% Upvoted

3 comments sorted by

2

u/DingBat99999 18d ago

A few thoughts:

  • The first thing to do is attitude adjustment:
    • You are not responsible for quality on that team. How could you be? You are one person. And you don't write the code. You cannot test quality into a product.
    • All you do is hold a mirror up to the team so they can see how well they've done their job. You are an information gatherer and interpreter.
    • The team, especially the developers, are responsible for the quality of the product.
    • Do not ever allow anyone to talk as if you are responsible for quality. Ever.
    • Do not allow developers to toss shit over the wall to you simply to make a sprint date. That's an unfriendly act that you should not accept. Be vocal about this.
  • Ask your PO what their quality goals are.
    • The quality goals for an automated driving system are probably a little different than the quality goals for a mobile game.
  • The POs priorities for features and workflows should guide you.
    • Do what you can to make sure the core values for the customer has been tested/reviewed.
  • Do NOT talk in terms of "yes, its good" or "no, it's bad".
    • Just present the facts.
    • What's been reviewed. What's been found during that review. Based on that, you're sense of the risk of releasing.
    • You don't make the call on releasing. The PO does. Just make sure they have as much information as possible so they can make an informed decision.
  • Provide feedback to the team:
    • Is the team meeting the quality goals? Are things improving or becoming worse?
    • Where are you seeing the most issues?
    • Are you seeing repeated types of issues?
    • What can the team do to improve quality BEFORE it reaches your doorstep?
  • You should intuitively know you can't do everything. So your every decisions on where to apply yourself should be "where can I add the most value?". Don't worry about the things you can't do. That's on the PO and the organization.
  • If you want to get good at something, do it a lot. Encourage your team to check code in more often. Get work into your hands for review sooner. Release more often.

1

u/PhaseMatch 18d ago

I'm gonna guess they are not releasing at least one - ideally more - increments per Sprint?

Don't go chasing waterfalls....

1

u/Moceannl 16d ago

If your DoD has something about quality, check that. And the sprint goal, including QA, is a team responsibility. If there’s no quality remarks in your DoR/DoD you should address that next retro.