Complete Agile SDLC Documentation for a Personal Expense Dashboard Web Application

Operations, maintenance, support, and future Agile increments

Maintenance activity

After production deployment, the application enters controlled maintenance. Corrective, adaptive, preventive, and perfective changes return to the Agile backlog and follow the same sprint lifecycle when implementation is required.

Operational monitoring

• Application availability.
• Server and application errors.
• Authentication failures and suspicious patterns.
• Database health and storage.
• Dashboard response time.
• Backup job status.

Support priorities

• P1: Security incident, confirmed data loss, or complete application outage.
• P2: Core authentication, transaction, or budget functionality unavailable.
• P3: Partial functionality degraded with workaround available.
• P4: Minor defect or enhancement request.

Maintenance categories

• Corrective: repair production defects.
• Adaptive: update dependencies, infrastructure, supported browsers, or runtime configuration.
• Perfective: improve usability, analytics, maintainability, or performance.
• Preventive: refactoring, test expansion, dependency upgrades, backup validation, and security hardening.

Backup and recovery controls

• Run automated backups daily.
• Alert on failed backup jobs.
• Perform periodic restore tests.
• Record restore ownership and procedure in the operations runbook.

Maintenance change intake

1. Record the defect, enhancement, or operational improvement.
2. Classify priority and risk.
3. Product Owner adds approved work to the backlog.
4. Security-sensitive maintenance receives technical review.
5. Selected work follows the next Agile sprint cycle.

Examples of future backlog items

• CSV transaction import.
• Recurring transactions.
• Additional reporting periods.
• Exportable monthly reports.
• Shared household budgeting, subject to separate privacy and authorization design.