Intake & validation
18 story points · 4 stories
- US-01 · Create loan application (5)
- US-02 · Submit loan application (5)
- US-03 · Validate mandatory fields (3)
- US-04 · View required documents (5)
Planned backlog · To Do
From manual application handling to a traceable digital loan journey: requirements, process redesign, sprint planning, and operational reporting.
A portfolio case study that connects business needs to practical delivery and reporting outputs.
The scope covers application capture, mandatory-field validation, document readiness, assignment, manual review, decision recording, notifications, audit history, and operational KPIs.
The final swimlane diagrams show the current manual process and the proposed digital workflow, including missing-information loops and approval or decline paths.
The BRD defines the business scope, functional requirements, business rules, and acceptance criteria. The story register translates these into a prioritized backlog.
| BRD reference | Requirement summary | Related stories |
|---|---|---|
| FR-01 | Create, save and submit applications | US-01 / US-02 |
| FR-02 | Validate mandatory details before submission | US-03 |
| FR-03 | Document checklist and readiness | US-04 |
| FR-04 | Assign and reassign loan officers | US-06 / US-07 |
| FR-05 | Request information and record decision reasons | US-05 / US-08 |
| FR-06 | View application and ownership history | US-11 |
| FR-07 | Operational KPI reporting | US-12 |
As a loan officer, I want to record an approval or decline decision so that the application has a clear outcome.
| Stakeholder | Responsibility | Influence | Interest |
|---|---|---|---|
| Lending Business Owner / Management | Approve business goals, prioritize requirements, and review outcomes | High | High |
| Loan Operations Team | Register applications, track documents, and follow up on missing information | High | High |
| Loan Officers | Validate information, assess applications, and record decisions | High | High |
| Lending Manager | Assign applications, resolve escalations, and monitor turnaround time | High | High |
| Risk / Credit Policy Representative | Validate rule definitions and review exceptions for the project scenario | High | Medium |
| Customer Service Team | Respond to enquiries, explain next steps, and coordinate applicant communication | Medium | High |
| Loan Applicants | Provide accurate information and complete requested actions | Medium | High |
| Business Analyst | Gather requirements, document the BRD, write user stories, and map workflows | High | High |
| Data Analyst | Clean data, analyze outcomes, and prepare Excel and Power BI reporting | Medium | High |
| System Administrator | Maintain user access, support configuration, and monitor system issues | Medium | Medium |
Eight epics and 12 user stories are organized into three planned sprints. Story points, priorities and acceptance criteria follow the project story register.
18 story points · 4 stories
Planned backlog · To Do
23 story points · 4 stories
Planned backlog · To Do
23 story points · 4 stories
Planned backlog · To Do
The supplied analysis dataset contains 120 applications and nine fields. Application IDs are unique; required values are present. The cleaning script documents type conversion, validation and controlled categories.
The supplied raw and clean CSV files contain the same records. This case does not claim a measured reduction in duplicates or errors.
| Field group | Example fields |
|---|---|
| Identifiers | Application_ID, Customer_ID |
| Application details | Submitted_Date, Requested_Amount_JOD, Term_Months |
| Profile and status | Employment_Type, Current_Status |
| Operational tracking | Turnaround_Days, Current_or_Decision_Reason |
Date · Month Year · Month SortSubmitted_DateRecorded duration is the supplied Turnaround_Days field. It includes open and closed cases and is not a pure decision-time measure.
The workbook includes applicant, status, decision, queue, loan-term and monthly trend analysis. Open the PDF to inspect all analysis pages.
This page filters the same 120-row CSV used in the project. It is a website preview, separate from Power BI Desktop.
Explicit ownership, information requests, and decision states make the next action easier to identify.
Designed benefit; not production-measured.
BRD requirements connect to user stories, acceptance criteria, workflow steps, and planned sprints.
Evidence: BRD, story register and Jira plan.
43 applications are Under Review or awaiting more information in the simulated dataset. Reporting makes this queue visible.
26 Under Review + 17 More Information Required.
Business need, scope, risks and expected benefits.
Roles, needs, responsibilities, influence and interest.
Business and functional requirements, rules and acceptance criteria.
12 prioritized stories across three sprints.
Final As-Is and To-Be diagrams and editable originals.
Epic structure, sprint plan, stories and implementation tasks.
Simulated source and cleaned application records.
Database setup, cleaning and ten analysis queries.
Workbook and full eight-page analysis export.
Final dashboard PDF and editable report.