PROJECT MANAGEMENT

REPORT
Visualisation Platform for Government Datasets
(VPGD)

Project Title: Visualisation Platform for Government Datasets

Course: Project Management

Institution: University of Engineering and Technology, Lahore

Session: 2023  2027

Date: June 2026

Document Version: 1.0  Final Submission

Department of Computer Science | UET Lahore

Contents
1 Project Name 2
2 Project Description 3
2.1 Purpose of the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2 Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.3 Problem Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.4 Proposed Solution & Key Features . . . . . . . . . . . . . . . . . . . . . . . . 4
2.5 Target Users & Expected Benets . . . . . . . . . . . . . . . . . . . . . . . . . 4

3 Project Scope Document 5

3.1 Project Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.2 In-Scope vs Out-of-Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.3 Deliverables, Assumptions & Constraints . . . . . . . . . . . . . . . . . . . . . 7
3.4 Success Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

4 Work Breakdown Structure (WBS) 8

4.1 WBS Hierarchical Numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.2 WBS Tree Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

5 Communication Plan 11
6 Responsibility Matrix (RACI) 13
7 Project Activities 15
8 Activity Table & Network Diagram 18
8.1 Activity Predecessor Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
8.2 Network Diagram (Activity-on-Node) . . . . . . . . . . . . . . . . . . . . . . . 19

9 Critical Path Analysis 20

9.1 Forward Pass  ES & EF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

10 Risk Management 23
10.1 Risk Breakdown Structure (RBS) . . . . . . . . . . . . . . . . . . . . . . . . . 23
10.2 Risk Severity Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
10.3 Risk Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

11 Conclusion 26

1
1. Project Name
Project Title
Visualisation Platform for Government Datasets (VPGD):
A Web-Based
Public SectorOpen Data Dashboard
Transparency and and Analytics Decision
Evidence-Based System for
Making

2
2. Project Description
2.1 Purpose of the System
The Visualisation Platform for Government Datasets (VPGD) is a comprehensive, web-based
software solution designed to empower government agencies, policy analysts, and the general
public to upload, manage, analyse, and visually interpret large volumes of structured public-
sector data. The platform eliminates barriers traditionally associated with data analysis and
democratises access to actionable governmental insights through an intuitive, browser-based
environment.

2.2 Background
Governments at national, provincial, and municipal levels routinely collect vast amounts
of data spanning demographics, health, education, transportation, nance, infrastructure,
and environmental conditions. This data historically resides in disconnected silosstored
across incompatible systems and released in static formats. The global open government
data movement has demonstrated the substantial societal and economic benets of freely
accessible data, yet simply publishing raw datasets is insucient. True value is realised
only when citizens and administrators can explore, visualise, and contextualise information
interactively.

2.3 Problem Statement

ˆ Government datasets are dispersed across multiple portals with no unied access point.

ˆ Existing portals provide static downloads with no built-in visualisation capabilities.

ˆ Non-technical users lack accessible tools to explore and interpret raw data.

ˆ No standardised data quality management exists, leading to inconsistent records.

ˆ Geographical data representation is inadequate; geospatial mapping is absent.

ˆ Real-time data updates are not supported, impeding time-sensitive decisions.

2.4 Proposed Solution & Key Features

3
Visualisation Platform for Government Datasets Project Management Report

Dashboard Chart (Browser

& Export
Presentation Map
Builder Layer
Engine /Filter
Search
&
Responsive Web UI)
(PDF/Excel)

RBAC Data
Auth /Application Ingestion
Layer Vis. /Engine
(REST API Report Gen.
Business Logic) External
Govt. APIs

Data Layer (PostgreSQL + Redis Cache)

Infrastructure Layer (AWS Cloud / Docker / Nginx)

Figure 2.1. VPGD System Architecture Overview

2.5 Target Users & Expected Benets

Target User Groups Expected Benets
ˆ Government Ministry Data Ocers ˆ Enhanced public-sector transparency

ˆ Policy Analysts & Research Ocers ˆ Data analysis time reduced from days to
minutes
ˆ Journalists & Transparency Advocates
ˆ Evidence-based policy development
ˆ General Citizens & Civil Society Organi-
sations ˆ Improved citizen trust via live dashboards

ˆ Reduced manual reporting overhead

UET Lahore  PM Course 2026 4

3. Project Scope Document
3.1 Project Objectives
#
Objective

1 Design and develop a secure, web-based platform for government dataset

upload and management.

2 Implement an interactive multi-format visualisation engine (charts, maps,

dashboards).

3 Deliver a role-based access control system with Admin, Analyst, and

Viewer roles.

4 Provide dataset export capabilities in PDF, Excel, PNG, and SVG

formats.

5 Ensure platform scalability to handle datasets of up to 10 million records.

6 Complete the full project lifecycle within 95 working days and within
approved budget.

Table 3.1. Project Objectives

3.2 In-Scope vs Out-of-Scope

5
Visualisation Platform for Government Datasets Project Management Report

In-Scope Features
Out-of-Scope Features

Multi-format dataset upload Native mobile applications

(CSV, JSON, Excel, XML) (iOS/Android)

Interactive dashboard builder Real-time streaming data

pipelines

Chart, map & geospatial Machine learning / AI

visualisation predictions

Role-Based Access Control Legacy dataset migration

(RBAC)

PDF, Excel, PNG, SVG Custom third-party plugin

export development

Audit trails & metadata Oine / desktop client

tagging

RESTful API gateway Multi-language localisation

(Phase 1)

Table 3.2. Scope Boundaries

3.3 Deliverables, Assumptions & Constraints

UET Lahore  PM Course 2026 6

Visualisation Platform for Government Datasets Project Management Report

Deliverable
Assumptions Constraints

Project Charter Client SMEs available from Completion within 95

Day 1 working days

Scope Document Dataset samples provided Budget envelope xed

by Day 15

Requirements Cloud infra provisioned by Open-source technologies

Spec. Dev phase only

Design Artefacts Team skills match resource ISO 27001 security

plan compliance

Web Application Budget unchanged National data protection

throughout compliance

Test Reports Written UAT commitment No scope changes after

by Day 30 baseline

User Manual Stakeholders attend review Single-language (English)

meetings for Phase 1

Project Closure PM authority to escalate All deliverables require

Report risks client sign-o

Table 3.3. Deliverables, Assumptions and Constraints

3.4 Success Criteria

Criterion
Measurable Target

System Uptime 99.5% uptime during UAT period

Performance Dashboard load ≤ 3 seconds for 500K-record

datasets

Usability ≥ 85% of UAT participants rate interface easy to

use

Data Integrity Zero data corruption incidents during testing

Schedule Project delivered within 95-day schedule

Scope Compliance All in-scope features conrmed at nal sign-o

Table 3.4. Project Success Criteria

UET Lahore  PM Course 2026 7

4. Work Breakdown Structure (WBS)
4.1 WBS Hierarchical Numbering
WBS ID
Element Name Level Description

1.0 VPGD Project 1 Total project scope

1.1 Initiation 2 Project authorisation and

setup

1.1.1 Project Charter 3 Draft and approve project

charter

1.1.2 Stakeholder Identication 3 Identify and register all

stakeholders

1.2 Planning 2 Comprehensive project

planning

1.2.1 Scope Document 3 Dene and document project

scope

1.2.2 WBS & Schedule 3 Develop WBS and project

schedule

1.2.3 Resource Plan 3 Assign team roles and

resources

1.3 Requirements Analysis 2 Elicitation and documentation

1.3.1 Functional Requirements 3 Document system functional

specications

1.3.2 Non-Functional 3 Dene performance, security,

Requirements usability specs

1.3.3 Use Case Documentation 3 Develop use case diagrams

and narratives

1.4 Design 2 System and user interface

design

1.4.1 UI/UX Wireframes 3 Design and validate all screen

wireframes

1.4.2 Database Schema Design 3 Design and normalise the

relational DB schema

1.4.3 System Architecture 3 Dene three-tier architecture

and API design

1.5 Development 2 Full-stack software

development

8
Visualisation Platform for Government Datasets Project Management Report

WBS ID
Element Name Level Description

1.5.1 Backend Development 3 Server-side logic and API

implementation

[Link] API Development 4 Develop RESTful API

endpoints

[Link] Database Implementation 4 Implement and seed

production database

1.5.2 Frontend Development 3 Client-side UI implementation

[Link] Dashboard UI 4 Build interactive dashboard

components

[Link] Chart & Map Widgets 4 Implement chart and

geospatial map modules

1.5.3 Data Integration 3 Connect data sources and

pipeline modules

1.6 Testing 2 Quality assurance and

validation

1.6.1 Unit Testing 3 Test individual modules and

functions

1.6.2 Integration Testing 3 Test module interactions and

data ows

1.6.3 UAT 3 Formal user acceptance

testing

1.7 Deployment 2 Platform release and

conguration

1.7.1 Staging Environment 3 Deploy and validate on

staging server

1.7.2 Production Deployment 3 Release platform to

production

1.7.3 Cong & Monitoring 3 Congure monitoring, alerts,

and backups

1.8 Documentation 2 Technical and user

documentation

1.8.1 Technical Documentation 3 Developer and API reference

docs

1.8.2 User Manual 3 End-user guide and help

system

1.8.3 API Documentation 3 REST API reference and

integration guide

1.9 Training 2 User and administrator

training

UET Lahore  PM Course 2026 9

Visualisation Platform for Government Datasets Project Management Report

WBS ID
Element Name Level Description

1.9.1 User Training 3 Conduct end-user training

sessions

1.9.2 Admin Training 3 Conduct system admin

training

1.10 Project Closure 2 Formal project wrap-up

1.10.1 Final Sign-O 3 Obtain formal client

acceptance

1.10.2 Lessons Learned 3 Document and archive lessons

learned

Table 4.1. WBS Hierarchical Numbering

4.2 WBS Tree Diagram

1.0 VPGD Project

1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.9 1.10
Initiation Planning Requirements Design Development Testing Deployment Documentation Training Closure

1.1.1 1.1.2
1.2.1 1.2.2 1.2.3
1.3.1 1.3.2 1.3.3
1.4.1 1.4.2 1.4.3 1.5.1 1.5.2 1.6.1
1.5.3 1.6.2 1.6.3
1.7.1 1.7.2 1.8.1
1.7.3 1.8.2 1.8.3
1.9.1 [Link].1 1.10.2
Charter Stakeholders
Scope DocWBS/SchedResources
Func. [Link]
Wireframes
Cases DB SchemaSys. Arch. Backend FrontendData
UnitInteg.
TestInteg. Test UAT
Staging Production Tech Docs
Cong/Mon User ManualAPI Docs
User Train Admin Sign-O
Train Lessons

[Link] [Link] [Link] [Link]

API Dev DashboardDB Impl Charts/Maps

Figure 4.1. WBS Tree Diagram  Levels 1 through 4

UET Lahore  PM Course 2026 10

5. Communication Plan
Information Purpose Method Freq. Owner
Stakeholder
Project Budget, Executive Written Bi- PM
Sponsor milestones, risks oversight report + weekly
brieng
Client Repre- Requirements, Validate Steering Weekly PM
sentative UAT sign-o deliverables committee
Project Task progress, Day-to-day Daily Daily Team
Manager blockers control stand-up Leads
Business Req. changes, Keep reqs Working 2Ö/week BA
Analyst feedback current sessions
Development Sprint tasks, tech Clear work Agile Daily PM
Team specs instructions sprint/JIRA
QA Tester Test plans, defect Coordinate Test mgmt. Per build QA Lead
status testing tool
UI/UX Wireframe Maintain Design Weekly PM
Designer feedback design reviews
quality
Database Schema changes, DB Tech review As Backend
Admin perf. integrity mtgs required Dev
End Users Training, UAT Platform Email + UAT/Training
BA
(Pilot) guide adoption portal
IT Security Security reviews, Security Formal At mile- PM
Ocer compliance standards review stones
sessions

Table 5.1. Communication Plan

11
Visualisation Platform for Government Datasets Project Management Report

Stakeholder Power-Interest Grid

KEEP SATISFIED MANAGE CLOSELY

PM Sponsor
High
UI/UX Client Rep
Level of Inuence

IT Security
Dev Team
Medium BA

DB Admin
QA Tester End Users

Low
MONITOR KEEP INFORMED

Low Medium High

Level of Interest
Figure 5.1. Stakeholder Power-Interest Grid

UET Lahore  PM Course 2026 12

6. Responsibility Matrix (RACI)
PM BA UI/UX DB Back Front QA Client
Activity
Project Charter A/R C I I I I I C
Stakeholder ID A/R R I I I I I C
Scope Document A R C C C C I C
WBS & Schedule A/R C I I C C I I
Resource Planning A/R I I I I I I I
Functional Requirements A R C C C C C R
Non-Functional Req. A R I C C I C C
Use Case Documentation I A/R C I C C I C
UI/UX Wireframes A C R I I C C C
DB Schema Design I C I A/R C I I I
System Architecture A C I C R C I I
Backend API Dev. I I I C A/R I I I
DB Implementation I I I A/R R I I I
Frontend Dashboard I I C I C A/R I I
Data Integration I C I C A/R C I I
Unit Testing A I I I C C R I
Integration Testing A I I I C C R I
UAT Execution A C C I C C R R
Bug Fixing A I C C R R R I
Technical Docs A I I C R R I I
User Manual A R C I C C C C
Staging Deployment A I I I R R C I
Production Deploy A I I I R R C I
User Training A R I I I I I C
Admin Training A C I R R C I I
Project Closure A/R C I I I I I R
Table 6.1. RACI Matrix (R=Responsible, A=Accountable, C=Consulted, I=Informed)

13
Visualisation Platform for Government Datasets Project Management Report

RACI  R/A Assignment Count per Role

Number of Assignments (R or A) 15

10

0
PM BA X s. nd d QA p.
/U De cke ten Re
UI DB B a Fr o n
ent
Cli
Team Role
Figure 6.1. Number of Responsible/Accountable assignments per role

UET Lahore  PM Course 2026 14

7. Project Activities

15
Visualisation Platform for Government Datasets Project Management Report

ID
Activity Description WBS Ref. Duration

A Project Initiation (Charter & 1.1 5 days

Kick-o )

B Stakeholder Identication and 1.1.2 3 days

Register

C Scope Document Preparation 1.2.1 5 days

D WBS Development and Project 1.2.2 5 days

Scheduling

E Resource Planning and Team 1.2.3 4 days

Assignment

F Functional Requirements Elicitation 1.3.1 7 days

G Non-Functional Requirements 1.3.2 5 days

Denition

H Use Case Documentation 1.3.3 5 days

I UI/UX Wireframe Design and 1.4.1 8 days

Review

J Database Schema Design 1.4.2 6 days

K System Architecture Design 1.4.3 7 days

L Backend API and Server-Side 1.5.1 15 days

Development

M Frontend Dashboard and UI 1.5.2 14 days

Development

N Data Integration and Pipeline 1.5.3 10 days

Development

O Unit Testing of All Modules 1.6.1 7 days

P Integration Testing 1.6.2 8 days

Q Performance and Load Testing 1.6.2 5 days

R User Acceptance Testing (UAT) 1.6.3 6 days

S Bug Fixing and Regression Testing 1.6.3 5 days

T Technical Documentation and API 1.8.1/3 5 days

Reference

U User Manual Preparation 1.8.2 4 days

V Staging Environment Deployment 1.7.1 4 days

W User and Administrator Training 1.9 5 days

X Production Deployment and 1.7.2/3 3 days

Conguration

Y Project Closure and Sign-O 1.10 4 days

Table 7.1. Complete Project Activity List

UET Lahore  PM Course 2026 16

Visualisation Platform for Government Datasets Project Management Report

Activity Duration Chart

A
B
C
D
E
F
G
H
I
J
K
L
M
N
O
P
Q
R
S
T
U
V
W
X
Y

Duration (Days)
0 2 4 6 8 10 12 14 16 18

Figure 7.1. Activity Duration Bar Chart (Activities AY)

UET Lahore  PM Course 2026 17

8. Activity Table & Network Diagram
8.1 Activity Predecessor Table
ID
Activity Description Predecessor(s) Duration

A Project Initiation  5

B Stakeholder Identication A 3

C Scope Document B 5

D WBS & Scheduling C 5

E Resource Planning D 4

F Functional Requirements D 7

G Non-Functional Requirements D 5

H Use Case Documentation F, G 5

I UI/UX Wireframes H 8

J Database Schema Design H 6

K System Architecture H 7

L Backend Development I, J, K 15

M Frontend Development I, K 14

N Data Integration I, J 10

O Unit Testing L, M, N 7

P Integration Testing O 8

Q Performance Testing P 5

R UAT P 6

S Bug Fixing & Regression R 5

T Technical Documentation R 5

U User Manual R 4

V Staging Deployment S, T, U 4

W Training V 5

X Production Deployment W 3

Y Project Closure X 4

Table 8.1. Activity Predecessor Table

8.2 Network Diagram (Activity-on-Node)

18
Visualisation Platform for Government Datasets Project Management Report

E K M Q
[Link] [Link] Frontend Perf Test
4d 7d 14d 5d

A B C D F H I L O P
Init Stake Scope WBS [Link] Use Case UI/UX Backend Unit Test Integ Test
5d 3d 5d 5d 7d 5d 8d 15d 7d 8d S
Bug Fix
5d
G J N R
NF Req DB Schema Data Integ UAT V W X Y

5d 6d 10d 6d Staging Training Prod Dep Closure

T 4d 5d 3d 4d
Tech Doc
5d

U
User Man
4d

Figure 8.1. Activity-on-Node Network Diagram  Critical path in red solid, non-critical in blue
dashed

UET Lahore  PM Course 2026 19

9. Critical Path Analysis
9.1 Forward Pass  ES & EF
Forward Pass Rule
ES of activity = MAX(EF of all predecessors). EF = ES + Duration.

20
Visualisation Platform for Government Datasets Project Management Report

Activity Dur ES EF LS LF Slack

ID
Project Initiation 5 0 5 0 5 0
A
Stakeholder ID 3 5 8 5 8 0
B
Scope Document 5 8 13 8 13 0
C
WBS & Scheduling 5 13 18 13 18 0
D
E Resource Planning 4 18 22 19 23 1
Functional Req. 7 18 25 18 25 0
F
G Non-Functional Req. 5 18 23 20 25 2
Use Case Docs 5 25 30 25 30 0
H
UI/UX Wireframes 8 30 38 30 38 0
I
J DB Schema Design 6 30 36 32 38 2
K System Architecture 7 30 37 31 38 1
Backend Dev. 15 38 53 38 53 0
L
M Frontend Dev. 14 38 52 39 53 1
N Data Integration 10 38 48 43 53 5
Unit Testing 7 53 60 53 60 0
O
Integration Testing 8 60 68 60 68 0
P
Q Performance Testing 5 68 73 69 74 1
UAT 6 68 74 68 74 0
R
Bug Fixing 5 74 79 74 79 0
S
Technical Docs 5 74 79 74 79 0
T
U User Manual 4 74 78 75 79 1
Staging Deploy 4 79 83 79 83 0
V
Training 5 83 88 83 88 0
W
Production Deploy 3 88 91 88 91 0
X
Project Closure 4 91 95 91 95 0
Y
UET Lahore  PM
Table Course
9.1. 2026 ESEFLSLFSlack
Complete 21 Table (Critical activities in red)
Visualisation Platform for Government Datasets Project Management Report

Total Float per Activity

A
B
C
D
E
F
G
H
I
J
K
L
M
N
O
P
Q
R
S
T
U
V
W
X
Y

Total Float / Slack (Days)

0 1 2 3 4 5 6 7

Figure 9.1. Total Float per Activity  zero oat = critical path

Critical Path  Total Duration: 95 Working Days

A → B → C → D → F → H → I → L → O → P → R → S/T → V
→W→X→Y

16 activities with zero total oat. Any delay on this path directly extends the project
completion date.

Planning Design Dev Unit Test UAT Docs &Training PROJECT

Complete Complete Complete Done Complete Fix Done Done END

Days
0 7 14 18 28 38 45 53 60 68 79 88 91 95
Init/Plan/Req Design Development Test/Doc Deploy

Figure 9.2. Project Milestone Timeline (95 Working Days)

UET Lahore  PM Course 2026 22

10. Risk Management
10.1 Risk Breakdown Structure (RBS)
1.0 Project Risks

1.1 Technical 1.2 Schedule 1.3 Cost 1.4 Organisational 1.5 External 1.6 Security

Integration Scalability Library Req. Resource Budget Infra Cost Stakeholder Skills Regulatory Policy Data Injection
Complexity Constraints Deprecation
Volatility Unavailability Overrun Escalation Disengagement Gap Changes Shift Breach Vulnerabilities

Figure 10.1. Risk Breakdown Structure (RBS)

10.2 Risk Severity Matrix

Risk Scoring Formula
Risk Severity Score = Probability (15) × Impact (15)
Scores 15: Low 611: Medium 1219: High 2025: Very High

P\I
1 2 Minor 3 4 Signi- 5 Catas-
Negligible Moderate cant trophic

5 Very
High
5 10 15 20 25

4 High 4 8 12 16 20

3 Medium 3 6 9 12 15

2 Low 2 4 6 8 10

1 Very
Low
1 2 3 4 5

Table 10.1. Risk Severity Matrix

23
Visualisation Platform for Government Datasets Project Management Report

Risk Bubble Plot  12 Identied Risks

Catastrophic R-02

R-03 R-01

Signicant R-11
Impact

R-07

Moderate R-05

Minor

Negligible

ow h igh
yL Low ium Hig yH
Ver Med Ver
Probability
Figure 10.2. Risk Bubble Plot  Red = High Severity, Amber = Medium, Green = Low

10.3 Risk Register

ID
Description Category Prob Impact Severity Response Owner
Strategy

16
HIGH
R- Frequent req. Schedule 4 4 Formal change PM
01 changes delay control; freeze
analysis baseline after
sprint 1

R- Key dev. resigns Schedule 2 5 10 Cross-train team; PM

02 mid-project MED maintain
knowledge docs

R- Platform fails Technical 3 4 12 Load test from Backend

03 perf. targets HIGH Day 60; add
under load caching

R- SQL injection Security 2 5 10 Code review; QA

04 vulnerability MED OWASP
validation

R- Client can't Schedule 3 3 9 MED Written UAT BA

05 supply UAT commitment by
participants Day 30

UET Lahore  PM Course 2026 24

Visualisation Platform for Government Datasets Project Management Report

ID
Description Category Prob Impact Severity Response Owner
Strategy

R- Charting library Technical 2 3 6 LOW Use LTS Frontend

06 deprecated libraries; monitor
npm advisories

R- Budget overrun Cost 3 4 12 Change control PM

07 via scope creep HIGH board; track
actuals weekly

R- Cloud costs Cost 2 3 6 LOW AWS billing PM

08 exceed estimate alerts; reserved
pricing

R- Regulatory External 2 4 8 MED Modular privacy BA

09 redesign required controls from
design phase

R- Stakeholder Org. 3 3 9 MED Escalate to PM

10 sign-o delays Sponsor within 3
days

R- Legacy govt. API Technical 4 3 12 Prototype API in Backend

11 integration fails HIGH requirements
phase

R- Geospatial Technical 2 3 6 LOW Use veried Frontend

12 mapping GeoJSON
inaccurate boundary les

Table 10.2. Risk Register

Risk Severity Scores

20
Severity Score

15
High threshold
10

Risk ID
R-01R-02R-03R-04R-05R-06R-07R-08R-09R-10R-11R-12

Figure 10.3. Risk Severity Scores with High-Risk Threshold Line

UET Lahore  PM Course 2026 25

11. Conclusion
This report has presented a comprehensive project management plan for the Visualisation
Platform for Government Datasets (VPGD)  a web-based application designed to trans-
form how public-sector data is accessed, explored, and communicated. Through systematic
application of project management principles, the report has addressed all critical dimen-
sions of project planning, from scope denition to risk mitigation, and has produced a fully
integrated scheduling and control framework.

Scope and Objectives. The scope document delineates the platform's boundaries with
precision, specifying ten in-scope deliverables  including the dataset management console,
visualisation engine, RBAC system, and export module  while explicitly excluding native
mobile applications, AI-based predictions, and real-time streaming. This clarity is essen-
tial to preventing scope creep, managing stakeholder expectations, and maintaining budget
discipline.

WBS and Planning. The Work Breakdown Structure decomposes the total scope
across ten phases and four hierarchical levels into 42 discrete work packages, providing the
organisational backbone for the activity schedule and responsibility assignments.

Scheduling and Critical Path. The CPM analysis, performed through complete for-
ward and backward passes, identies the critical path as:

Critical Path
A → B → C → D → F → H → I → L → O → P → R → S/T → V
→W→X→Y
Total Project Duration: 95 Working Days
The analysis reveals that backend development (L, 15 days) is the single longest activity
and the primary bottleneck entering the testing phase. Non-critical activities  including
resource planning (E), DB schema design (J), frontend development (M), and user manual
preparation (U)  carry between 1 and 5 days of oat, providing scheduling exibility for
resource levelling.

Risk Management. Twelve signicant risks were identied across six RBS categories.
The four highest-severity risks  requirements volatility (R-01, score 16), backend API failure
(R-11, score 12), performance degradation (R-03, score 12), and budget overrun (R-07, score
12)  have been assigned concrete mitigation strategies and designated risk owners. The
risk register will be maintained as a living document, reviewed at every fortnightly steering
committee.

Overall Value. Provided the project team adheres to the dened 95-day schedule,
manages risks proactively, and enforces disciplined change control, the VPGD can be delivered
on time, within scope, and to the quality standards required by government stakeholders 
delivering measurable improvements in public transparency, data accessibility, and evidence-
based policy formulation.

26