CashLine ERP MVP Production WBS Plan
Work Breakdown Structure for controlled production MVP delivery, including governance, hosting, deployment, database, QA, staging, production cutover, hypercare, and wider rollout work packages.
Development -> QA -> Staging/Pre-production -> Controlled Production MVP -> Stabilization -> Wider rollout
CashLine ERP MVP Production WBS Plan
Document date: 2026-04-20
Document status: Controlled production MVP work breakdown structure baseline
Prepared for: Project sponsor, project manager, technical lead, business analysis, QA, implementation, operations, and release governance
Project start date: Tuesday, 21 Apr 2026
Project finish date: Wednesday, 03 Jun 2026
Release path:
Development -> QA -> Staging/Pre-production -> Controlled Production MVP -> Stabilization -> Wider rollout
---
1. Executive Summary
This Work Breakdown Structure plan decomposes the CashLine ERP controlled production MVP into manageable work packages. It is designed to support planning, ownership, tracking, dependency management, testing, deployment, production readiness, backup/recovery, hypercare, and wider-rollout decision-making.
The WBS aligns with the MVP Production Project Charter and supports the 32-business-day critical path from Tuesday, 21 Apr 2026 to Wednesday, 03 Jun 2026.
2. WBS Ownership Summary
| Role | Name | Primary WBS Responsibility |
|---|---|---|
| Project Sponsor | Khalid Gabr | Approval, scope authority, production go/no-go, wider-rollout decision |
| Project Manager | Mostafa El Shahawy | Project coordination, schedule, governance, risk, communication, release control |
| Technical Lead | Nour Elsiminy | Hosting, deployment, database, technical readiness, backup/recovery, support |
| Business Analysis | Doaa Sabry | Requirements validation, UAT, user journeys, business sign-off support |
| Technical team | Technical Support / Engineering | Build, configuration, bug fixing, performance, release execution |
| Implementation team | Customer Service / Enablement | Training, user onboarding, field support, hypercare assistance |
3. WBS Level 1 Summary
| WBS | Workstream | Objective |
|---|---|---|
| 1.0 | Project governance | Authorize, control, and communicate the MVP production project |
| 2.0 | Hosting and infrastructure | Prepare Cloudflare and Azure target hosting stack |
| 3.0 | Deployment pipeline | Prepare repeatable build, package, release, and approval flow |
| 4.0 | Database and data loading | Prepare migrations, seed data, test data, and production data rules |
| 5.0 | Testing and QA | Validate functional, API, UI, workflow, access, reporting, and desktop behavior |
| 6.0 | Staging/UAT | Rehearse production deployment and obtain business sign-off |
| 7.0 | Production cutover | Deploy the controlled production MVP and activate approved users |
| 8.0 | Hypercare and stabilization | Monitor, support, triage, and stabilize production MVP usage |
| 9.0 | Wider rollout decision | Decide whether to expand beyond controlled MVP |
4. Detailed WBS
4.1 WBS 1.0 Project Governance
| WBS ID | Work Package | Description | Owner | Key Output |
|---|---|---|---|---|
| 1.1 | Charter approval | Approve project charter, roles, timeline, and release authority | Project Sponsor / Project Manager | Approved charter |
| 1.2 | Scope freeze | Confirm MVP scope, exclusions, and deferred items | Project Manager / Business Analysis | Frozen MVP scope |
| 1.3 | Governance cadence | Establish daily/weekly project review rhythm | Project Manager | Governance calendar |
| 1.4 | Risk and issue control | Track risks, blockers, decisions, and escalations | Project Manager | Risk and issue log |
| 1.5 | Change control | Route scope, timeline, cost, and readiness changes through approval | Project Manager | Change register |
4.2 WBS 2.0 Hosting And Infrastructure
| WBS ID | Work Package | Description | Owner | Key Output |
|---|---|---|---|---|
| 2.1 | Cloudflare setup | Prepare DNS, HTTPS, WAF, Pages, and static delivery path | Technical Lead | Cloudflare environment |
| 2.2 | Azure backend hosting | Prepare Azure App Service or Container Apps for backend APIs | Technical Lead | Backend runtime |
| 2.3 | Azure SQL setup | Prepare SQL database for staging and production | Technical Lead | SQL environments |
| 2.4 | Azure Blob Storage | Prepare document/export storage | Technical Lead | Storage containers |
| 2.5 | Monitoring setup | Configure Azure Monitor and Application Insights | Technical Lead | Monitoring dashboard |
| 2.6 | Budget alerts | Configure budget/cost alerts for MVP | Technical Lead / Project Manager | Cost guardrails |
5. WBS 3.0 Deployment Pipeline
| WBS ID | Work Package | Description | Owner | Key Output |
|---|---|---|---|---|
| 3.1 | Build preparation | Confirm frontend, backend, desktop, and database build steps | Technical Lead | Build checklist |
| 3.2 | Release package | Prepare deployable release package and archive structure | Technical Lead | Release package |
| 3.3 | Environment configuration | Separate dev, QA, staging, and production configuration | Technical Lead | Config baseline |
| 3.4 | Deployment approval gate | Define who approves staging and production deployment | Project Manager | Approval workflow |
| 3.5 | Rollback package | Preserve last-known-good package and rollback instructions | Technical Lead | Rollback pack |
6. WBS 4.0 Database And Data Loading
| WBS ID | Work Package | Description | Owner | Key Output |
|---|---|---|---|---|
| 4.1 | Migration baseline | Prepare and validate versioned database migrations | Technical Lead | Migration package |
| 4.2 | Reference data | Load production-safe lookup/reference data | Technical Lead | Reference data set |
| 4.3 | Test data pack | Prepare QA/staging test data only | QA / Business Analysis | Test data scripts |
| 4.4 | Production data rules | Define no-demo/no-UAT data controls | Project Manager / Technical Lead | Production data checklist |
| 4.5 | Backup before migration | Capture pre-release database backup | Technical Lead | Backup evidence |
7. WBS 5.0 Testing And QA
| WBS ID | Work Package | Description | Owner | Key Output |
|---|---|---|---|---|
| 5.1 | Functional UAT | Validate supplier, customer, operations, admin, and system owner journeys | Business Analysis / QA | UAT evidence |
| 5.2 | API testing | Validate request/response, errors, authorization, and workflow effects | Technical Lead / QA | API test evidence |
| 5.3 | Workflow testing | Validate state transitions and approval paths | QA | Workflow evidence |
| 5.4 | Role/access testing | Validate sidebar, permissions, backend access, and denied routes | QA / Technical Lead | Access matrix |
| 5.5 | UI/UX testing | Validate layout, language, buttons, desktop parity, and production cleanup | QA / Business Analysis | UI evidence |
| 5.6 | Reporting/export testing | Validate dashboard, reports, PDF, and Excel exports | QA | Reporting evidence |
| 5.7 | Negative testing | Validate invalid actions, blocked transitions, and unauthorized access | QA | Negative test record |
| 5.8 | Smoke testing | Validate critical production paths after deployment | QA / Technical Lead | Smoke test record |
8. WBS 6.0 Staging/UAT
| WBS ID | Work Package | Description | Owner | Key Output |
|---|---|---|---|---|
| 6.1 | Staging deployment | Deploy full package to staging/pre-production | Technical Lead | Staging deployment |
| 6.2 | Staging data load | Load approved test/reference data | Technical Lead / QA | Staging data state |
| 6.3 | Business walkthrough | Run business validation sessions | Business Analysis | Walkthrough notes |
| 6.4 | UAT sign-off | Capture formal business approval | Project Manager / Business Analysis | UAT sign-off |
| 6.5 | Production readiness gate | Confirm readiness before production cutover | Project Manager / Sponsor | Go/no-go record |
9. WBS 7.0 Production Cutover
| WBS ID | Work Package | Description | Owner | Key Output |
|---|---|---|---|---|
| 7.1 | Release freeze | Stop unapproved changes before cutover | Project Manager | Freeze notice |
| 7.2 | Pre-release backup | Capture production backup before deployment | Technical Lead | Backup evidence |
| 7.3 | Production deployment | Deploy backend, frontend, database migration, storage, and configuration | Technical Lead | Production release |
| 7.4 | Production smoke test | Validate login, roles, journeys, reports, and health checks | QA / Technical Lead | Smoke result |
| 7.5 | MVP user activation | Activate approved users only | Project Manager / Technical Lead | Activation log |
10. WBS 8.0 Hypercare And Stabilization
| WBS ID | Work Package | Description | Owner | Key Output |
|---|---|---|---|---|
| 8.1 | Hypercare monitoring | Monitor login, APIs, workflows, reports, notifications, and desktop | Technical Lead | Monitoring log |
| 8.2 | Issue triage | Classify, assign, and resolve production findings | Project Manager | Issue log |
| 8.3 | User support | Support approved users during MVP | Implementation team | Support record |
| 8.4 | Restore drill | Validate backup restore capability | Technical Lead / QA | Restore evidence |
| 8.5 | Stabilization report | Summarize defects, risks, actions, and readiness | Project Manager | Hypercare report |
11. WBS 9.0 Wider Rollout Decision
| WBS ID | Work Package | Description | Owner | Key Output |
|---|---|---|---|---|
| 9.1 | MVP results review | Review production usage, defects, support, performance, and business feedback | Project Manager / Sponsor | MVP review |
| 9.2 | Cost review | Compare actual hosting cost against estimate | Project Manager / Technical Lead | Cost review |
| 9.3 | Risk review | Confirm open risks before expansion | Project Manager | Risk update |
| 9.4 | Wider rollout recommendation | Recommend expand, hold, or remediate | Project Manager | Recommendation |
| 9.5 | Executive decision | Approve or defer wider rollout | Project Sponsor | Decision record |
12. WBS And Critical Path Alignment
| Critical Path Node | Related WBS | Planned Window |
|---|---|---|
| A - Charter approval | 1.1 | 21 Apr 2026 |
| B - Scope freeze | 1.2 | 22 Apr 2026 - 23 Apr 2026 |
| E/F - Pipeline and database readiness | 3.0 / 4.0 | 26 Apr 2026 - 28 Apr 2026 |
| H - QA regression | 5.0 | 29 Apr 2026 - 05 May 2026 |
| J - Staging deployment rehearsal | 6.1 | 06 May 2026 - 07 May 2026 |
| K - Staging UAT sign-off | 6.3 / 6.4 | 10 May 2026 - 13 May 2026 |
| L - Production readiness gate | 6.5 | 14 May 2026 |
| M/N/O - Cutover and smoke test | 7.0 | 17 May 2026 - 19 May 2026 |
| P - Hypercare | 8.0 | 20 May 2026 - 02 Jun 2026 |
| Q - Wider rollout decision | 9.0 | 03 Jun 2026 |
13. WBS Completion Criteria
| WBS | Completion Criteria |
|---|---|
| 1.0 | Charter, scope, governance, risks, and change control approved |
| 2.0 | Cloudflare, Azure, SQL, Blob, monitoring, and budget controls ready |
| 3.0 | Build, package, config, approval, and rollback path ready |
| 4.0 | Migrations, seed data, test data, production data rules, and backup evidence ready |
| 5.0 | Required tests completed and blocking findings resolved or formally accepted |
| 6.0 | Staging deployment and business UAT sign-off complete |
| 7.0 | Production deployed, smoke-tested, and approved MVP users activated |
| 8.0 | Hypercare completed with stabilization report and restore evidence |
| 9.0 | Wider rollout decision recorded |
14. External Integration Uncertainty Work Package
ETA/e-invoicing, Fawry, and Paymob must be tracked as explicit go-live uncertainty paths within the WBS. They are not baseline active MVP work packages unless third-party credentials, merchant/account access, authority access, endpoint configuration, callback configuration, certification evidence, and owner sign-off become available.
They may be added to the controlled MVP at any time if the third parties activate access earlier than expected. If that happens, the work must be inserted into the WBS through change control and linked to testing, deployment, security, backup/rollback, monitoring, and release approval.
| WBS Impact Area | ETA / e-invoicing | Fawry | Paymob |
|---|---|---|---|
| Scope control | Conditional activation path | Conditional activation path | Conditional activation path |
| Technical work | Credentials, endpoint, submission, exception handling | Merchant credentials, payment API, callbacks, reconciliation | Merchant credentials, payment API, callbacks, reconciliation |
| Testing work | Staging submission and exception testing | Payment-flow, callback, reconciliation, failure testing | Payment-flow, callback, reconciliation, failure testing |
| Release work | Finance/tax sign-off and production release approval | Payment owner sign-off and production release approval | Payment owner sign-off and production release approval |
| Risk control | Statutory reporting risk if activated too quickly | Payment/reconciliation risk if activated too quickly | Payment/reconciliation risk if activated too quickly |
No ETA/e-invoicing, Fawry, or Paymob capability should be enabled directly in production without impact assessment, staging validation, security review, rollback plan, owner approval, and release evidence.
15. Final Recommendation
The WBS should be used as the operational control structure for the MVP production project. It should be reviewed in project governance meetings, linked to the CPM schedule, and used to track readiness by workstream until the wider-rollout decision is formally recorded.