Book a Demo Try Speak AI Free Login

Quality Assurance Meeting Agenda Template (45 Minutes, With Metrics)

Use this agenda to run a regular QA meeting that looks at numbers, not stories. It covers defects, escaped bugs, test coverage and release readiness in 45 minutes, and ends with owned actions.

Book a DemoTry Speak AI Free

Used by 300,000+ individuals and teams. Free trial, no credit card required.

Quality assurance meeting agenda: the template

Seven timed items for a weekly or sprint-end QA meeting. Each has an owner and an example entry, so you can see the numbers and detail to bring.

Quality assurance meeting agenda

Total time: 45 minutes

  • Product or release: [Name and version]
  • Date and time: [Date, start time]
  • Location or link: [Room or video link]
  • Facilitator: [QA lead]
  • Note taker: [Name]
  • Attendees: [QA, developers, product owner, support rep]
  • Reporting period: [Sprint or dates]
  1. 0:005 min
    Review last meeting's actions

    Read each open action with its owner. Mark done, carried over or dropped. Do not discuss detail yet.

    ExampleFlaky checkout test fixed by Aisha: done. Staging data refresh: carried over.
    OwnerQA lead
  2. 0:058 min
    Defect and test metrics

    Show open defects by severity, defects found versus fixed this period, and test pass rate. Compare with last period.

    ExampleOpen: 3 critical, 11 major, 24 minor. Found 38, fixed 41. Automated pass rate 96%, up from 93%.
    OwnerQA lead
  3. 0:138 min
    Escaped defects and root causes

    List bugs customers found. For each, say which test should have caught it and why it did not.

    ExampleInvoice rounding bug reported by 6 customers. No test for 3-decimal currencies. Add case to regression suite.
    OwnerSupport rep and QA lead
  4. 0:217 min
    Test coverage and gaps

    Review coverage on changed areas and any manual testing still needed. Name the riskiest untested path.

    ExamplePayments module 82% covered. Refund flow has no automated test. Manual pass planned for Thursday.
    OwnerTest engineer
  5. 0:287 min
    Release readiness

    Check the release criteria one by one: no open critical defects, regression suite green, sign-offs in place. Make a go, hold or no-go call.

    ExampleCriteria met except 1 critical defect (PAY-208). Hold until fixed and retested, decision Wednesday 14:00.
    OwnerProduct owner
  6. 0:355 min
    Process and tooling issues

    Ask what slowed testing down this period: environments, data, flaky tests, unclear requirements. Pick the top one to fix.

    ExampleStaging was down for 2 days. Action: add a health check alert and a named owner for the environment.
    OwnerFacilitator
  7. 0:405 min
    Actions and close

    Read back each action with owner and date, and say when the notes will be shared.

    ExampleFive actions recorded. Notes in the QA channel by end of day.
    OwnerFacilitator

Action items

Task Owner Due
Add a regression test for 3-decimal currency rounding Aisha [Date]
Retest PAY-208 and report go or no-go for the release Test engineer [Date]
Set up a health check alert for the staging environment DevOps engineer [Date]
Copy as textDownload .txtPrint or save as PDF

Copy-ready agenda text

Paste this into Google Docs, Word, Notion or an email. Replace anything in [brackets].

Copy the text
QUALITY ASSURANCE MEETING AGENDA

Product or release: [Name and version]
Date and time: [Date, start time]
Location or link: [Room or video link]
Facilitator: [QA lead]
Note taker: [Name]
Attendees: [QA, developers, product owner, support rep]
Reporting period: [Sprint or dates]

TIMED AGENDA (45 minutes)

0:00  Review last meeting's actions (5 min) | Owner: QA lead
      Read each open action with its owner. Mark done, carried over or dropped. Do not discuss detail yet.
0:05  Defect and test metrics (8 min) | Owner: QA lead
      Show open defects by severity, defects found versus fixed this period, and test pass rate. Compare with last period.
0:13  Escaped defects and root causes (8 min) | Owner: Support rep and QA lead
      List bugs customers found. For each, say which test should have caught it and why it did not.
0:21  Test coverage and gaps (7 min) | Owner: Test engineer
      Review coverage on changed areas and any manual testing still needed. Name the riskiest untested path.
0:28  Release readiness (7 min) | Owner: Product owner
      Check the release criteria one by one: no open critical defects, regression suite green, sign-offs in place. Make a go, hold or no-go call.
0:35  Process and tooling issues (5 min) | Owner: Facilitator
      Ask what slowed testing down this period: environments, data, flaky tests, unclear requirements. Pick the top one to fix.
0:40  Actions and close (5 min) | Owner: Facilitator
      Read back each action with owner and date, and say when the notes will be shared.

ACTION ITEMS
Task | Owner | Due
[Task] | [Name] | [Date]

How to run this meeting

  1. Send the numbers the day before

    Post the defect counts, pass rate and escaped bugs in a one-page summary the day before. The meeting is then for decisions on the numbers, not for reading them out.

  2. Look at escaped defects first

    Bugs customers found are the clearest quality signal. For each one, ask which check should have caught it and fix that gap. Do not spend time on who wrote the bug.

  3. Use fixed release criteria

    Write the go or no-go criteria before the meeting, such as zero open critical defects and a green regression suite. Then the readiness item is a check against the list, not a debate.

  4. Cap each item and park the rest

    Defect triage can eat the whole hour. If a single bug needs more than two minutes, give it an owner and take it offline, so you finish all seven items.

Keep the defect numbers and release calls on record

QA meetings produce specific numbers and go or no-go calls that are easy to misquote later. Speak AI records the meeting and gives you a searchable transcript and the actions.

  • Record the QA meeting on Zoom, Google Meet or Microsoft Teams, or upload the file.
  • Get a transcript with speakers labelled, so the release call is attributed to the right person.
  • Get an automatic summary of metrics discussed, root causes and release status.
  • Get action items with owners and dates, ready to move into your tracker.

See how the AI meeting assistant and the AI notetaker work, or start with a free account.

Book a DemoTry Speak AI Free

Frequently asked questions

What should be on a quality assurance meeting agenda?

Open actions, defect and test metrics, escaped defects and root causes, test coverage gaps, release readiness, process problems, and next actions. Give each item an owner and a time limit and bring the numbers in advance.

How long should a QA meeting be?

Forty-five minutes suits a weekly or sprint-end QA meeting. Daily QA stand-ups should be 10 to 15 minutes on blockers only. A monthly quality review with leadership can run 60 minutes.

What is a good structure for a QA meeting agenda?

Start with the previous actions, move to metrics, then root causes of escaped bugs, coverage gaps and release readiness, and finish with actions. Put decisions in the middle while people are fresh.

Who should attend a quality meeting?

The QA lead, test engineers, a developer from each active team, the product owner, and someone from support who sees customer-reported bugs. Add operations if environments are a regular blocker.

What metrics should a QA meeting review?

Open defects by severity, defects found and fixed, escaped defects, automated test pass rate, coverage on changed code, and time to fix critical bugs. Pick five and track them over time so trends are visible.

Related templates and tools

Process Improvement Meeting Agenda TemplateRisk Management Meeting Agenda TemplateSupplier Evaluation Meeting Agenda TemplateAll meeting templatesAI Meeting AssistantAI Notetaker

Run your QA meeting, then keep the record

Book a demo to see Speak AI record a QA meeting and pull out the decisions and actions, or try it free on your next call.

Book a DemoTry Speak AI Free