13. Implementation backlog
| Epic | File |
|---|---|
| 1. Identity and access | 13.1 |
| 2. Borrower onboarding | 13.2 |
| 3. KYB / KYC | 13.3 |
| 4. Application | 13.4 |
| 5. Data ingestion | 13.5 |
| 6. Underwriting | 13.6 |
| 7. Offer / sanction | 13.7 |
| 8. Documentation | 13.8 |
| 9. Disbursement | 13.9 |
| 10. LMS | 13.10 |
| 11. Collections | 13.11 |
| 12. Co-lending | 13.12 |
| 13. Partner portal | 13.13 |
| 14. DSA / CA portal | 13.14 |
| 15. Reporting | 13.15 |
| 16. Compliance | 13.16 |
| 17. Accounting | 13.17 |
| 18. Vendor integrations | 13.18 |
| 19. Analytics | 13.19 |
| 20. Security | 13.20 |
| 21. Audit | 13.21 |
Format per epic
Section titled “Format per epic”- User stories (3 – 8 representative; full library lives in the actual sprint planning tool).
- API requirements (key endpoints).
- Data model requirements (key tables / events).
- UI screens (key screens).
- Backend services (which module).
- External integrations (vendor list).
- Test cases (representative).
- Edge cases (top 5 – 10).
- Acceptance criteria (when done).
Sizing
Section titled “Sizing”These epics are scoped as multi-sprint efforts, not single sprints. Each epic represents 4 – 16 weeks of engineering depending on team size and phase.