Skip to content

[QA] session plan for module 3 week 3 #300

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
siderdk merged 1 commit into from
May 1, 2026
Merged

[QA] session plan for module 3 week 3 #300

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
31 changes: 8 additions & 23 deletions courses/qa/test-management/week3/session-plan.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,28 +1,13 @@
# Session Plan

> [!TIP]
> The session plan is written to guide the mentor to prepare and run the session. Of course, trainees may come across and read this material. But it should be written as if you're speaking to a mentor.
- Key QA Metrics - how to measure and keep track (45 mins)
- What QA metrics are and why they matter
- How to track metrics over time
- Reporting & Communication – Sharing QA Results Effectively (40 mins)
- Rout Cause Analysis - what is it and why it matters in QA (45 mins)
- Continuous Improvement & PDCA (Plan‑Do‑Check‑Act) (40 mins)
- Wrap‑Up & Next Steps (20 mins)

## Session Materials

> [!TIP]
> Previously used slides, docs or any other materials that future mentors could get value from should be listed here. If we don't have any (yet), this section can be removed.

These are some examples of previously created materials by mentors that you can use yourself, or for inspiration.

- [`Resource Name`, `@author`, `Team X`](https://example.com/)

## Session Outline

> [!TIP]
> Write a plan for the order of topics, points to cover, examples, timings, exercises and any other useful info to guide the session.

## Exercises

> [!TIP]
> Exercises might appear inside the Session Outline section if they are tightly integrated into the flow of the session. If you have more like a library of exercises that should be worked through in order, then you could also list them in a separate section here.

## Optional Exercises

> [!TIP]
> If you have some extra exercises that trainees can complete if they finish the rest, or want to push themselves, include them in this optional section.
In this session, trainees will learn how to measure QA effectiveness using key metrics and communicate testing progress clearly to stakeholders. We will cover common QA metrics for a feature, reporting best practices, and review all manual and automation topics covered so far. This week also includes planning for the final demo project, defining scope, and organizing teams.
Loading