Scribd
Upload
2 views

Manual_Testing_Agile_Test_Plan

This document outlines a Manual Testing Test Plan within an Agile Scrum framework, detailing objectives, scope, limitations, and effort estimation for QA activities. It specifies various test types, deliverables, and communication strategies to ensure effective collaboration and defect management. Additionally, it addresses risks and mitigation strategies to enhance the testing process throughout the software development life cycle.

Uploaded by

babu.s
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
2 views

Manual_Testing_Agile_Test_Plan

This document outlines a Manual Testing Test Plan within an Agile Scrum framework, detailing objectives, scope, limitations, and effort estimation for QA activities. It specifies various test types, deliverables, and communication strategies to ensure effective collaboration and defect management. Additionally, it addresses risks and mitigation strategies to enhance the testing process throughout the software development life cycle.

Uploaded by

babu.s
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

Manual Testing Test Plan in Agile Framework

Project Name: Manual Testing in Agile Product Development

Framework: Agile Scrum

Tool Stack: Jira, Confluence, TestRail / Zephyr, Excel / Google Sheets, Slack / Teams

---

1. Objective

To outline a detailed approach for conducting manual testing activities throughout the agile software

development life cycle (SDLC), ensuring early defect identification, continuous validation, and iterative quality

feedback.

---

2. Scope

- Functional, exploratory, regression, and smoke testing

- User story validation and acceptance testing

- Sprint-based test execution and bug tracking

- Manual test case management in TestRail/Zephyr

- Test coverage reporting and QA sign-off

---

3. Out of Scope

- Performance/load testing (handled by a separate team)

- Automation scripting and maintenance


- Non-functional security and penetration testing

---

4. Limitations

- Dependency on stable builds from development team

- Test coverage may be limited in early sprints

- Regression testing effort increases over time

---

5. Effort Estimation

Sprint Duration | QA Activities | Estimated Effort

------------------|--------------------------------------------------|------------------

Sprint Planning | Review stories, write high-level scenarios | 0.5 - 1 day

During Sprint | Test case writing, exploratory testing, bug logging | 3 - 4 days

Sprint Review | Demo support, QA sign-off, documentation | 1 day

Regression | Final sprint regression testing | 1 - 2 days

Total / Sprint | | 5 - 7 days

---

6. Test Strategy

- Begin with early story analysis and clarification

- Create test charters and acceptance criteria validation matrix

- Peer review and reuse of test scenarios across features

- Maintain traceability with Jira tickets and test cases


- Include exploratory sessions in every sprint

- Conduct daily sync-ups and test reporting via Slack or standups

---

7. Test Types

- Smoke Testing: Post-deployment checks for major builds

- Functional Testing: Based on acceptance criteria

- Regression Testing: Prior sprint features re-validation

- Exploratory Testing: Free-form testing to identify edge cases

- UAT Support: Assist product owners in user acceptance sessions

---

8. Test Deliverables

- Test case document (Excel/TestRail/Zephyr)

- Daily QA status update

- Sprint test summary reports

- Defect logs and triage sheets

- Release sign-off document

---

9. Sample Test Scenario

User Story: As a user, I should be able to login using valid credentials.

Test Cases:

1. Verify login with valid username and password


2. Verify login with invalid credentials

3. Validate error messages for blank fields

4. Validate session timeout

5. Check redirect to homepage post login

---

10. Communication & Collaboration

- Participate in sprint planning, daily stand-ups, retrospectives

- Log defects in Jira with clear reproduction steps

- Use Confluence to maintain QA documentation and known issues

- Collaborate with developers and POs via Slack or Microsoft Teams

---

11. Risks & Mitigation

Risk | Mitigation Strategy

--------------------------------------|---------------------------------------------

User stories without clear ACs | Collaborate with PO for clarification

Environment instability | Schedule buffer time, use test environments

Multiple builds close to release | Regression testing prioritization

---

12. Appendices

- Agile Testing Quadrants: https://www.agilealliance.org

- ISTQB Agile Extension: https://www.istqb.org/certification-path-root/agile-tester


- Jira Test Management Plugins: https://marketplace.atlassian.com

---

Prepared by: [Your Name]

Date: [Insert Date]

You might also like