Here are some useful abbreviations and frameworks related to QA, Agile, and Team Management, including WWW (Work, When, and Why):
1. WWW – Work, When, and Why
-
Work – What needs to be done? (Scope & tasks)
-
When – What is the timeline? (Deadlines & priorities)
-
Why – Why is this task important? (Impact & goals)
Example in QA:
Before starting automation, ask:
📌 Work – Automate regression suite for APIs.
📌 When – Must be ready before the next release.
📌 Why – Reduces manual effort and speeds up testing.
2. SMART – Goal-Setting Framework
-
S – Specific (Clearly defined objective)
-
M – Measurable (How will success be tracked?)
-
A – Achievable (Is it realistic?)
-
R – Relevant (Does it align with business goals?)
-
T – Time-bound (Deadline?)
Example in QA:
✔️ Goal: Automate 80% of regression tests within 3 months.
3. INVEST – Writing Good User Stories
-
I – Independent (Self-contained)
-
N – Negotiable (Can be refined)
-
V – Valuable (Delivers business value)
-
E – Estimable (Can be sized)
-
S – Small (Fits in one sprint)
-
T – Testable (Clear acceptance criteria)
Example User Story:
✔️ As a user, I should be able to reset my password so that I can regain access to my account.
4. FURPS – Quality Attributes of a Product
-
F – Functionality (Features & correctness)
-
U – Usability (User experience)
-
R – Reliability (Uptime & stability)
-
P – Performance (Speed & responsiveness)
-
S – Supportability (Maintainability & scalability)
5. MoSCoW – Prioritization Method
-
M – Must have (Critical for release)
-
S – Should have (Important but not critical)
-
C – Could have (Nice to have)
-
W – Won’t have (Not planned for now)
Example in Testing:
📌 Must-have: API tests for core functionality.
📌 Should-have: Performance tests.
📌 Could-have: UI test automation.
📌 Won’t-have: Cross-browser testing for MVP.
6. RACI – Role Responsibility Matrix
-
R – Responsible (Does the work)
-
A – Accountable (Final decision-maker)
-
C – Consulted (Provides input)
-
I – Informed (Needs updates)
Example in a QA Team:
✔️ QA Engineers → Responsible for writing test cases.
✔️ Test Lead → Accountable for test strategy.
✔️ Developers → Consulted for technical feasibility.
✔️ Stakeholders → Informed about test progress.
7. DOR & DOD – Definition of Ready & Done
-
Definition of Ready (DOR) – When a task is clear enough to be worked on.
-
Definition of Done (DOD) – When a task is considered completed.
Example in Testing:
✔️ DOR: User story has clear acceptance criteria and test data.
✔️ DOD: Test cases are automated, executed, and defects are fixed.
8. PDCA – Continuous Improvement Cycle
-
P – Plan (Define objectives)
-
D – Do (Execute)
-
C – Check (Analyze results)
-
A – Act (Implement improvements)
Example in QA:
✔️ Plan: Identify flaky tests.
✔️ Do: Fix locators.
✔️ Check: Monitor failure rate.
✔️ Act: Remove unstable scripts.
9. SHIFT LEFT – Early Testing Approach
-
Shift Left means testing earlier in the development lifecycle to catch defects sooner.
-
Example: QA participates in code reviews & writes unit tests with Devs.
10. 3 Amigos – Collaboration in Agile
-
BA (Business Analyst) – Defines requirements.
-
Dev (Developer) – Builds the feature.
-
QA (Tester) – Ensures it works as expected.
Example: Before development, the 3 Amigos discuss scenarios to avoid misunderstandings.
No comments:
Post a Comment