09 — Delivery Plan, Team and Commercial Notes
Source: proposal §6–7. All figures are preliminary estimates to be re-confirmed with the university after scope, integrations, data volume and the go-live plan are fixed.
Timeline: 10 months, overlapping phases
The text says "5 main phases" but the table lists 6:
| Phase | Months | Activities | Output |
|---|---|---|---|
| 1. Requirement Analysis | 1–4 | Gather, analyse and confirm requirements for all 12 modules; study central, campus and school processes | Requirement Specification and confirmed workflows, delivered per module |
| 2. UX/UI & System Design | 1–5 | UX/UI, prototype, system architecture, data model, per module as it becomes ready | Prototype, system design, data model |
| 3. System Development | 3–8 | Build modules by priority, several in parallel, with cross-module data links | Modules ready for testing |
| 4. QA & Integration Testing | 4–9 | Functional, integration and security testing; continuous fixing | Test results; system passes criteria |
| 5. UAT & Training | 8–10 | UAT with users, fixes, manuals, training | UAT sign-off, manuals, trained users |
| 6. Deployment & Go-live | 10 | Install, migrate data, go live, early support | Live system plus post-go-live support |
Modules whose requirements and design are confirmed start development first. The schedule may shift with data readiness and external-system readiness.
Phase priority (from §1.1): core education → mobile/web services → finance and scholarships → external integrations → AI.
Team (22 people)
| Role | Count | Responsibility |
|---|---|---|
| Project Manager | 1 | Plan, resources, risk, client liaison |
| Business Analyst | 3 | Requirements, process design, specs, UAT support |
| UX/UI Designer | 2 | Web, mobile and backoffice UX |
| Frontend Developer | 4 | Web app, dashboard, backoffice, mobile app |
| Backend Developer | 6 | API, business logic, database, integrations |
| QA | 3 | Test planning, defects, UAT support |
| Solution Architect / Tech Lead | 1 | Architecture, technical standards, quality |
| DevOps Engineer | 1 | Environments, CI/CD, deployment, monitoring |
| Data / AI Engineer | 1 | Data management and integration, AI features |
Success factors
- Clear scope: requirements and per-module priority confirmed before development.
- User availability: representatives from central office, campuses and schools join requirements and testing.
- Access to integration details for external systems (there is no legacy system to migrate).
- Timely decisions by named owners.
- Change-request control to protect schedule and scope.
Budget and commercial model
[unknown]. Proposal §7 has not been written for TNSU yet. Its current content is leftover template text from another project, so ignore it.
Releases
The use cases mention R1 (first release) and some items deferred from it: automatic cross-campus admission clearing is out of R1 (D-06), and the sports-science LAB moves to a separate contract from 2574 (D-06, REL-09). The full release plan is in the team's documents, not in this repo. See 12-use-cases.md.