# MVP Work Plan

Optional working template for Module 5. Update your existing team issues, project board, and documentation; this does not add another graded submission. The MVP and recorded Project Showcase remain due in Module 6 at the time stated in Canvas. Complete the independent midterm assessment separately.

## One User Workflow

- Approved proposal goal:
- User action and starting state:
- Expected visible result:
- Related team issue:

## Interface And Ownership

| VM | Work needed | Teammate responsible | Related issue or PR |
| --- | --- | --- | --- |
| App | | | |
| MQ | | | |
| API, when used by this feature | | | |
| DB, when used by this feature | | | |

- Agreed request/reply contract or documentation link:
- Existing helper or service path to reuse:
- Data to transform or persist:

All internal VM-to-VM requests, results, status, and errors use RabbitMQ, including API-to-DB work. Administration access does not replace application messaging. Internal variable names are team choices unless a shared interface consumes them.

## Acceptance Checks

Write the outcome beside each check that applies to the workflow.

| Check | Expected result | Observed result or linked evidence |
| --- | --- | --- |
| Successful action | | |
| Reload or subsequent read, when persistence matters | | |
| Invalid input | | |
| Unauthorized access, when protected data is involved | | |
| Missing or late reply | | |
| External source unavailable, when used | | |

Use test data. Keep passwords, tokens, private keys, and sensitive session identifiers out of source, screenshots, and logs.

## Integration And Demo Readiness

- Reviewed team pull request(s):
- Logging and account behavior rechecked:
- Known limitation and related issue:
- Each member's concrete contribution and practice-demo speaking area:
- Next useful action and owner:

Link existing evidence instead of copying it into several records. Follow the assigned Module 6 MVP/showcase checklist for submission requirements, grading, and the recording link. Select work from the approved MVP stories and required admin CRUD slice; keep later proposal features in the final-demo scope.