Update Module 3 and weeks readme.md

Author: GayathriVenkatraman

courses/qa/test-management/README.md

@@ -1,27 +1,24 @@
-# `Module Name`
+# TEST MANAGEMENT
 
-This module is about `description goes here`
+Here you can find course content and assignments for the Practical Test Planning, Agile & Project Management module. This module focuses on applying QA skills in an Agile environment, emphasizing effective planning, documentation, and communication for regular QA work. (Management focus and specific Test Management tools have been removed.)
 
 ## Contents
 
-| Week | Topic                                | Preparation                           | Session Plan                                          | Assignment                          |
-| ---- | ------------------------------------ | ------------------------------------- | ----------------------------------------------------- | ----------------------------------- |
-| 1.   | [`Session Title`](./week1/README.md) | [Preparation](./week1/preparation.md) | [Session Plan](./week1/session-plan.md) (for mentors) | [Assignment](./week1/assignment.md) |
+| Week | Topic                                     | Preparation                         | Assignment                        | Session Plan                          |
+| ---- | ----------------------------------------- | ----------------------------------- | --------------------------------- | ------------------------------------- |
+| 1.   | Test Planning, Strategy & Scope           | [Preparation](week1/preparation.md) | [Assignment](week1/assignment.md) | [Session Plan](week1/session-plan.md) |
+| 2.   | Agile Testing & Working with User Stories | [Preparation](week2/preparation.md) | [Assignment](week2/assignment.md) | [Session Plan](week2/session-plan.md) |
+| 3.   | QA Metrics, Reporting & Demo Project Prep | [Preparation](week3/preparation.md) | [Assignment](week3/assignment.md) | [Session Plan](week3/session-plan.md) |
 
 ## Module Learning Goals
 
-> [!TIP]
-> Learning goals should be a list of outcomes, rather than a list of topics. For example, instead of "Synchronous vs Asynchronous", write something like "Explain the difference between sync and async code execution in JavaScript"
-
 By the end of this module, you will be able to:
 
-- [ ] `[action verb] [specific skill/knowledge]`
-
-## Prerequisites
-
-> [!TIP]
-> Some modules build on the learning goals of other modules. If that is the case, link them below. If there are no prerequesites, feel free to remove this section. Note that it is assumed that all foundation modules are a prerequisite of a specialisation course and its modules, so in that case you don't have to write them all out here :-)
-
-You should have completed or understand the learning goals in the following modules before proceeding:
-
-- [`Module Name`](https://example.com)
+- [ ] Understand the purpose and structure of a Test Plan and Test Strategy.
+- [ ] Define scope, objectives, risks, and environments for testing.
+- [ ] Apply practical test case management (grouping, linking, status updates).
+- [ ] Implement requirement traceability (requirements → test cases → bugs).
+- [ ] Understand Agile principles, Scrum roles, artifacts, and ceremonies.
+- [ ] Analyze User Stories and Acceptance Criteria to create effective test cases.
+- [ ] Track QA progress and communicate status effectively using QA metrics.
+- [ ] Prepare for a demo project by planning scope and team responsibilities.

courses/qa/test-management/week1/README.md

@@ -1,6 +1,6 @@
-# `Session Name` (Week `X`)
+# TEST MANAGEMENT, Week 1
 
-This session is about `description goes here`
+In this session, trainees will learn how to create effective test plans and strategies for real-world projects. We will cover the purpose of a Test Plan and Test Strategy, key sections such as scope, objectives, risks, and test environments, and practical test case management techniques. This week also introduces requirement traceability to ensure complete coverage from requirements to test cases and defects.
 
 ## Contents
 
@@ -10,9 +10,10 @@ This session is about `description goes here`
 
 ## Session Learning Goals
 
-> [!TIP]
-> Learning goals specific to this session. These should be a subset of the module's learning goals, and expanded on in more detail if possible.
-
 By the end of this session, you will be able to:
 
-- [ ] `[action verb] [specific skill/knowledge]`
+- [ ] Understand the purpose and importance of a Test Plan and Test Strategy.
+- [ ] Identify key sections of a Test Plan: scope, objectives, risks, and environments.
+- [ ] Apply practical test case management techniques (grouping, linking, status updates).
+- [ ] Implement requirement traceability (requirements → test cases → bugs).
+- [ ] Draft a practical Test Plan for a new feature and define the testing scope.

courses/qa/test-management/week2/README.md

@@ -1,6 +1,6 @@
-# `Session Name` (Week `X`)
+# TEST MANAGEMENT, Week 2
 
-This session is about `description goes here`
+In this session, trainees will learn how QA integrates into Agile development processes. We will cover Agile principles, Scrum roles, artifacts, and ceremonies, and explore QA’s responsibilities during sprint planning and estimation. This week emphasizes analyzing User Stories and Acceptance Criteria (AC) to create effective test cases and maintaining continuous testing and feedback throughout the sprint.
 
 ## Contents
 
@@ -10,9 +10,11 @@ This session is about `description goes here`
 
 ## Session Learning Goals
 
-> [!TIP]
-> Learning goals specific to this session. These should be a subset of the module's learning goals, and expanded on in more detail if possible.
-
 By the end of this session, you will be able to:
 
-- [ ] `[action verb] [specific skill/knowledge]`
+- [ ] Understand Agile principles and Scrum framework (roles, artifacts, ceremonies).
+- [ ] Identify QA’s role in Agile teams, including sprint planning and estimation.
+- [ ] Analyze User Stories and Acceptance Criteria to derive test scenarios.
+- [ ] Create detailed manual test cases based on ACs.
+- [ ] Track test case status during a simulated sprint.
+- [ ] Apply continuous testing and feedback practices in Agile workflows.

courses/qa/test-management/week3/README.md

@@ -1,6 +1,6 @@
-# `Session Name` (Week `X`)
+# TEST MANAGEMENT, Week 3
 
-This session is about `description goes here`
+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.
 
 ## Contents
 
@@ -10,9 +10,19 @@ This session is about `description goes here`
 
 ## Session Learning Goals
 
-> [!TIP]
-> Learning goals specific to this session. These should be a subset of the module's learning goals, and expanded on in more detail if possible.
-
 By the end of this session, you will be able to:
 
-- [ ] `[action verb] [specific skill/knowledge]`
+- [ ] Understand common QA metrics:
+  - [ ] Test coverage
+  - [ ] Pass/fail rate
+  - [ ] Defect density
+- [ ] Create clear QA status reports and communicate progress effectively.
+- [ ] Review manual and automation concepts from previous modules.
+- [ ] Define demo project scope and team responsibilities.
+- [ ] Prepare a QA metrics sheet and reporting template for real-world use.
+- [ ] Plan and set up teams for the final project.
+
+## Hands-on Activity
+
+- [ ] Create a QA status report and metrics sheet for a past week’s testing.
+- [ ] Collaborate with peers to plan demo project scope and team setup.