Sprint 4 Retrospective

✅ What Went Well

• Completed and polished Login and Sign-Up flows, including “Forgot Password” / Password Recovery functionality.
• Implemented Transaction Categorization Automation, reducing manual tagging to near zero.
• Added Budget Limit Alerts that trigger notifications at 80% usage and upon budget overrun.
• Built Password Recovery email workflow with confirmation screens and custom templates.
• Enabled Export Reports in PDF and CSV formats directly from the UI.

🔍 What Could Be Improved

• Performance of large report generation can lag; consider background tasks or pagination.
• Styling Consistency across the new “alerts” and “exports” modals; subtle CSS mismatches remain.
• Documentation for deployment steps related to email SMTP settings and export modules.

📌 Action Items

1. Improve export error handling

   • Surface specific failure reasons (file format, network, permissions) in the UI.

2. Optimize report generation

   • Offload heavy export tasks to a background worker (Celery/RQ) and show progress indicators.

3. Expand automated tests

   • Add unit/integration tests for budget alerts edge cases and password-reset flows.

4. Polish UI components

   • Harmonize colors, spacing, and typography in alerts and export dialogs.

5. Document configuration

   • Create a “README-Email & Exports” section detailing mail server setup and export dependencies.

6. Schedule a UX review

   • Walk through the new features with a designer or product owner to catch any usability gaps.