Skip to content

Testing Schedule: E-Commerce Checkout System

Project: ShopFlow E-Commerce Platform - Checkout Module Enhancement
Version: 2.0
Prepared By: Sarah Johnson, Test Manager
Date: 2024-01-25
Last Updated: 2024-02-15
Status: In Progress - Sprint 2


Overview

This document provides comprehensive testing schedules for the ShopFlow Checkout Module Enhancement project, showing both Agile (Scrum) and Waterfall methodology approaches. The project follows Agile methodology with 2-week sprints.

Project Timeline: January 8, 2024 - April 3, 2024 (12 weeks)
Testing Duration: January 29, 2024 - April 1, 2024 (9 weeks)
Target Release Date: April 3, 2024


Table of Contents

  1. Agile Testing Schedule
  2. Waterfall Testing Schedule
  3. Resource Allocation
  4. Milestones and Dependencies
  5. Risk and Buffer Time

Agile Testing Schedule

High-Level Agile Timeline

Project Timeline (12 weeks):

Jan 8      Jan 15     Jan 29           Feb 12           Feb 26           Mar 11     Mar 18       Apr 1    Apr 3
  |----------|----------|----------------|----------------|----------------|----------|-----------|---------|-----|
  Planning   Test       Sprint 1         Sprint 2         Sprint 3         Regression  UAT Phase   Go Live
  (1 week)   Design     (2 weeks)        (2 weeks)        (2 weeks)        (1 week)    (2 weeks)   (1 day)
             (2 weeks)

Sprint-Based Testing Schedule

Sprint 0: Test Planning & Preparation (Jan 8 - Jan 29)

Dates: January 8 - January 29, 2024 (3 weeks)

Week Dates Activities Deliverables Owner Status
Week 1 Jan 8-12 Test Planning
- Review requirements
- Define test strategy
- Create test plan
- Risk assessment
- Test Plan v1.0
- Risk Matrix
Sarah Johnson ✅ Complete
Week 2 Jan 15-19 Test Design
- Design test cases
- Create test data specs
- Set up test management tool
- Review test cases
- Test cases (first 100)
- Test data requirements
Emily Rodriguez
David Kim
✅ Complete
Week 3 Jan 22-26 Environment Setup
- Provision test environment
- Configure test tools
- Load test data
- Smoke test environment
- Environment ready
- Test data loaded
- Test cases (complete 350)
James Wilson
Maria Garcia
✅ Complete
Week 3 Jan 27-29 Sprint 1 Planning
- Finalize Sprint 1 scope
- Assign test cases
- Prepare automation framework
- Sprint 1 test plan
- Automation framework
QA Team ✅ Complete

Key Milestone: ✅ Test Readiness Gate (Jan 29) - Environment validated, test cases ready


Sprint 1: Guest Checkout Foundation (Jan 29 - Feb 12)

Dates: January 29 - February 12, 2024 (2 weeks)
Theme: Guest checkout flow, user session management
User Stories: SHOP-1251, SHOP-1252, SHOP-1253, SHOP-1254

Week 1: Jan 29 - Feb 2
Day Date Activities Test Cases Resources Status
Mon Jan 29 Sprint Planning & Kickoff
- Sprint planning meeting (9-11 AM)
- Review Sprint 1 scope
- Test case assignment
- Environment smoke test
Smoke tests (15) Full team ✅ Complete
Tue Jan 30 Initial Testing
- Test guest checkout flow
- Test email validation
- Test session management
- Log defects
TC-CHK-001 to TC-CHK-015 Emily R.
David K.
Lisa P.
✅ Complete
2 defects found
Wed Jan 31 Continue Testing
- Test shipping address form
- Test address validation
- Test US and international addresses
- Exploratory testing session (2 hrs)
TC-CHK-016 to TC-CHK-030 Emily R.
David K.
Lisa P.
✅ Complete
3 defects found
Thu Feb 1 Integration Testing
- Test cart to checkout flow
- Test guest vs registered user paths
- Test session timeout
- Defect verification
TC-CHK-031 to TC-CHK-045 Emily R.
David K.
✅ Complete
1 defect found
Fri Feb 2 Regression & Automation
- Run regression suite (existing checkout)
- Update automation scripts
- Defect triage meeting (10 AM)
- Test report
Regression (50 cases)
Automation (20 scripts)
James W.
All testers
✅ Complete
Regression: Pass

Week 1 Summary: - Test Cases Executed: 95 - Pass: 88 (92.6%) - Fail: 7 (7.4%) - Defects Found: 6 (4 High, 2 Medium) - Automation: 20 scripts updated

Week 2: Feb 5 - Feb 9
Day Date Activities Test Cases Resources Status
Mon Feb 5 Defect Verification
- Verify fixed defects (DEF-001 to DEF-006)
- Retest failed test cases
- Continue integration testing
Retesting (15 cases)
TC-CHK-046 to TC-CHK-060
Emily R.
David K.
✅ Complete
5 verified, 1 reopened
Tue Feb 6 Cross-browser Testing
- Test on Chrome, Firefox, Safari, Edge
- Test on Windows and Mac
- Document browser-specific issues
Browser matrix (40 cases) Lisa P.
David K.
✅ Complete
2 defects found
Wed Feb 7 Mobile Testing
- Test on iPhone 13, 14
- Test on Samsung Galaxy S21, S22
- Test responsive design
- Test touch interactions
Mobile (30 cases) Lisa P. ✅ Complete
3 defects found
Thu Feb 8 Accessibility Testing
- Screen reader testing (JAWS, NVDA)
- Keyboard navigation
- Color contrast validation
- WCAG 2.1 compliance check
Accessibility (25 cases) Emily R.
Lisa P.
✅ Complete
4 defects found
Fri Feb 9 Sprint Review & Retrospective
- Demo to stakeholders (2-3 PM)
- Sprint retrospective (3-4 PM)
- Sprint 1 test report
- Sprint 2 planning prep
N/A Full team ✅ Complete

Week 2 Summary: - Test Cases Executed: 110 - Pass: 102 (92.7%) - Fail: 8 (7.3%) - Additional Defects: 9 (3 High, 5 Medium, 1 Low) - Sprint 1 Total Defects: 15

Sprint 1 Summary: - Total Test Cases Executed: 205 - Overall Pass Rate: 92.7% - Total Defects Found: 15 (7 High, 7 Medium, 1 Low) - Defects Fixed in Sprint: 12 - Defects Carried to Sprint 2: 3 - Sprint Goal Achievement: ✅ Met - Guest checkout functional


Sprint 2: Payment Gateway Integration (Feb 12 - Feb 26)

Dates: February 12 - February 26, 2024 (2 weeks)
Theme: PayPal, Apple Pay, Google Pay integration
User Stories: SHOP-1260, SHOP-1261, SHOP-1262, SHOP-1263, SHOP-1264

Week 1: Feb 12 - Feb 16
Day Date Activities Test Cases Resources Status
Mon Feb 12 Sprint Planning
- Sprint 2 planning (9-11 AM)
- Review payment integration scope
- Environment validation
- Payment sandbox setup check
Smoke tests (20) Full team ✅ Complete
Tue Feb 13 PayPal Integration Testing
- Test PayPal Express Checkout
- Test PayPal login flow
- Test payment success/failure scenarios
- Test redirect handling
TC-PAY-001 to TC-PAY-020 Emily R.
David K.
✅ Complete
3 defects found
Wed Feb 14 Apple Pay Testing
- Test Apple Pay on Safari
- Test Apple Pay on iPhone/iPad
- Test payment authorization
- Test payment cancellation
TC-PAY-021 to TC-PAY-035 Lisa P.
Emily R.
✅ Complete
2 defects found
Thu Feb 15 Google Pay Testing
- Test Google Pay on Chrome
- Test Google Pay on Android
- Test saved cards
- Test payment flows
TC-PAY-036 to TC-PAY-050 David K.
Lisa P.
✅ Complete
1 defect found
Fri Feb 16 Integration & Error Handling
- Test payment gateway timeouts
- Test network errors
- Test order creation on payment success
- Defect triage
TC-PAY-051 to TC-PAY-065 All testers ✅ Complete
2 defects found

Week 1 Summary: - Test Cases Executed: 85 - Pass: 77 (90.6%) - Fail: 8 (9.4%) - Defects Found: 8 (5 High, 3 Medium)

Week 2: Feb 19 - Feb 23
Day Date Activities Test Cases Resources Status
Mon Feb 19 Presidents' Day Holiday N/A N/A -
Tue Feb 20 Security Testing
- Payment data encryption verification
- PCI compliance checks
- SSL/TLS validation
- Sensitive data handling
Security (20 cases) Tom A.
Emily R.
✅ Complete
1 defect found
Wed Feb 21 Defect Verification
- Verify Sprint 2 fixes
- Retest payment flows
- Cross-browser payment testing
Retesting (30 cases) All testers ✅ Complete
Thu Feb 22 Performance Testing
- Payment processing time
- Load test payment gateways (100 concurrent)
- Response time validation
Performance (15 cases) Anna K. ✅ Complete
1 medium issue
Fri Feb 23 Sprint Review & Retrospective
- Demo payment integrations (2-3 PM)
- Sprint retrospective (3-4 PM)
- Sprint 2 test report
N/A Full team ✅ Complete

Week 2 Summary: - Test Cases Executed: 65 - Pass: 62 (95.4%) - Fail: 3 (4.6%) - Additional Defects: 2

Sprint 2 Summary: - Total Test Cases Executed: 150 - Overall Pass Rate: 93.3% - Total Defects Found: 10 (5 High, 4 Medium, 1 Low) - Defects Fixed in Sprint: 8 - Defects Carried to Sprint 3: 5 (including 3 from Sprint 1) - Sprint Goal Achievement: ✅ Met - All payment methods functional


Sprint 3: Mobile Optimization & Polish (Feb 26 - Mar 11)

Dates: February 26 - March 11, 2024 (2 weeks)
Theme: Mobile responsiveness, accessibility, final polish
User Stories: SHOP-1270, SHOP-1271, SHOP-1272, SHOP-1273

Week 1: Feb 26 - Mar 1
Day Date Activities Test Cases Resources Status
Mon Feb 26 Sprint Planning
- Sprint 3 planning (9-11 AM)
- Review mobile optimization scope
- Final feature review
Smoke tests (25) Full team ✅ Complete
Tue Feb 27 Comprehensive Mobile Testing
- Full checkout flow on iOS
- Full checkout flow on Android
- Touch gesture testing
- Virtual keyboard handling
Mobile (60 cases) Lisa P.
David K.
✅ Complete
4 defects found
Wed Feb 28 Accessibility Deep Dive
- ARIA labels validation
- Tab order testing
- Color contrast (WCAG AAA)
- Screen reader full flow
Accessibility (40 cases) Emily R.
Lisa P.
✅ Complete
2 defects found
Thu Feb 29 Usability Testing
- User flow analysis
- Error message clarity
- Tooltips and help text
- Loading indicators
Usability (30 cases) Emily R.
David K.
✅ Complete
3 defects found
Fri Mar 1 Full Regression Suite
- Execute complete regression (250 cases)
- Automated regression run
- Manual critical path testing
Regression (250 cases) All testers ✅ Complete
Pass rate: 96%

Week 1 Summary: - Test Cases Executed: 380 - Pass: 371 (97.6%) - Fail: 9 (2.4%) - Defects Found: 9 (2 High, 5 Medium, 2 Low)

Week 2: Mar 4 - Mar 8
Day Date Activities Test Cases Resources Status
Mon Mar 4 Defect Verification Marathon
- Verify all outstanding defects
- Retest all failed cases
- Cross-verification by different testers
Retesting (50 cases) All testers ✅ Complete
Tue Mar 5 Exploratory Testing
- Unscripted testing sessions
- Edge case discovery
- User journey mapping
- Negative testing
Exploratory Emily R.
David K.
Lisa P.
✅ Complete
2 defects found
Wed Mar 6 Integration Testing Complete Flow
- End-to-end checkout scenarios
- Multiple payment methods
- International scenarios
- Promotional codes
Integration (45 cases) All testers ✅ Complete
1 defect found
Thu Mar 7 Final Smoke Tests
- Smoke test all features
- Browser compatibility sweep
- Mobile device testing
- Prepare for feature freeze
Smoke (50 cases) All testers ✅ Complete
Fri Mar 8 Sprint Review & Retrospective
- Demo polished features (2-3 PM)
- Sprint retrospective (3-4 PM)
- Sprint 3 test report
- Regression planning
N/A Full team ✅ Complete

Week 2 Summary: - Test Cases Executed: 145 - Pass: 143 (98.6%) - Fail: 2 (1.4%) - Additional Defects: 3

Sprint 3 Summary: - Total Test Cases Executed: 525 - Overall Pass Rate: 98.1% - Total Defects Found: 12 (2 High, 5 Medium, 5 Low) - All Defects Resolved: ✅ Yes - Sprint Goal Achievement: ✅ Met - Mobile optimized, WCAG compliant

Feature Freeze: March 11, 2024 - No new features after this date


Regression & Hardening Sprint (Mar 11 - Mar 18)

Dates: March 11 - March 18, 2024 (1 week)
Focus: Full regression, performance, security validation

Day Date Activities Owner Status
Mon Mar 11 Full Regression Start
- Complete automated regression (180 cases)
- Manual regression critical paths (70 cases)
- Feature freeze enforced
All testers ✅ Complete
Tue Mar 12 Performance Testing
- Load testing (1,000 concurrent users)
- Stress testing (2,000 concurrent users)
- Checkout flow performance validation
- Database query performance
Anna K.
DevOps
✅ Complete
Pass
Wed Mar 13 Security Audit
- External security audit begins
- Penetration testing
- Vulnerability scanning
- OWASP ZAP automated scan
Tom A.
External auditor
✅ Complete
Thu Mar 14 Security Remediation
- Address audit findings
- Verify security fixes
- Re-test security scenarios
- Documentation review
Tom A.
Dev team
✅ Complete
Fri Mar 15 Final Regression & Sign-off
- Final regression pass (250 cases)
- Sign-off from QA
- UAT environment preparation
- UAT kickoff meeting (3 PM)
All testers ✅ Complete
QA Sign-off

Regression Summary: - Total Regression Cases: 250 - Pass Rate: 98.8% (247 passed, 3 minor issues) - Performance: All targets met ✅ - Security: No critical vulnerabilities ✅ - QA Approval: ✅ Approved for UAT


UAT (User Acceptance Testing) (Mar 18 - Apr 1)

Dates: March 18 - April 1, 2024 (2 weeks)
Participants: Business stakeholders, product owners, select customers

Week 1: Mar 18 - Mar 22
Day Date Activities Participants Status
Mon Mar 18 UAT Kickoff
- UAT training session (10 AM-12 PM)
- Environment walkthrough
- Test script distribution
- Begin UAT testing
Product Owner
Business Analyst
Marketing
✅ Complete
Tue-Thu Mar 19-21 UAT Testing
- Business stakeholders execute test scenarios
- QA support available
- Issue tracking and triage
- Daily UAT stand-ups (9 AM)
All stakeholders
QA support
In Progress
Fri Mar 22 Mid-UAT Review
- Review progress (2 PM)
- Address blockers
- Adjust test coverage as needed
Product Owner
Test Manager
Planned
Week 2: Mar 25 - Mar 29
Day Date Activities Participants Status
Mon-Wed Mar 25-27 Continued UAT Testing
- Complete remaining scenarios
- Exploratory testing by stakeholders
- Real-world scenario validation
All stakeholders
QA support
Planned
Thu Mar 28 UAT Defect Resolution
- Fix critical UAT findings
- Verify fixes with stakeholders
- Final scenario validation
Dev team
QA team
Stakeholders
Planned
Fri Mar 29 UAT Close-out
- Final UAT report
- Stakeholder sign-off
- Go/No-Go meeting preparation
Product Owner
Test Manager
Planned
Final Week: Apr 1
Day Date Activities Participants Status
Mon Apr 1 Go/No-Go Decision
- Executive review meeting (10 AM)
- Final risk assessment
- Production deployment approval
- Release notes finalization
Executives
PMO
Test Manager
Dev Manager
Planned

UAT Success Criteria: - 95%+ of UAT scenarios pass - Zero critical defects open - All high-severity defects resolved or accepted - Business stakeholder sign-off - Production readiness confirmed


Production Release (Apr 2-3)

Dates: April 2-3, 2024

Day Date Activities Owner Status
Tue Apr 2 Pre-Deployment
- Final production environment checks
- Deployment runbook review
- Rollback plan validation
- Team on-call schedule
DevOps
QA
Dev
Planned
Wed Apr 3 Deployment & Go-Live
- Deploy to production (6 AM)
- Smoke test production (7-9 AM)
- Monitor initial traffic
- Canary release (10% traffic)
- Full release (12 PM)
DevOps
QA
Support
Planned

Waterfall Testing Schedule (Alternative)

For comparison, here is how this project would be scheduled using Waterfall methodology:

Waterfall Phase Timeline

Project Timeline (20 weeks):

Jan 1        Feb 1         Mar 1          Apr 1          May 1          Jun 1
  |------------|-------------|--------------|--------------|--------------|-----------|
  Requirements  Design        Development    Testing        UAT          Production
  (3 weeks)    (4 weeks)     (8 weeks)      (3 weeks)      (1 week)     (1 week)

Detailed Waterfall Schedule

Phase 1: Requirements (3 weeks) - Jan 1-19

Week Dates Activities Deliverables
1-2 Jan 1-12 Requirements gathering, analysis BRD, requirements doc
3 Jan 15-19 Requirements review, approval, sign-off Approved requirements

Phase 2: Design (4 weeks) - Jan 22 - Feb 16

Week Dates Activities Deliverables
4-5 Jan 22 - Feb 2 Technical design, architecture Technical design doc
6-7 Feb 5-16 UI/UX design, database design UI mockups, DB schema

Phase 3: Test Planning (2 weeks) - Feb 19 - Mar 1

Week Dates Activities Deliverables Owner
8 Feb 19-23 Test plan creation, strategy definition, resource planning Test Plan v1.0, Test Strategy Test Manager
9 Feb 26 - Mar 1 Test case design (all 350 cases), test data preparation, test environment planning Complete test suite, Test data specs QA Team

Phase 4: Development (8 weeks) - Mar 4 - Apr 26

Week Dates Development Activities Parallel Testing Activities
10-11 Mar 4-15 Guest checkout development Test case review, environment setup
12-13 Mar 18-29 Payment integration development Test automation script development
14-15 Apr 1-12 Mobile optimization development Test environment validation, test data loading
16-17 Apr 15-26 Bug fixes, code review, final development Smoke test preparation, automation completion

Phase 5: Testing (3 weeks) - Apr 29 - May 17

Week 1: System Testing (Apr 29 - May 3)
Day Activities Test Cases Resources
Mon-Tue Smoke testing, setup validation 50 cases Full QA team
Wed-Fri Functional testing - all features 150 cases Full QA team
Week 2: Integration & Regression (May 6-10)
Day Activities Test Cases Resources
Mon-Tue Integration testing - payment gateways, shipping APIs 75 cases Full QA team
Wed-Thu Regression testing - existing features 250 cases Full QA team
Fri Performance and security testing 25 cases Specialist testers
Week 3: Defect Resolution & Retest (May 13-17)
Day Activities Test Cases Resources
Mon-Wed Defect fixing, verification, retesting 100+ cases Dev + QA teams
Thu Final regression run 250 cases Full QA team
Fri Test closure, QA sign-off, test report - Test Manager

Phase 6: UAT (1 week) - May 20-24

Day Activities Participants
Mon UAT training and kickoff Business stakeholders
Tue-Thu UAT execution Business stakeholders + QA support
Fri UAT sign-off, Go/No-Go decision Executives, PMO

Phase 7: Production Release (1 week) - May 27-31

Day Activities Owner
Mon-Tue Final production preparation DevOps + QA
Wed Production deployment DevOps
Thu-Fri Post-deployment validation, monitoring QA + Support

Waterfall vs Agile Comparison

Aspect Agile (Actual) Waterfall (Hypothetical)
Total Duration 12 weeks 20 weeks
Testing Start Week 4 (parallel with dev) Week 18 (after dev complete)
Feedback Loops Every 2 weeks (sprint reviews) After all development (UAT)
Flexibility High - can adjust each sprint Low - changes require formal change control
Risk Detection Early and continuous Late (during testing phase)
Deployment Single release after 3 sprints Single release after all phases
Stakeholder Involvement Continuous (every sprint) Bookends (requirements + UAT)
Documentation Lightweight, iterative Comprehensive upfront

Resource Allocation

Team Capacity by Week

Week Dates Sprint/Phase Available Resources (Person-Days)
1 Jan 8-12 Planning 35 (7 people × 5 days)
2-3 Jan 15-26 Test Design 70 (7 people × 10 days)
4-5 Jan 29 - Feb 9 Sprint 1 70 (7 people × 10 days)
6-7 Feb 12-23 Sprint 2 63 (7 people × 9 days, 1 holiday)
8-9 Feb 26 - Mar 8 Sprint 3 70 (7 people × 10 days)
10 Mar 11-15 Regression 35 (7 people × 5 days)
11-12 Mar 18-29 UAT 21 (3 people × 7 days, support only)
13 Apr 1-5 Release 35 (7 people × 5 days)

Total Testing Effort: 469 person-days

Resource Allocation by Role

Role Person Allocation % Activities
Test Manager Sarah Johnson 100% Planning, coordination, reporting, stakeholder communication
QA Lead Michael Chen 100% Test design oversight, defect triage, technical leadership
Sr. Test Engineer Emily Rodriguez 100% Test execution, test design, complex scenario testing
Test Engineer David Kim 100% Test execution, defect logging, regression testing
Test Engineer Lisa Patel 100% Mobile testing, cross-browser testing, accessibility testing
Automation Engineer James Wilson 100% Test automation, framework development, CI/CD integration
Performance Tester Anna Kowalski 50% Performance testing, load testing (shared with other projects)
Security Tester Tom Anderson 25% Security testing, compliance validation (shared)

Milestones and Dependencies

Critical Milestones

Milestone Date Criteria Status Risk
M1: Test Readiness Jan 29 Environment ready, test cases complete, test data loaded ✅ Complete Low
M2: Sprint 1 Complete Feb 12 Guest checkout functional, <5 open defects ✅ Complete Low
M3: Sprint 2 Complete Feb 26 Payment methods functional, security validated ✅ Complete Low
M4: Sprint 3 Complete Mar 11 Mobile optimized, accessibility compliant ✅ Complete Low
M5: Feature Freeze Mar 11 No new features, regression ready ✅ Complete Low
M6: QA Sign-off Mar 15 All testing complete, <2 open issues ✅ Complete Low
M7: UAT Sign-off Apr 1 Business approval, ready for production Planned Medium
M8: Production Go-Live Apr 3 Successful deployment, monitoring established Planned Medium

Dependencies

Dependency Type Impact Mitigation
Payment Gateway Sandbox Access External High - Blocks payment testing Early setup, backup test accounts
Test Environment Availability Internal Critical - Blocks all testing Environment provisioned early, monitoring
Development Sprint Completion Internal High - Delays testing Buffer time, parallel testing where possible
Security Audit Scheduling External Medium - Affects release date Booked auditor early, flexible dates
UAT Participant Availability External Medium - Delays sign-off Early calendar holds, remote options
Production Deployment Window Internal High - Affects go-live date Pre-approved deployment window

Risk and Buffer Time

Schedule Buffers

Phase Planned Duration Buffer Time Total
Test Planning 1 week 0.5 weeks 1.5 weeks
Test Design 2 weeks 0.5 weeks 2.5 weeks
Sprint Testing (3 sprints) 6 weeks 1 week 7 weeks
Regression 1 week 0.5 weeks 1.5 weeks
UAT 2 weeks 0.5 weeks 2.5 weeks
Total 12 weeks 3 weeks 15 weeks

Note: Current schedule has 3 weeks of buffer distributed across phases. Used judiciously for unexpected issues.

Schedule Risks

Risk Probability Impact Contingency
Development delays Medium High Parallel testing, reduced scope
Environment instability Low Medium Backup environment, quick restoration
Extended defect fixing Medium High Prioritize critical defects, defer minor issues
UAT delays Medium Medium Flexible UAT windows, remote participation
Security audit delays Low Critical Pre-audit preparation, expedited audit option

Appendix: Testing Metrics

Weekly Test Execution Progress

Week Test Cases Executed Pass Rate Defects Found Cumulative Coverage
1 (Sprint 0) 15 (smoke) 100% 0 -
2-3 (Sprint 0) - - - Test design phase
4 (Sprint 1 W1) 95 92.6% 6 27%
5 (Sprint 1 W2) 110 92.7% 9 59%
6 (Sprint 2 W1) 85 90.6% 8 83%
7 (Sprint 2 W2) 65 95.4% 2 102%
8 (Sprint 3 W1) 380 97.6% 9 211%
9 (Sprint 3 W2) 145 98.6% 3 252%
10 (Regression) 250 98.8% 3 324%

Note: Cumulative coverage >100% due to retesting and regression cycles

Defect Trend

Defects Found Per Week:

Week 4 (Sprint 1 W1): ██████ 6 defects
Week 5 (Sprint 1 W2): █████████ 9 defects
Week 6 (Sprint 2 W1): ████████ 8 defects
Week 7 (Sprint 2 W2): ██ 2 defects
Week 8 (Sprint 3 W1): █████████ 9 defects
Week 9 (Sprint 3 W2): ███ 3 defects
Week 10 (Regression): ███ 3 defects

Total Defects: 40
Fixed: 37 (92.5%)
Open: 3 (7.5%) - all low priority

Document End

Last Updated: February 15, 2024
Next Review: Weekly during sprint planning
Document Owner: Sarah Johnson, Test Manager