In Agile teams, Scrum ceremonies such as sprint planning, daily meetings, and retrospectives help to structure the development cycle. However, additional coordination is often required when it comes to Quality Assurance. This is where dedicated QA meetings come in.
That said, team meetings are essential to the smooth running of any software project. This is something that becomes obvious when you are used to working with the Scrum methodology.
But let's face it, not all companies follow Scrum to the letter. When you join a new team or a project that already has its own habits and rhythms, it's not always easy to know which meetings to propose or attend, especially when some of them seem unproductive or irrelevant to your role.
I don't know about you, but for me it's been a real headache at times, teams that are agile but not totally, teams that are agile but in their own way, by jumping from one context to another.
I've created a list of meetings focused on QA to help manage this problem. The list explains the value of each meeting and who should ideally attend. If you're looking to improve visibility, structure your QA practice or avoid wasting time on unnecessary calls, this guide will help you find the right balance.
Strategy Meetings
To lay solid foundations, QA needs alignment from the very beginning.
Test Strategy Workshop Held at the start of a project or during a critical phase, this workshop defines the global QA approach. The QA Lead collaborates with the architect, developers, and product owner to align on objectives and methodology.
Automation Strategy Session This meeting defines the test automation roadmap. It usually happens at the beginning of a project, then every quarter to adjust direction. QA automation engineers and QA leads are the key participants.
Planning Meetings
Good planning ensures effective and timely testing.
Test Plan Review Organized at the start of each release or cycle, this meeting clarifies responsibilities, tools, and the testing scope. It brings together QA leads, testers, developers, and the product owner.
Security Testing Meeting Scheduled either quarterly or at each release, this optional session focuses on defining the scope of security tests with developers and QA security specialists.
Risk-Based Test Prioritization By identifying and prioritizing risks, QA can focus testing where it matters most. This meeting is especially useful early in a project or release.
Test Readiness Review Before each test campaign, the QA checks that all conditions are met to start testing: environments, data, test cases, etc.
UAT Planning Meeting Ahead of any User Acceptance Testing phase, QA, business representatives, and analysts prepare the test scenarios and acceptance workflows.
Analysis Meetings
These meetings are crucial to ensure requirements are clear, testable, and well understood.
Three Amigos Workshop For each new user story, a BA, a developer, and a QA engineer align their understanding and expectations. It helps prevent ambiguity from slipping into development.
Acceptance Criteria Workshop At the beginning of each sprint or story, this session clarifies the conditions of success for each feature. It aligns QA, developers, and product owners.
Impact Analysis Meeting When a significant change occurs, this meeting helps determine what existing tests must be updated or re-executed to avoid regressions.
Requirement Review Before development begins, QA, BAs, and product owners validate that the requirements are clear and testable.
Test Design Meetings
Designing tests is a creative and collaborative process.
Test Design Workshop Held at the start of a sprint or release, QA engineers work together to derive test cases directly from business requirements.
Internal QA Demo Before any client-facing demo, QA teams internally validate automated scripts and test coverage.
Test Data Preparation Session Whether synthetic or anonymized, good test data is essential. This recurring meeting helps QA and data engineers prepare the right datasets.
Execution & Coordination
Running tests often requires tight coordination across roles and tools.
DevOps Integration Sync Weekly or biweekly, this sync ensures QA and DevOps are aligned on CI/CD pipelines, environments, and automation tools.
Pair Testing When needed, testers pair up with developers or other QA colleagues to dig deeper and detect edge-case issues together.
User Experience Testing Although not always formalized, these ad hoc sessions evaluate the usability and user journey alongside UX and product teams.
Chaos Testing Session This meeting aims to simulate extreme scenarios to test system resilience. It may be scheduled per release or as a one-off.
QA Monitoring & Review
Tracking quality is just as important as building it.
QA and Support Sync This monthly or post-release meeting ensures QA is aware of production incidents and can adapt test coverage accordingly.
Quality Debt Review Held monthly, this meeting tracks tests that are outdated, missing, or not automated.
Bug Triage Whether weekly or as needed, this meeting ensures bugs are prioritized and assigned to the right team members efficiently.
KPI Review On a monthly basis, QA leads review key performance indicators to monitor progress and bottlenecks with management.
Compliance Review For teams in regulated sectors, this meeting ensures QA practices align with standards like ISO or GDPR.
Automated Script Review Scheduled every two to four weeks, it helps ensure the automation codebase remains clean, reliable, and maintainable.
Continuous Improvement
Great QA teams evolve through shared learning.
QA Bootcamp / Onboarding Every time a new QA joins, a tailored onboarding process helps them become productive and autonomous quickly.
Knowledge Sharing Session These monthly meetups are a great opportunity for QA engineers to share tools, methods, or post-mortems.
Setting up the right meetings outside of Scrum can make a big difference not just for QA, but for the whole team. The goal isn't to multiply meetings for the sake of it, but to make sure the right conversations happen at the right time, with the right people.
Whether you're full-time, freelance, or just getting started as a QA, having a clear idea of which meetings to push for can save you time, clarify your role, and strengthen your impact on the project.
If this list helps you structure your QA involvement better or if you think some key meetings are missing feel free to share your thoughts.