CashLine ERP Full Project Management Plan
Integrated master plan combining the project charter, WBS, CPM, dependency nodes, deployment strategy, testing strategy, hosting, backup/recovery, business visit plan, RACI, risks, budget framework, change control, and approval matrix.
Full project-management baseline: Charter + WBS + CPM + Deployment + Testing + Hosting + Backup + RACI + Risks + Budget + Approvals
CPM Network Diagram
The diagram below applies the Critical Path Method concept to the real CashLine MVP production nodes. Orange nodes/arrows represent the zero-slack critical path; blue nodes/arrows represent supporting work with float.
CashLine ERP MVP Full Project Management Plan
Document date: 2026-04-20
Document status: Full project-management baseline for controlled production MVP
Prepared for: CashLine ERP project sponsor, project manager, technical lead, business analysis, QA, implementation, operations, finance, business stakeholders, 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 document is the integrated project-management plan for the CashLine ERP controlled production MVP. It combines the project charter, Work Breakdown Structure, CPM schedule, dependency nodes, critical path calculation, deployment strategy, testing strategy, hosting strategy, backup/recovery controls, business visit plan, governance model, RACI, risks, budget framework, success criteria, and approval matrix into one professional project-control document.
The plan authorizes and organizes the work required to move CashLine ERP from implementation readiness into controlled production MVP, while protecting scope, data quality, role governance, testing evidence, backup/recovery readiness, deployment discipline, and stakeholder confidence.
2. Project Charter
2.1 Project Identification
| Field | Value |
|---|---|
| Project title | CashLine ERP Controlled Production MVP Implementation |
| Project sponsor | Khalid Gabr |
| Project manager | Mostafa El Shahawy |
| Technical lead | Nour Elsiminy |
| Business analysis | Doaa Sabry |
| Project customer | SMEs, business owners, key users, supplier users, customer users, internal operations users, administrators, and system owner |
| Planned release model | Controlled Production MVP |
| Planned start date | Tuesday, 21 Apr 2026 |
| Planned finish date | Wednesday, 03 Jun 2026 |
| CPM duration | 32 business days using Sunday-Thursday working week |
| Hosting recommendation | Cloudflare Pages / DNS / WAF -> Azure App Service or Azure Container Apps -> Azure SQL Database -> Azure Blob Storage -> Azure Monitor |
2.2 Project Purpose
The purpose of this project is to prepare, validate, deploy, and stabilize the CashLine ERP platform as a controlled production MVP. The project will move the system into a governed production operating model with controlled users, production hosting, staging validation, deployment discipline, database loading controls, backup/recovery safeguards, role-based access, reporting/export readiness, and hypercare support.
2.3 Business Objectives
| Objective | Description |
|---|---|
| Controlled production activation | Launch CashLine ERP as a limited, governed production MVP for approved users |
| Production credibility | Ensure the system appears and behaves as a live operational platform |
| Workflow continuity | Validate that user actions trigger workflow, notification, audit, and reporting effects |
| Access governance | Enforce System Owner, Administrator, supplier, customer, and internal role restrictions |
| Deployment discipline | Establish Development, QA, Staging/Pre-production, Production MVP, Stabilization, and Wider rollout controls |
| Hosting readiness | Implement a reliable and cost-efficient Cloudflare + Azure hosting model |
| Backup/recovery readiness | Separate production runtime from backup/recovery capability and prove restore readiness |
| Test completion | Execute functional, API, UI, role, workflow, database, desktop, reporting, negative, and smoke testing |
| Stabilization | Operate hypercare after go-live and resolve production-impacting findings |
| Wider rollout readiness | Confirm whether the MVP can expand to more users, functions, clients, and transaction volume |
3. Scope Management
3.1 In Scope
| Scope Area | Included Work |
|---|---|
| Production MVP planning | Finalize release gates, approval criteria, environment strategy, and deployment path |
| Hosting setup | Prepare Cloudflare and Azure target hosting model |
| Staging/pre-production | Create production-like validation environment before production deployment |
| Production environment | Prepare clean production configuration, database, users, access, and monitoring |
| Backup/recovery | Define and validate database backups, pre-release backups, document protection, release archives, and restore drills |
| Deployment pipeline | Establish controlled build, deployment, validation, and approval flow |
| Database preparation | Apply migrations, seed data, reference data, production data rules, and test-load controls |
| System testing | Execute MVP test coverage across user journeys, APIs, workflows, permissions, reports, exports, and desktop parity |
| User governance | Validate System Owner and Administrator behavior and user/function administration |
| Supplier/customer journeys | Validate onboarding, activation, document flow, status, notifications, and reporting impact |
| Internal operations journeys | Validate review, approve, reject, return, hold, reopen, and audit behavior |
| Reporting and exports | Validate MVP reports and PDF/Excel export capability |
| Desktop parity | Confirm desktop behavior matches web/backend production rules |
| Hypercare | Monitor production usage, triage issues, and report stabilization status |
3.2 Out Of Scope
| Excluded Area | Notes |
|---|---|
| Full enterprise go-live | This plan covers controlled MVP production only |
| Full Islamic Finance production launch | Deferred until scoring, Shariah, lender, settlement, and regulatory controls are completed |
| Automated credit decisioning | Not part of MVP production cutover |
| Live iScore or external bureau integration | Future work subject to official membership, consent, legal approval, and technical access |
| Oracle production parity | Not included unless separately approved |
| Unqualified payment/tax authority live integrations | External integrations must pass owner qualification before activation |
| Broad public user rollout | Wider rollout follows stabilization sign-off |
| Major feature redesign during cutover | Change requests must go through release governance |
4. Stakeholder And Team Management
| Stakeholder / Team | Role | Responsibilities |
|---|---|---|
| Khalid Gabr | Project Sponsor / Executive Owner | Business scope approval, financial governance, release authority, strategic direction, final go-live decision |
| Mostafa El Shahawy | Project Manager | Project planning, coordination, timeline tracking, risk management, stakeholder communication, release governance |
| Nour Elsiminy | Technical Lead | Technical readiness, hosting, deployment, database, performance, security, bug fixing, production support |
| Doaa Sabry | Business Analysis | Business validation, user journey mapping, UAT coordination, documentation, sign-off support |
| Founders | Executive Leadership | ROI, brand reputation, long-term scalability, commercial credibility |
| Technical team | Technical Support / Engineering | System setup, implementation, bug fixing, performance optimization, release support |
| Implementation team | Customer Service / Enablement | User onboarding, training, support, go-live assistance |
| Client stakeholders | End users / key users | Requirements confirmation, test execution, feedback, acceptance |
| Marketing and Sales | Growth | Convert MVP readiness into client-facing confidence and sales enablement |
5. Work Breakdown Structure
| 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 |
5.1 Detailed WBS Work Packages
| WBS ID | Work Package | Owner | Key Output |
|---|---|---|---|
| 1.1 | Charter approval | Project Sponsor / Project Manager | Approved charter |
| 1.2 | Scope freeze | Project Manager / Business Analysis | Frozen MVP scope |
| 1.3 | Governance cadence | Project Manager | Governance calendar |
| 1.4 | Risk and issue control | Project Manager | Risk and issue log |
| 1.5 | Change control | Project Manager | Change register |
| 2.1 | Cloudflare setup | Technical Lead | Cloudflare environment |
| 2.2 | Azure backend hosting | Technical Lead | Backend runtime |
| 2.3 | Azure SQL setup | Technical Lead | SQL environments |
| 2.4 | Azure Blob Storage | Technical Lead | Storage containers |
| 2.5 | Monitoring setup | Technical Lead | Monitoring dashboard |
| 2.6 | Budget alerts | Technical Lead / Project Manager | Cost guardrails |
| 3.1 | Build preparation | Technical Lead | Build checklist |
| 3.2 | Release package | Technical Lead | Release package |
| 3.3 | Environment configuration | Technical Lead | Config baseline |
| 3.4 | Deployment approval gate | Project Manager | Approval workflow |
| 3.5 | Rollback package | Technical Lead | Rollback pack |
| 4.1 | Migration baseline | Technical Lead | Migration package |
| 4.2 | Reference data | Technical Lead | Reference data set |
| 4.3 | Test data pack | QA / Business Analysis | Test data scripts |
| 4.4 | Production data rules | Project Manager / Technical Lead | Production data checklist |
| 4.5 | Backup before migration | Technical Lead | Backup evidence |
| 5.1 | Functional UAT | Business Analysis / QA | UAT evidence |
| 5.2 | API testing | Technical Lead / QA | API test evidence |
| 5.3 | Workflow testing | QA | Workflow evidence |
| 5.4 | Role/access testing | QA / Technical Lead | Access matrix |
| 5.5 | UI/UX testing | QA / Business Analysis | UI evidence |
| 5.6 | Reporting/export testing | QA | Reporting evidence |
| 5.7 | Negative testing | QA | Negative test record |
| 5.8 | Smoke testing | QA / Technical Lead | Smoke test record |
| 6.1 | Staging deployment | Technical Lead | Staging deployment |
| 6.2 | Staging data load | Technical Lead / QA | Staging data state |
| 6.3 | Business walkthrough | Business Analysis | Walkthrough notes |
| 6.4 | UAT sign-off | Project Manager / Business Analysis | UAT sign-off |
| 6.5 | Production readiness gate | Project Manager / Sponsor | Go/no-go record |
| 7.1 | Release freeze | Project Manager | Freeze notice |
| 7.2 | Pre-release backup | Technical Lead | Backup evidence |
| 7.3 | Production deployment | Technical Lead | Production release |
| 7.4 | Production smoke test | QA / Technical Lead | Smoke result |
| 7.5 | MVP user activation | Project Manager / Technical Lead | Activation log |
| 8.1 | Hypercare monitoring | Technical Lead | Monitoring log |
| 8.2 | Issue triage | Project Manager | Issue log |
| 8.3 | User support | Implementation team | Support record |
| 8.4 | Restore drill | Technical Lead / QA | Restore evidence |
| 8.5 | Stabilization report | Project Manager | Hypercare report |
| 9.1 | MVP results review | Project Manager / Sponsor | MVP review |
| 9.2 | Cost review | Project Manager / Technical Lead | Cost review |
| 9.3 | Risk review | Project Manager | Risk update |
| 9.4 | Wider rollout recommendation | Project Manager | Recommendation |
| 9.5 | Executive decision | Project Sponsor | Decision record |
6. Schedule Management And CPM
6.1 CPM Network Diagram Concept
The project-management plan includes a CPM network diagram concept based on the CashLine MVP production dependency nodes. The diagram should be read as follows:
- each activity node shows task ID, duration, early start, early finish, late start, late finish, and slack
- orange nodes and arrows represent the zero-slack critical path
- blue nodes and arrows represent non-critical supporting work with available float
- the current critical path duration is 32 business days
- the planned schedule runs from Tuesday, 21 Apr 2026 to Wednesday, 03 Jun 2026
Diagram asset for the Cloudflare package:
assets/cashline-mvp-cpm-network-diagram-2026-04-20.svg
6.2 Dependency Nodes
| Node | Activity | Duration | Dependencies | Planned Start | Planned Finish |
|---|---|---|---|---|---|
| A | Project charter approval and governance kickoff | 1 | None | 21 Apr 2026 | 21 Apr 2026 |
| B | MVP scope freeze and release baseline confirmation | 2 | A | 22 Apr 2026 | 23 Apr 2026 |
| C | Hosting account, Cloudflare, Azure, DNS, and environment provisioning | 3 | B | 26 Apr 2026 | 28 Apr 2026 |
| D | Backup/recovery model and restore-drill plan | 2 | B | 26 Apr 2026 | 27 Apr 2026 |
| E | CI/CD pipeline and deployment package preparation | 3 | B | 26 Apr 2026 | 28 Apr 2026 |
| F | Database migration, seed, and production data-load preparation | 3 | B | 26 Apr 2026 | 28 Apr 2026 |
| G | QA/staging test-data pack preparation | 2 | B | 26 Apr 2026 | 27 Apr 2026 |
| H | QA system, API, workflow, UI, desktop, and reporting regression | 5 | E, F, G | 29 Apr 2026 | 05 May 2026 |
| I | Security, role, function, and access-control review | 3 | C, E, F | 29 Apr 2026 | 03 May 2026 |
| J | Staging/pre-production deployment rehearsal | 2 | C, D, E, F, H, I | 06 May 2026 | 07 May 2026 |
| K | Staging UAT and business sign-off | 4 | J | 10 May 2026 | 13 May 2026 |
| L | Production readiness gate and go/no-go approval | 1 | K | 14 May 2026 | 14 May 2026 |
| M | Production backup and cutover preparation | 1 | L | 17 May 2026 | 17 May 2026 |
| N | Production deployment and database migration | 1 | M | 18 May 2026 | 18 May 2026 |
| O | Production smoke test and MVP user activation | 1 | N | 19 May 2026 | 19 May 2026 |
| P | Hypercare stabilization window | 10 | O | 20 May 2026 | 02 Jun 2026 |
| Q | Wider rollout decision and closure report | 1 | P | 03 Jun 2026 | 03 Jun 2026 |
6.3 Critical Path Calculation
| Node | Duration | ES | EF | LS | LF | Float | Critical |
|---|---|---|---|---|---|---|---|
| A | 1 | 0 | 1 | 0 | 1 | 0 | Yes |
| B | 2 | 1 | 3 | 1 | 3 | 0 | Yes |
| C | 3 | 3 | 6 | 5 | 8 | 2 | No |
| D | 2 | 3 | 5 | 9 | 11 | 6 | No |
| E | 3 | 3 | 6 | 3 | 6 | 0 | Yes |
| F | 3 | 3 | 6 | 3 | 6 | 0 | Yes |
| G | 2 | 3 | 5 | 4 | 6 | 1 | No |
| H | 5 | 6 | 11 | 6 | 11 | 0 | Yes |
| I | 3 | 6 | 9 | 8 | 11 | 2 | No |
| J | 2 | 11 | 13 | 11 | 13 | 0 | Yes |
| K | 4 | 13 | 17 | 13 | 17 | 0 | Yes |
| L | 1 | 17 | 18 | 17 | 18 | 0 | Yes |
| M | 1 | 18 | 19 | 18 | 19 | 0 | Yes |
| N | 1 | 19 | 20 | 19 | 20 | 0 | Yes |
| O | 1 | 20 | 21 | 20 | 21 | 0 | Yes |
| P | 10 | 21 | 31 | 21 | 31 | 0 | Yes |
| Q | 1 | 31 | 32 | 31 | 32 | 0 | Yes |
Critical path:
A -> B -> E/F -> H -> J -> K -> L -> M -> N -> O -> P -> Q
Total duration:
32 business days, from Tuesday 21 Apr 2026 to Wednesday 03 Jun 2026
7. Milestone Management
| Milestone | Date / Window | Acceptance Criteria |
|---|---|---|
| Charter approved | 21 Apr 2026 | Sponsor and project manager approval captured |
| MVP scope frozen | 22 Apr 2026 - 23 Apr 2026 | Scope, exclusions, release baseline, and success criteria confirmed |
| Hosting and infrastructure ready | 26 Apr 2026 - 28 Apr 2026 | Cloudflare/Azure environment path confirmed |
| Pipeline and database ready | 26 Apr 2026 - 28 Apr 2026 | Deployment package and migration path ready |
| QA regression complete | 29 Apr 2026 - 05 May 2026 | System, API, workflow, UI, role, desktop, and reporting tests completed |
| Staging deployed | 06 May 2026 - 07 May 2026 | Production-like rehearsal complete |
| UAT signed off | 10 May 2026 - 13 May 2026 | Business confirms staging readiness |
| Production go/no-go | 14 May 2026 | Release owner approves cutover |
| Production deployed | 18 May 2026 | Production package deployed |
| Production smoke passed | 19 May 2026 | Critical paths pass in production |
| Hypercare complete | 02 Jun 2026 | Critical issues closed or controlled |
| Wider rollout decision | 03 Jun 2026 | Executive decision recorded |
8. Deployment Management
The deployment model follows:
Development -> QA -> Staging/Pre-production -> Controlled Production MVP -> Stabilization -> Wider rollout
Deployment rules:
- No direct production change without staging rehearsal.
- No production deployment without pre-release backup.
- No UAT/demo records in production.
- No production launch without role/access validation.
- No wider rollout before stabilization sign-off.
- All release actions must be recorded in the production cutover record.
9. Testing And Quality Management
| Test Type | Coverage |
|---|---|
| Functional UAT | Supplier, customer, internal operations, administrator, and system owner journeys |
| API testing | Request/response validation, errors, authorization, and workflow-triggered behavior |
| Workflow testing | Approval, rejection, return, hold, reopen, activation, and status progression |
| Database testing | Migration, seed data, test loading, production data rules, and rollback readiness |
| Role/permission testing | Sidebar, function access, backend enforcement, unauthorized route denial |
| UI/UX testing | Layout, buttons, navigation, Arabic/English behavior, desktop parity, and content cleanup |
| Reporting testing | Dashboard, reports, drilldowns, PDF export, Excel export, and audit visibility |
| Negative testing | Invalid data, duplicate actions, unauthorized access, missing reasons, and invalid transitions |
| Asynchronous testing | Notifications, retries, failures, recovery, and delayed workflow effects |
| Production smoke testing | Login, role visibility, one supplier/customer/internal path, reports, exports, and health checks |
10. Hosting And Infrastructure Management
| Layer | MVP Recommendation |
|---|---|
| Frontend | Cloudflare Pages |
| DNS / CDN / WAF | Cloudflare |
| Backend API | Azure App Service or Azure Container Apps |
| Database | Azure SQL Database |
| Documents and exports | Azure Blob Storage |
| Monitoring | Azure Application Insights and Azure Monitor |
| Secrets/configuration | Azure Key Vault or Azure App Configuration |
| Backup/recovery | Azure SQL PITR, pre-release backup, Blob soft-delete/versioning, release package archive |
11. Backup And Recovery Management
Production and backup/recovery must remain separate. Backup/recovery is not another production environment and must not be used for normal user activity, testing, reporting experiments, or operational processing.
| Backup Area | MVP Requirement |
|---|---|
| Azure SQL automatic backups | Enable point-in-time restore with at least 7 days minimum retention, preferably up to 35 days if budget allows |
| Pre-deployment backup | Required before every production deployment or migration |
| Blob/document protection | Enable soft-delete, versioning, or equivalent retention |
| Release package archive | Preserve backend, frontend, desktop, Cloudflare, and configuration package |
| Restore drill | Run before go-live and monthly during MVP stabilization |
| RPO | MVP baseline: 24 hours or better unless live finance data requires tighter recovery |
| RTO | MVP baseline: same business day recovery unless business requires tighter SLA |
12. Business Visit Plan
12.1 Travel Plan A
| Governorate | Travel Date | Travel Day | Departure Date | Departure Day |
|---|---|---|---|---|
| Beni Suef | 02 May 2026 | Saturday | 05 May 2026 | Tuesday |
| Minya | 05 May 2026 | Tuesday | 08 May 2026 | Friday |
| Assiut | 08 May 2026 | Friday | 12 May 2026 | Tuesday |
| Sohag | 12 May 2026 | Tuesday | 15 May 2026 | Friday |
| Qena | 15 May 2026 | Friday | 19 May 2026 | Tuesday |
| Luxor | After Eid al-Adha | |||
| Aswan | ||||
| Hurghada |
12.2 Travel Plan B
| Governorate | Travel Date | Travel Day | Departure Date | Departure Day |
|---|---|---|---|---|
| Hurghada | 02 May 2026 | Saturday | 05 May 2026 | Tuesday |
| Qena | 05 May 2026 | Tuesday | 08 May 2026 | Friday |
| Assiut | 08 May 2026 | Friday | 12 May 2026 | Tuesday |
| Sohag | 12 May 2026 | Tuesday | 15 May 2026 | Friday |
| Minya | 15 May 2026 | Friday | 19 May 2026 | Tuesday |
| Luxor | After Eid al-Adha | |||
| Aswan | ||||
| Beni Suef |
13. RACI Matrix
| Workstream | Khalid Gabr | Mostafa El Shahawy | Nour Elsiminy | Doaa Sabry | Technical Team | Implementation Team |
|---|---|---|---|---|---|---|
| Charter approval | A | R | C | C | I | I |
| MVP scope freeze | A | R | C | R | I | C |
| Hosting setup | I | C | A/R | I | R | I |
| Database migration | I | C | A/R | C | R | I |
| Testing and UAT | I | A | R | R | R | C |
| Production cutover | A | R | R | C | R | I |
| Hypercare | I | A/R | R | C | R | R |
| Wider rollout decision | A | R | C | C | I | I |
14. Risk Management
| Risk | Impact | Mitigation | Owner |
|---|---|---|---|
| User adoption resistance | Slow uptake and weak MVP value perception | Training, role-based walkthroughs, hypercare support | Implementation team |
| Production data contamination | Loss of production credibility and reporting quality | No UAT/demo data in production; controlled data load checklist | Technical Lead |
| Migration failure | Deployment delay or data inconsistency | Migration dry-run, backup, rollback plan | Technical Lead |
| Role/access misconfiguration | Unauthorized access or hidden function failure | Role/function regression testing and production smoke validation | QA / Technical Lead |
| Hosting instability | Downtime or poor user experience | Cloudflare + Azure managed services, monitoring, alerts | Technical Lead |
| Backup not restorable | Recovery failure during incident | Restore drill before go-live and monthly checks | Technical Lead |
| Unclear scope changes | Schedule delay and project drift | Scope freeze, change approval, sponsor escalation | Project Manager |
| Critical bugs after go-live | User disruption and reputational risk | Hypercare, severity triage, rollback readiness | Project Manager / Technical Lead |
| Integration assumptions | False readiness claims | Keep unqualified integrations disabled until owner sign-off | Project Sponsor / Technical Lead |
| ETA/e-invoicing, Fawry, or Paymob activated by third party during MVP | Scope, schedule, security, testing, reconciliation, tax, and release risk if credentials become active unexpectedly | Treat as go-live uncertainty path; require change control, staging test, owner sign-off, rollback plan, and production release approval | Project Sponsor / Project Manager / Technical Lead |
15. Budget Framework
Hosting cost is included based on the approved hosting strategy. Other cost elements are intentionally left blank for business/finance completion.
| Cost Element | Estimated Cost | Notes |
|---|---|---|
| Hosting - Lean controlled MVP | $80 - $250/month | Cloudflare + Azure low-cost controlled MVP |
| Hosting - Production-comfortable MVP | $250 - $600/month | Cloudflare + Azure with more production comfort |
| Human resources | To be completed by business/finance | |
| Implementation services | To be completed by business/finance | |
| QA/testing services | To be completed by business/finance | |
| Security review | To be completed by business/finance | |
| Training and enablement | To be completed by business/finance | |
| Support and operations | To be completed by business/finance | |
| Marketing and sales | To be completed by business/finance | |
| Contingency | To be completed by business/finance | |
| Total | To be completed by business/finance |
16. External Integration Go-Live Uncertainty Paths
ETA/e-invoicing, Fawry, and Paymob are explicit go-live uncertainty paths for the MVP. They are currently held/conditional because activation depends on third-party credentials, merchant/account access, authority access, endpoint configuration, callback readiness, certification evidence, and owner sign-off.
These paths may be added to the controlled MVP at any time if the relevant third party activates the required credentials or access during MVP preparation, staging, cutover, stabilization, or early production. This is a formal project risk and change-control dependency. It is not a permanent exclusion and it is not an automatic production approval.
| External Path | Current MVP Position | Trigger For Activation | Required Project Control |
|---|---|---|---|
| ETA / e-invoicing | Held / conditional | ETA credentials, authority access, target endpoint, and submission evidence become available | Change request, impact assessment, staging submission test, tax/finance sign-off, rollback plan, production approval |
| Fawry | Held / conditional | Fawry merchant credentials, API access, callback configuration, and payment test evidence become available | Change request, impact assessment, payment-flow test, callback validation, reconciliation check, rollback plan, production approval |
| Paymob | Held / conditional | Paymob merchant credentials, API access, callback configuration, and payment test evidence become available | Change request, impact assessment, payment-flow test, callback validation, reconciliation check, rollback plan, production approval |
No team member should enable ETA/e-invoicing, Fawry, or Paymob directly in production only because credentials become available. Activation must be approved through project governance and must include test evidence, security review, monitoring, owner sign-off, and release documentation.
17. Success Criteria
| Success Criterion | Measurement |
|---|---|
| Production MVP is live | Approved users can access production environment |
| No critical production blockers | Severity 1 issues are zero or controlled by approved workaround |
| Role governance works | System Owner, Administrator, supplier, customer, and internal role visibility is enforced |
| Core workflows operate | Supplier/customer onboarding and internal review workflows complete as designed |
| Reports and exports work | MVP reports export successfully to PDF/Excel |
| Backup/recovery is proven | Pre-release backup and restore drill evidence exist |
| Hypercare is operating | Daily issue review and stabilization reporting active |
| Wider rollout decision ready | Sponsor receives evidence-based go/no-go recommendation |
18. Communication Plan
| Communication | Audience | Frequency | Owner |
|---|---|---|---|
| Project governance update | Sponsor, PM, technical lead, BA | Weekly or as needed during cutover | Project Manager |
| Daily readiness standup | Technical, QA, implementation | Daily during active cutover window | Project Manager |
| Risk and blocker escalation | Sponsor and responsible owners | As needed | Project Manager |
| UAT status | Business and QA stakeholders | During staging/UAT | Business Analysis |
| Production cutover notice | Approved MVP users and project team | Before production deployment | Project Manager |
| Hypercare report | Sponsor, PM, technical lead, BA | Daily during hypercare | Project Manager |
| Wider rollout recommendation | Executive stakeholders | At project closure gate | Project Manager |
19. Change Control
| Change Type | Required Approval |
|---|---|
| Scope expansion | Project Sponsor and Project Manager |
| Production deployment date change | Project Sponsor and Project Manager |
| Hosting architecture change | Technical Lead and Project Sponsor |
| Database migration change | Technical Lead and Project Manager |
| User role/access model change | Project Manager, Business Analysis, Technical Lead |
| Cost-impacting change | Project Sponsor |
| Wider rollout change | Project Sponsor |
| ETA/e-invoicing, Fawry, or Paymob activation | Project Sponsor, Project Manager, Technical Lead, and relevant business owner |
20. Approval Matrix
| Approval Role | Name | Approval Status | Signature / Date |
|---|---|---|---|
| Project Sponsor | Khalid Gabr | Pending | |
| Project Manager | Mostafa El Shahawy | Pending | |
| Technical Lead | Nour Elsiminy | Pending | |
| Business Analysis | Doaa Sabry | Pending | |
| Client / Business Representative | Pending |
21. Final Project Management Statement
This full project-management plan should be used as the controlling document for the CashLine ERP controlled production MVP. It connects the project charter, WBS, CPM, testing, deployment, hosting, backup/recovery, visit planning, RACI, risks, budget framework, and approvals into one operating baseline.
The project should proceed as a controlled MVP production activation, not a full enterprise big-bang go-live. Wider rollout should occur only after stabilization evidence, cost review, risk review, and sponsor approval.