Project Management Research Literature Review

This assignment presents a collection of scholarly articles focusing on diverse aspects of project management. The papers explore themes such as networking strategies in public construction projects, the impact of social media on project communication, project duration prediction models, software-defined networking, and the effectiveness of different project control methods. The review highlights key findings and trends within these specialized areas of project management.

Running head: FINAL PROJECT REPORT
Final Project Report
Name of the Student:
Student ID:
Name of the University:
Author’s note:

1FINAL PROJECT REPORT
Table of Contents
1. Introduction..................................................................................................................................2
2. Project Assumptions....................................................................................................................3
2a. WBS logic or dependencies...................................................................................................3
2b. Duration Costs and Resources...............................................................................................5
2c. Expected Time Calculation....................................................................................................8
2d. Project crashing for 10 days..................................................................................................9
3. Project Reports.............................................................................................................................9
3a. Project Baseline Report..........................................................................................................9
3b. Scenario Plans......................................................................................................................14
3c. Progress and Cash flow report.............................................................................................15
3d. EVM analysis for project.....................................................................................................19
3d. Milestone Report.................................................................................................................22
3e. Other Reports of Project......................................................................................................22
Bibliography..................................................................................................................................24

2FINAL PROJECT REPORT
1. Introduction
The following report is made on the development of the effective use of project
management tools and principles for the project of software development projects. The analysis
would allow the formation of the improved functional and development activities (Saxena and
Upadhyay 2016). The alignment of the effective project development principles would help in
listing the development of the effective operations. The system integrated project development
had implied for forming the various development strategy for implementing the improved
functional activities. The report would provide the inclusion of the various reports like baseline
reports cash flow reports, milestone reports, communication plan, and risk management reports.
Project Scope Statement
Project ID: #003458
Project Name: Tasks for software development project
Project Sponsor: Chris Jones
Project Mgr.: <<name of the student>>
Date: 10/02/18
Project Description: The project is an IT development project and the development of the
software is the basic deliverable for the project. Many organizations have been using the
development of the software implementation for improving their operations. The use of the
software development in the project would help in integrating the facilities of effective
communication management within the organization. The development of the effective
communication had helped in listing the facilities of complete software development of the
operations.
Project Scope: The project scope can be classified into two sections namely in-scope and out of
scope items. The project scope involves the development of the operations for implementing the
software development for the organization. In scope-> The in scope items of the project are
documents like charter and initiation documentation, plan development for scope,
communication, development, deployment, maintenance, communication, quality, and risk
management, and designing UI, use case, database, and permissions. Out of scope-> The out of

3FINAL PROJECT REPORT
scope items of the project are the transportation requirements, system change implementation,
test plan, and change management.
Deliverables: The deliverables for the project are,
S. No. Deliverable Start date Finish date
1 Development of project charter Wed 2/21/18 Tue 2/27/18
2 Project Initiation Documentation Wed 2/28/18 Tue 3/6/18
3 Various Plans for project Thu 3/8/18 Thu 4/12/18
4 Develop use cases Sun 4/15/18 Tue 4/17/18
5 Create data and hardware
architecture Wed 4/18/18 Tue 4/24/18
6 Software System Wed 6/6/18 Wed 6/6/18
Acceptance Criteria: Completion of project in the expected time of within 3-4 months
Overall cost of the project would be AED100,000.00
Design developed would be feasible and the test results would be favorable for utilization
Project Assumptions: The project assumptions include the following points,
Resources required for the project would be available for being used for effective operations.
Project would include the modification of the activities for forming the development of intrusive
development
Project schedule is developed for ensuring that the development of the activities would involve
the listing the activities of the project
Project Constraints: The time, cost, and technology development are the constraints of the
project. The use of effective technology development is the factors of constraints for the project.
Table 1: Project Scope Statement
2. Project Assumptions
2a. WBS logic or dependencies
The WBS logic is formed for the development of the task dependencies and the
alignment of the operations in a sequential method. The alignment of the project is formed for

4FINAL PROJECT REPORT
ensuring that the project is listed for the development of the effective communication. The
dependencies of the WBS is shown in the table below,
WBS Task Name Predecessors Successors
1 Initiation Phase
1.1 Requirement Analysis 3
1.2 Scope Development 2 4
1.3 Development of project charter 3 5
1.4 Project Initiation Documentation 4 6
1.5 Project Kick off meeting 5 8
2 Planning Phase
2.1 Development Planning 6 9
2.2 Deployment Planning 8 10
2.3 Maintenance Planning 9 11
2.4 Project Planning 10 12
2.5 Communication Planning 11 13
2.6 Quality Planning 12 14
2.7 Risk Management Planning 13 15
2.8 Procurement Planning 14 16
2.9 Plans Approval 15 19
3 Execution Phase
3.1 Manage Design
3.1.1 Develop use cases 16 20
3.1.2 Create data and hardware architecture 19 21
3.1.3 Perform impact analysis 20 22
3.1.4 Develop migration strategy 21 24
3.2 Design product
3.2.1 Design UI 22 25
3.2.2 Design objects and workflow 24 26
3.2.3 Design rules and middle tier 25 27
3.2.4 Design database 26 28
3.2.5 Design connectivity with other systems 27 29
3.2.6 Design permissions 28 30
3.2.7 Product design approved 29
Table 2: Project Dependencies
The project developed is based on the traditional waterfall approach for project plan
development as it would allow the formation of the effective and improved communication for
the operation. The linear dependency would allow the users for undertaking the project activities

5FINAL PROJECT REPORT
step by step for completion of the effective and improved operations. The traditional waterfall
model is highly responsible for forming the effective and linear communication among the
project team members (Alshamrani and Bahattab 2015). The alignment of the activities had
supported the alignment of the cohesive and effective communication for the users. The
deployment of the effective development model would allow the formation of the effective
deployment of the operations. The alignment of the effective and improved operations would be
possible with the help of implementing waterfall model integration.
2b. Duration Costs and Resources
The project durations is shown in the table below along with the details of the tasks
required for the project and their individual duration,
WBS Task Name Duration Start Finish
0 Tasks for software development project 83 days Mon 2/12/18 Thu 6/7/18
1 Initiation Phase 18 days Mon 2/12/18 Thu 3/8/18
1.1 Requirement Analysis 3 days Mon 2/12/18 Thu 2/15/18
1.2 Scope Development 4 days Thu 2/15/18 Wed 2/21/18
1.3 Development of project charter 5 days Wed 2/21/18 Wed 2/28/18
1.4 Project Initiation Documentation 5 days Wed 2/28/18 Wed 3/7/18
1.5 Project Kick off meeting 1 day Wed 3/7/18 Thu 3/8/18
2 Planning Phase 26 days Thu 3/8/18 Sun 4/15/18
2.1 Development Planning 3 days Thu 3/8/18 Tue 3/13/18
2.2 Deployment Planning 3 days Tue 3/13/18 Sun 3/18/18
2.3 Maintenance Planning 3 days Sun 3/18/18 Wed 3/21/18
2.4 Project Planning 3 days Wed 3/21/18 Mon 3/26/18
2.5 Communication Planning 3 days Mon 3/26/18 Thu 3/29/18
2.6 Quality Planning 3 days Thu 3/29/18 Tue 4/3/18
2.7 Risk Management Planning 3 days Tue 4/3/18 Sun 4/8/18
2.8 Procurement Planning 3 days Sun 4/8/18 Wed 4/11/18
2.9 Plans Approval 2 days Wed 4/11/18 Sun 4/15/18
3 Execution Phase 39 days Sun 4/15/18 Thu 6/7/18
3.1 Manage Design 15 days Sun 4/15/18 Sun 5/6/18
3.1.1 Develop use cases 3 days Sun 4/15/18 Wed 4/18/18
3.1.2 Create data and hardware architecture 5 days Wed 4/18/18 Wed 4/25/18
3.1.3 Perform impact analysis 3 days Wed 4/25/18 Mon 4/30/18

6FINAL PROJECT REPORT
3.1.4 Develop migration strategy 4 days Mon 4/30/18 Sun 5/6/18
3.2 Design product 24 days Sun 5/6/18 Thu 6/7/18
3.2.1 Design UI 3 days Sun 5/6/18 Wed 5/9/18
3.2.2 Design objects and workflow 5 days Wed 5/9/18 Wed 5/16/18
3.2.3 Design rules and middle tier 5 days Wed 5/16/18 Wed 5/23/18
3.2.4 Design database 4 days Wed 5/23/18 Tue 5/29/18
3.2.5 Design connectivity with other systems 4 days Tue 5/29/18 Mon 6/4/18
3.2.6 Design permissions 2 days Mon 6/4/18 Wed 6/6/18
3.2.7 Product design approved 1 day Wed 6/6/18 Thu 6/7/18
Table 3: Project Durations
The cost expenses for the project is shown below,
WBS Resource Names Cost
0 AED100,000.00
1 AED11,280.00
1.1 Analyst AED1,920.00
1.2 Analyst AED2,560.00
1.3 Documenter AED2,800.00
1.4 Documenter AED2,800.00
1.5 Project Manager AED1,200.00
2 AED21,840.00
2.1 Planner AED1,920.00
2.2 IT Engineer AED3,360.00
2.3 IT Engineer AED3,360.00
2.4 Planner AED1,920.00
2.5 Planner AED1,920.00
2.6 Quality Head AED2,880.00
2.7 Risk Analyst AED2,160.00
2.8 Planner AED1,920.00
2.9 Project Manager AED2,400.00
3 AED66,880.00
3.1 AED24,720.00
3.1.1 Junior Engineer AED2,400.00
3.1.2 Senior Engineer, Hardware[1] AED14,480.00
3.1.3 IT Engineer AED3,360.00
3.1.4 IT Engineer AED4,480.00
3.2 AED42,160.00
3.2.1 Junior Engineer, UI tools[1] AED6,400.00
3.2.2 Senior Engineer, Programming tools[1] AED9,700.00
3.2.3 Junior Engineer AED4,000.00

7FINAL PROJECT REPORT
3.2.4 Senior Engineer, Database[1] AED10,160.00
3.2.5 Junior Engineer, Network
Connection[1] AED8,700.00
3.2.6 Senior Engineer AED2,080.00
3.2.7 IT Engineer AED1,120.00
Table 4: Project Cost Expenses
The resource usage of the project is shown below,
Resource Name Activities Used in Duration/Quantity
Analyst Requirement Analysis 24 hrs
Scope Development 32 hrs
Documenter Development of project charter 40 hrs
Project Initiation Documentation 40 hrs
Project Manager Project Kick off meeting 8 hrs
Plans Approval 16 hrs
Planner Development Planning 24 hrs
Project Planning 24 hrs
Communication Planning 24 hrs
Procurement Planning 24 hrs
Planner Deployment Planning 24 hrs
Maintenance Planning 24 hrs
Develop migration strategy 32 hrs
Product design approved 8 hrs
Perform impact analysis 24 hrs
Quality head Quality Planning 24 hrs
Risk Analyst Risk Management Planning 24 hrs
Junior Engineer Develop use cases 24 hrs
Design rules and middle tier 40 hrs
Design connectivity with other systems 32 hrs
Design UI 24 hrs
Senior engineer Create data and hardware architecture 40 hrs
Design database 32 hrs
Design permissions 16 hrs
Design objects and workflow 40 hrs
Hardware Create data and hardware architecture 1
Database Design database 1
UI tools Design UI 1
Programming Tools Design objects and workflow 1
Network Connection Design connectivity with other systems 1
Table 5: Project Resource Usage

8FINAL PROJECT REPORT
2c. Expected Time Calculation
Project Name: Tasks for software development project
Activity Pessimisti
c (P)
Most
Likely
(M)
Optimisti
c (O)
Expected activity
duration
E=(P+4M+O)/6
Variation
V=((P-
O)/6)^2
Requirement Analysis 3 3 3 3.00 0.00
Scope Development 4 4 4 4.00 0.00
Development of project charter 5 5 5 5.00 0.00
Project Initiation Documentation 5 5 5 5.00 0.00
Project Kick off meeting 1 1 1 1.00 0.00
Development Planning 6 4 3 4.17 0.25
Deployment Planning 7 5 3 5.00 0.44
Maintenance Planning 5 3 3 3.33 0.11
Project Planning 6 4 3 4.17 0.25
Communication Planning 7 5 3 5.00 0.44
Quality Planning 7 5 3 5.00 0.44
Risk Management Planning 6 4 3 4.17 0.25
Procurement Planning 5 3 3 3.33 0.11
Plans Approval 5 3 2 3.17 0.25
Develop use cases 3 3 3 3.00 0.00
Create data and hardware
architecture
5 5 5 5.00 0.00
Perform impact analysis 3 3 3 3.00 0.00
Develop migration strategy 4 4 4 4.00 0.00
Design UI 3 3 3 3.00 0.00

9FINAL PROJECT REPORT
Design objects and workflow 5 5 5 5.00 0.00
Design rules and middle tier 5 5 5 5.00 0.00
Design database 4 4 4 4.00 0.00
Design connectivity with other
systems
4 4 4 4.00 0.00
Design permissions 2 2 2 2.00 0.00
Product design approved 1 1 1 1.00 0.00
Total 111 93 83 94.33
Table 6: Project 3 Point Estimation
2d. Project crashing for 10 days
The crashing of the project for 10 days and decreasing its duration for getting effective
and improved communication implementation for the users would require the decreasing of the
expected time of the project by 10 days. It would increase the overall cost budget as more
resource would be required for completing the activity of the project in shorter time (Mortazavi
Nejad and Tareghian 2017). The alignment of the activities is aligned for forming the effective
and improved operations for the users.
3. Project Reports
3a. Project Baseline Report
Project Start Date Mon 2/12/18
Project End date Wed 6/6/18

10FINAL PROJECT REPORT
Planned Costs
WBS Task Name Cost
1 Initiation Phase AED11,280.00
2 Planning Phase AED21,840.00
3 Execution Phase AED66,880.00
3.1 Manage Design AED24,720.00
3.2 Design product AED42,160.00
Milestones Project Kick off meeting - Wed 3/7/18
Plans Approval- Thu 4/12/18
Perform impact analysis - Fri 4/27/18
Product design approved- Wed 6/6/18
Resources
Resource Name Type
Analyst Work
Documenter Work
Project Manager Work
Planner Work
IT Engineer Work
Quality Head Work
Risk Analyst Work
Junior Engineer Work
Senior Engineer Work
Hardware Material
Database Material
UI tools Material
Programming tools Material
Network Connection Material
Table 7: Project baseline report
Project Schedule Table: The project schedule table showing project start and finish day along
with planned duration is shown as,
WBS Task Name Duration Start Finish Predecessors Resource Names
0 Tasks for software
development project 83 days Mon
2/12/18
Thu
6/7/18
1 Initiation Phase 18 days Mon Thu

11FINAL PROJECT REPORT
2/12/18 3/8/18
1.1 Requirement
Analysis 3 days Mon
2/12/18
Thu
2/15/18 Analyst
1.2 Scope
Development 4 days Thu
2/15/18
Wed
2/21/18 2 Analyst
1.3 Development of
project charter 5 days Wed
2/21/18
Wed
2/28/18 3 Documenter
1.4 Project Initiation
Documentation 5 days Wed
2/28/18
Wed
3/7/18 4 Documenter
1.5 Project Kick off
meeting 1 day Wed
3/7/18
Thu
3/8/18 5 Project Manager
2 Planning Phase 26 days Thu
3/8/18
Sun
4/15/18
2.1 Development
Planning 3 days Thu
3/8/18
Tue
3/13/18 6 Planner
2.2 Deployment
Planning 3 days Tue
3/13/18
Sun
3/18/18 8 IT Engineer
2.3 Maintenance
Planning 3 days Sun
3/18/18
Wed
3/21/18 9 IT Engineer
2.4 Project Planning 3 days Wed
3/21/18
Mon
3/26/18 10 Planner
2.5 Communication
Planning 3 days Mon
3/26/18
Thu
3/29/18 11 Planner
2.6 Quality Planning 3 days Thu
3/29/18
Tue
4/3/18 12 Quality Head
2.7 Risk Management
Planning 3 days Tue
4/3/18
Sun
4/8/18 13 Risk Analyst
2.8 Procurement
Planning 3 days Sun
4/8/18
Wed
4/11/18 14 Planner
2.9 Plans Approval 2 days Wed
4/11/18
Sun
4/15/18 15 Project Manager
3 Execution Phase 39 days Sun
4/15/18
Thu
6/7/18
3.1 Manage Design 15 days Sun
4/15/18
Sun
5/6/18
3.1.1 Develop use
cases 3 days Sun
4/15/18
Wed
4/18/18 16 Junior Engineer
3.1.2 Create data and
hardware architecture 5 days Wed
4/18/18
Wed
4/25/18 19 Senior
Engineer,Hardware[1]
3.1.3 Perform impact
analysis 3 days Wed
4/25/18
Mon
4/30/18 20 IT Engineer
3.1.4 Develop
migration strategy 4 days Mon
4/30/18
Sun
5/6/18 21 IT Engineer

12FINAL PROJECT REPORT
3.2 Design product 24 days Sun
5/6/18
Thu
6/7/18
3.2.1 Design UI 3 days Sun
5/6/18
Wed
5/9/18 22 Junior Engineer,UI
tools[1]
3.2.2 Design objects
and workflow 5 days Wed
5/9/18
Wed
5/16/18 24
Senior
Engineer,Programming
tools[1]
3.2.3 Design rules and
middle tier 5 days Wed
5/16/18
Wed
5/23/18 25 Junior Engineer
3.2.4 Design database 4 days Wed
5/23/18
Tue
5/29/18 26 Senior
Engineer,Database[1]
3.2.5
Design
connectivity with
other systems
4 days Tue
5/29/18
Mon
6/4/18 27 Junior Engineer,Network
Connection[1]
3.2.6 Design
permissions 2 days Mon
6/4/18
Wed
6/6/18 28 Senior Engineer
3.2.7 Product design
approved 1 day Wed
6/6/18
Thu
6/7/18 29 IT Engineer
Table 8: Project Schedule table

13FINAL PROJECT REPORT
Project Gantt chart: The project Gantt chart is shown below,
ID Task
Mode
WBS Task Name Duration Start Finish
0 0 Tasks for software
development project
83 days Mon
2/12/18
Thu 6/7/18
1 1 Initiation Phase 18 days Mon 2/12/18Thu 3/8/18
2 1.1 Requirement Analysis 3 days Mon 2/12/18Thu 2/15/18
3 1.2 Scope Development 4 days Thu 2/15/18 Wed 2/21/18
4 1.3 Development of project charter5 days Wed 2/21/18Wed 2/28/18
5 1.4 Project Initiation Documentation5 days Wed 2/28/18Wed 3/7/18
6 1.5 Project Kick off meeting 1 day Wed 3/7/18 Thu 3/8/18
7 2 Planning Phase 26 days Thu 3/8/18 Sun 4/15/18
8 2.1 Development Planning 3 days Thu 3/8/18 Tue 3/13/18
9 2.2 Deployment Planning 3 days Tue 3/13/18 Sun 3/18/18
10 2.3 Maintenance Planning 3 days Sun 3/18/18 Wed 3/21/18
11 2.4 Project Planning 3 days Wed 3/21/18Mon 3/26/18
12 2.5 Communication Planning 3 days Mon 3/26/18 Thu 3/29/18
13 2.6 Quality Planning 3 days Thu 3/29/18 Tue 4/3/18
14 2.7 Risk Management Planning 3 days Tue 4/3/18 Sun 4/8/18
15 2.8 Procurement Planning 3 days Sun 4/8/18 Wed 4/11/18
16 2.9 Plans Approval 2 days Wed 4/11/18Sun 4/15/18
17 3 Execution Phase 39 days Sun 4/15/18 Thu 6/7/18
18 3.1 Manage Design 15 days Sun 4/15/18 Sun 5/6/18
19 3.1.1 Develop use cases 3 days Sun 4/15/18 Wed 4/18/18
20 3.1.2 Create data and
hardware architecture
5 days Wed
4/18/18
Wed
4/25/18
21 3.1.3 Perform impact analysis 3 days Wed 4/25/18Mon 4/30/18
22 3.1.4 Develop migration strategy4 days Mon 4/30/18Sun 5/6/18
23 3.2 Design product 24 days Sun 5/6/18 Thu 6/7/18
24 3.2.1 Design UI 3 days Sun 5/6/18 Wed 5/9/18
25 3.2.2 Design objects and workflow5 days Wed 5/9/18 Wed 5/16/18
26 3.2.3 Design rules and middle tier5 days Wed 5/16/18Wed 5/23/18
27 3.2.4 Design database 4 days Wed 5/23/18Tue 5/29/18
28 3.2.5 Design connectivity with
other systems
4 days Tue 5/29/18 Mon
6/4/18
29 3.2.6 Design permissions 2 days Mon 6/4/18 Wed 6/6/18
30 3.2.7 Product design approved1 day Wed 6/6/18 Thu 6/7/18
Analyst
Analyst
Documenter
Documenter
Project Manager
Planner
IT Engineer
IT Engineer
Planner
Planner
Quality Head
Risk Analyst
Planner
Project Manager
Junior Engineer
Senior Engineer,Hardware[1]
IT Engineer
IT Engineer
Junior Engineer,UI tools[1]
Senior Engineer,Programming tools[1]
Junior Engineer
Senior Engineer,Database[1]
Junior Engineer,Network Connection[1]
Senior Engineer
IT Engineer
T F S S M T W T F S S M T W
Jan 7, '18 Feb 11, '18 Mar 18, '18 Apr 22, '18 May 27, '18 Jul 1, '18 Aug 5, '18
Figure 1: Gantt chart
Project Time Phased Budget:-
February 2018 March 2018 April 2018 May 2018 June 2018
0.00 . .د إ
5,000.00 . .د إ
10,000.00 . .د إ
15,000.00 . .د إ
20,000.00 . .د إ
25,000.00 . .د إ
30,000.00 . .د إ
35,000.00 . .د إ
40,000.00 . .د إ
45,000.00 . .د إ
7,770.00 . .د إ
16,830.00 . .د إ
29,740.00 . .د إ
40,013.13 . .د إ
5,646.88 . .د إ
Cost
Cost
Figure 2: Time Phase budget
Project Resource Phased Budget
Analyst
Documenter
Project Manager
Planner
IT Engineer
Quality Head
Risk Analyst
Junior Engineer
Senior Engineer
Hardware
Database
UI tools
Programming tools
Network Connection
0.00 . .د إ
4,000.00 . .د إ
8,000.00 . .د إ
12,000.00 . .د إ
16,000.00 . .د إ
4,480.00 . .د إ 5,600.00 . .د إ 3,600.00 . .د إ
7,680.00 . .د إ
15,680.00 . .د إ
2,880.00 . .د إ 2,160.00 . .د إ
12,000.00 . .د إ
16,640.00 . .د إ
9,280.00 . .د إ
6,000.00 . .د إ 4,000.00 . .د إ 4,500.00 . .د إ 5,500.00 . .د إ
Cost
Cost
Figure 3: Resource Usage

14FINAL PROJECT REPORT
Project Network Diagram
3b. Scenario Plans
The project cash flow diagrams for the three scenarios (pessimistic, most likely, and optimistic) is shown below,
Pessimistic Scenario:
Analyst
Documenter
Project Manager
Planner
IT Engineer
Quality Head
Risk Analyst
Junior Engineer
Senior Engineer
Hardware
Database
UI tools
Programming tools
Network Connection
- . .د إ
5,000.00 . .د إ
10,000.00 . .د إ
15,000.00 . .د إ
20,000.00 . .د إ
25,000.00 . .د إ
4,480.00 . .د إ
5,600.00 . .د إ
7,200.00 . .د إ
15,360.00 . .د إ
22,400.00 . .د إ
6,720.00 . .د إ
4,320.00 . .د إ
12,000.00 . .د إ
16,640.00 . .د إ
9,280.00 . .د إ
6,000.00 . .د إ
4,000.00 . .د إ4,500.00 . .د إ
5,500.00 . .د إ
Cost of Resources
Cost of Resources
Figure 4: Cost of Resources (Pessimistic Scenario)
Most Likely Scenario:
Analyst
Documenter
Project Manager
Planner
IT Engineer
Quality Head
Risk Analyst
Junior Engineer
Senior Engineer
Hardware
Database
UI tools
Programming tools
Network Connection
- . .د إ
2,000.00 . .د إ
4,000.00 . .د إ
6,000.00 . .د إ
8,000.00 . .د إ
10,000.00 . .د إ
12,000.00 . .د إ
14,000.00 . .د إ
16,000.00 . .د إ
18,000.00 . .د إ
20,000.00 . .د إ
4,480.00 . .د إ
5,600.00 . .د إ
4,800.00 . .د إ
10,240.00 . .د إ
17,920.00 . .د إ
4,800.00 . .د إ
2,880.00 . .د إ
12,000.00 . .د إ
16,640.00 . .د إ
9,280.00 . .د إ
6,000.00 . .د إ
4,000.00 . .د إ4,500.00 . .د إ
5,500.00 . .د إ
Cost of Resources
Cost of Resources
Figure 5: Cost of Resources (Most Likely Scenario)
Optimistic Scenario:

15FINAL PROJECT REPORT
Analyst
Documenter
Project Manager
Planner
IT Engineer
Quality Head
Risk Analyst
Junior Engineer
Senior Engineer
Hardware
Database
UI tools
Programming tools
Network Connection
- . .د إ
2,000.00 . .د إ
4,000.00 . .د إ
6,000.00 . .د إ
8,000.00 . .د إ
10,000.00 . .د إ
12,000.00 . .د إ
14,000.00 . .د إ
16,000.00 . .د إ
18,000.00 . .د إ
4,480.00 . .د إ
5,600.00 . .د إ
3,600.00 . .د إ
7,680.00 . .د إ
15,680.00 . .د إ
2,880.00 . .د إ
2,160.00 . .د إ
12,000.00 . .د إ
16,640.00 . .د إ
9,280.00 . .د إ
6,000.00 . .د إ
4,000.00 . .د إ4,500.00 . .د إ
5,500.00 . .د إ
Cost of Resources
Cost of Resources
Figure 6: Cost of Resources (Optimistic Scenario)
3c. Progress and Cash flow report
The project Gantt chart, time phased budget, and activity time graph for all three scenarios (pessimistic, most likely, and optimistic) is shown below,
Pessimistic Scenario:
Project Gantt chart:-
ID Task
Mode
WBS Task Name Duration Start Finish
0 0 Tasks for software
development project
111 days Mon
2/12/18
Tue 7/17/18
1 1 Initiation Phase 18 days Mon 2/12/18Thu 3/8/18
2 1.1 Requirement Analysis 3 days Mon 2/12/18Thu 2/15/18
3 1.2 Scope Development 4 days Thu 2/15/18 Wed 2/21/18
4 1.3 Development of project charter5 days Wed 2/21/18Wed 2/28/18
5 1.4 Project Initiation Documentation5 days Wed 2/28/18Wed 3/7/18
6 1.5 Project Kick off meeting 1 day Wed 3/7/18 Thu 3/8/18
7 2 Planning Phase 54 days Thu 3/8/18 Wed 5/23/18
8 2.1 Development Planning 6 days Thu 3/8/18 Sun 3/18/18
9 2.2 Deployment Planning 7 days Sun 3/18/18 Tue 3/27/18
10 2.3 Maintenance Planning 5 days Tue 3/27/18 Tue 4/3/18
11 2.4 Project Planning 6 days Tue 4/3/18 Wed 4/11/18
12 2.5 Communication Planning 7 days Wed 4/11/18 Sun 4/22/18
13 2.6 Quality Planning 7 days Sun 4/22/18 Tue 5/1/18
14 2.7 Risk Management Planning 6 days Tue 5/1/18 Wed 5/9/18
15 2.8 Procurement Planning 5 days Wed 5/9/18 Wed 5/16/18
16 2.9 Plans Approval 5 days Wed 5/16/18Wed 5/23/18
17 3 Execution Phase 39 days Wed 5/23/18Tue 7/17/18
18 3.1 Manage Design 15 days Wed 5/23/18Wed 6/13/18
19 3.1.1 Develop use cases 3 days Wed 5/23/18Mon 5/28/18
20 3.1.2 Create data and
hardware architecture
5 days Mon
5/28/18
Mon 6/4/18
21 3.1.3 Perform impact analysis 3 days Mon 6/4/18 Thu 6/7/18
22 3.1.4 Develop migration strategy4 days Thu 6/7/18 Wed 6/13/18
23 3.2 Design product 24 days Wed 6/13/18Tue 7/17/18
24 3.2.1 Design UI 3 days Wed 6/13/18 Mon 6/18/18
25 3.2.2 Design objects and workflow5 days Mon 6/18/18Mon 6/25/18
26 3.2.3 Design rules and middle tier5 days Mon 6/25/18Mon 7/2/18
27 3.2.4 Design database 4 days Mon 7/2/18 Sun 7/8/18
28 3.2.5 Design connectivity with
other systems
4 days Sun 7/8/18 Thu 7/12/18
Analyst
Analyst
Documenter
Documenter
Project Manager
Planner
IT Engineer
IT Engineer
Planner
Planner
Quality Head
Risk Analyst
Planner
Project Manager
Junior Engineer
Senior Engineer,Hardware[1]
IT Engineer
IT Engineer
Junior Engineer,UI tools[1]
Senior Engineer,Programming tools[1]
Junior Engineer
Senior Engineer,Database[1]
Junior Engineer,Network Connection[1]
T F S S M T W T F S S M T W
Jan 7, '18 Feb 11, '18 Mar 18, '18 Apr 22, '18 May 27, '18 Jul 1, '18 Aug 5, '18
Figure 7: Gantt chart (Pessimistic Scenario)
Project Time Graph:-

16FINAL PROJECT REPORT
Requirement Analysis
Scope Development
Development of project charter
Project Initiation Documentation
Project Kick off meeting
Development Planning
Deployment Planning
Maintenance Planning
Project Planning
Communication Planning
Quality Planning
Risk Management Planning
Procurement Planning
Plans Approval
Develop use cases
Create data and hardware architecture
Perform impact analysis
Develop migration strategy
Design UI
Design objects and workflow
Design rules and middle tier
Design database
Design connectivity with other systems
Design permissions
Product design approved
0
1
2
3
4
5
6
7
8
3
4
5 5
1
6
7
5
6
7 7
6
5 5
3
5
3
4
3
5 5
4 4
2
1
Activity Duration (in days)
Activity Duration (in days)
Figure 8: Project Time Graph (Pessimistic Scenario)
Project Time Phased Budget:-
February 2018 March 2018 April 2018 May 2018 June 2018
0.00 . .د إ
5,000.00 . .د إ
10,000.00 . .د إ
15,000.00 . .د إ
20,000.00 . .د إ
25,000.00 . .د إ
30,000.00 . .د إ
35,000.00 . .د إ
7,770.00 . .د إ
18,410.00 . .د إ 17,300.00 . .د إ
27,262.00 . .د إ
30,298.00 . .د إ
Cost
Cost
Figure 9: Time Phased Budget (Pessimistic Scenario)
Most Likely Scenario:
Project Gantt chart:-

17FINAL PROJECT REPORT
ID Task
Mode
WBS Task Name Duration Start Finish
0 0 Tasks for software
development project
93 days Mon
2/12/18
Thu
6/21/18
1 1 Initiation Phase 18 days Mon 2/12/18Thu 3/8/18
2 1.1 Requirement Analysis 3 days Mon 2/12/18Thu 2/15/18
3 1.2 Scope Development 4 days Thu 2/15/18 Wed 2/21/18
4 1.3 Development of project charter5 days Wed 2/21/18Wed 2/28/18
5 1.4 Project Initiation Documentation5 days Wed 2/28/18Wed 3/7/18
6 1.5 Project Kick off meeting 1 day Wed 3/7/18 Thu 3/8/18
7 2 Planning Phase 36 days Thu 3/8/18 Sun 4/29/18
8 2.1 Development Planning 4 days Thu 3/8/18 Wed 3/14/18
9 2.2 Deployment Planning 5 days Wed 3/14/18Wed 3/21/18
10 2.3 Maintenance Planning 3 days Wed 3/21/18Mon 3/26/18
11 2.4 Project Planning 4 days Mon 3/26/18Sun 4/1/18
12 2.5 Communication Planning 5 days Sun 4/1/18 Sun 4/8/18
13 2.6 Quality Planning 5 days Sun 4/8/18 Sun 4/15/18
14 2.7 Risk Management Planning 4 days Sun 4/15/18 Thu 4/19/18
15 2.8 Procurement Planning 3 days Thu 4/19/18 Tue 4/24/18
16 2.9 Plans Approval 3 days Tue 4/24/18 Sun 4/29/18
17 3 Execution Phase 39 days Sun 4/29/18 Thu 6/21/18
18 3.1 Manage Design 15 days Sun 4/29/18 Sun 5/20/18
19 3.1.1 Develop use cases 3 days Sun 4/29/18 Wed 5/2/18
20 3.1.2 Create data and
hardware architecture
5 days Wed 5/2/18 Wed
5/9/18
21 3.1.3 Perform impact analysis 3 days Wed 5/9/18 Mon 5/14/18
22 3.1.4 Develop migration strategy4 days Mon 5/14/18Sun 5/20/18
23 3.2 Design product 24 days Sun 5/20/18 Thu 6/21/18
24 3.2.1 Design UI 3 days Sun 5/20/18 Wed 5/23/18
25 3.2.2 Design objects and workflow5 days Wed 5/23/18Wed 5/30/18
26 3.2.3 Design rules and middle tier5 days Wed 5/30/18Wed 6/6/18
27 3.2.4 Design database 4 days Wed 6/6/18 Tue 6/12/18
28 3.2.5 Design connectivity with
other systems
4 days Tue 6/12/18 Mon
6/18/18
29 3.2.6 Design permissions 2 days Mon 6/18/18Wed 6/20/18
30 3.2.7 Product design approved1 day Wed 6/20/18Thu 6/21/18
Analyst
Analyst
Documenter
Documenter
Project Manager
Planner
IT Engineer
IT Engineer
Planner
Planner
Quality Head
Risk Analyst
Planner
Project Manager
Junior Engineer
Senior Engineer,Hardware[1]
IT Engineer
IT Engineer
Junior Engineer,UI tools[1]
Senior Engineer,Programming tools[1]
Junior Engineer
Senior Engineer,Database[1]
Junior Engineer,Network Connection[1
Senior Engineer
IT Engineer
T F S S M T W T F S S M
Jan 7, '18 Feb 11, '18 Mar 18, '18 Apr 22, '18 May 27, '18 Jul 1, '18
Figure 10: Gantt chart (Most Likely Scenario)
Project Time Graph:-
Requirement Analysis
Scope Development
Development of project charter
Project Initiation Documentation
Project Kick off meeting
Development Planning
Deployment Planning
Maintenance Planning
Project Planning
Communication Planning
Quality Planning
Risk Management Planning
Procurement Planning
Plans Approval
Develop use cases
Create data and hardware architecture
Perform impact analysis
Develop migration strategy
Design UI
Design objects and workflow
Design rules and middle tier
Design database
Design connectivity with other systems
Design permissions
Product design approved
0
1
2
3
4
5
6
3
4
5 5
1
4
5
3
4
5 5
4
3 3 3
5
3
4
3
5 5
4 4
2
1
Activity Duration (in days)
Activity Duration (in days)
Figure 11: Project Time Graph (Most Likely Scenario)
Project Time Phased Budget:-

18FINAL PROJECT REPORT
February 2018 March 2018 April 2018 May 2018 June 2018
0.00 . .د إ
5,000.00 . .د إ
10,000.00 . .د إ
15,000.00 . .د إ
20,000.00 . .د إ
25,000.00 . .د إ
30,000.00 . .د إ
35,000.00 . .د إ
40,000.00 . .د إ
45,000.00 . .د إ
7,770.00 . .د إ
17,510.00 . .د إ 17,980.00 . .د إ
40,820.00 . .د إ
24,560.00 . .د إ
Cost
Cost
Figure 12: Time Phased Budget (Most Likely Scenario)
Optimistic Scenario:
Project Gantt chart:-
ID Task
Mode
WBS Task Name Duration Start Finish
0 0 Tasks for software
development project
83 days Mon
2/12/18
Thu 6/7/18
1 1 Initiation Phase 18 days Mon 2/12/18Thu 3/8/18
2 1.1 Requirement Analysis 3 days Mon 2/12/18Thu 2/15/18
3 1.2 Scope Development 4 days Thu 2/15/18 Wed 2/21/18
4 1.3 Development of project charter5 days Wed 2/21/18Wed 2/28/18
5 1.4 Project Initiation Documentation5 days Wed 2/28/18Wed 3/7/18
6 1.5 Project Kick off meeting 1 day Wed 3/7/18 Thu 3/8/18
7 2 Planning Phase 26 days Thu 3/8/18 Sun 4/15/18
8 2.1 Development Planning 3 days Thu 3/8/18 Tue 3/13/18
9 2.2 Deployment Planning 3 days Tue 3/13/18 Sun 3/18/18
10 2.3 Maintenance Planning 3 days Sun 3/18/18 Wed 3/21/18
11 2.4 Project Planning 3 days Wed 3/21/18Mon 3/26/18
12 2.5 Communication Planning 3 days Mon 3/26/18 Thu 3/29/18
13 2.6 Quality Planning 3 days Thu 3/29/18 Tue 4/3/18
14 2.7 Risk Management Planning 3 days Tue 4/3/18 Sun 4/8/18
15 2.8 Procurement Planning 3 days Sun 4/8/18 Wed 4/11/18
16 2.9 Plans Approval 2 days Wed 4/11/18Sun 4/15/18
17 3 Execution Phase 39 days Sun 4/15/18 Thu 6/7/18
18 3.1 Manage Design 15 days Sun 4/15/18 Sun 5/6/18
19 3.1.1 Develop use cases 3 days Sun 4/15/18 Wed 4/18/18
20 3.1.2 Create data and
hardware architecture
5 days Wed
4/18/18
Wed
4/25/18
21 3.1.3 Perform impact analysis 3 days Wed 4/25/18Mon 4/30/18
22 3.1.4 Develop migration strategy4 days Mon 4/30/18Sun 5/6/18
23 3.2 Design product 24 days Sun 5/6/18 Thu 6/7/18
24 3.2.1 Design UI 3 days Sun 5/6/18 Wed 5/9/18
25 3.2.2 Design objects and workflow5 days Wed 5/9/18 Wed 5/16/18
26 3.2.3 Design rules and middle tier5 days Wed 5/16/18Wed 5/23/18
27 3.2.4 Design database 4 days Wed 5/23/18Tue 5/29/18
28 3.2.5 Design connectivity with
other systems
4 days Tue 5/29/18 Mon
6/4/18
29 3.2.6 Design permissions 2 days Mon 6/4/18 Wed 6/6/18
30 3.2.7 Product design approved1 day Wed 6/6/18 Thu 6/7/18
Analyst
Analyst
Documenter
Documenter
Project Manager
Planner
IT Engineer
IT Engineer
Planner
Planner
Quality Head
Risk Analyst
Planner
Project Manager
Junior Engineer
Senior Engineer,Hardware[1]
IT Engineer
IT Engineer
Junior Engineer,UI tools[1]
Senior Engineer,Programming tools[1]
Junior Engineer
Senior Engineer,Database[1]
Junior Engineer,Network Connection[1]
Senior Engineer
IT Engineer
T F S S M T W T F S S M T W
Jan 7, '18 Feb 11, '18 Mar 18, '18 Apr 22, '18 May 27, '18 Jul 1, '18 Aug 5, '18
Figure 13: Gantt chart (Optimistic Scenario)
Project Time Graph:-

19FINAL PROJECT REPORT
Requirement Analysis
Scope Development
Development of project charter
Project Initiation Documentation
Project Kick off meeting
Development Planning
Deployment Planning
Maintenance Planning
Project Planning
Communication Planning
Quality Planning
Risk Management Planning
Procurement Planning
Plans Approval
Develop use cases
Create data and hardware architecture
Perform impact analysis
Develop migration strategy
Design UI
Design objects and workflow
Design rules and middle tier
Design database
Design connectivity with other systems
Design permissions
Product design approved
0
1
2
3
4
5
6
3
4
5 5
1
4
5
3
4
5 5
4
3 3 3
5
3
4
3
5 5
4 4
2
1
Activity duration (in days)
Activity duration (in days)
Figure 14: Project Time Graph (Optimistic Scenario)
Project Time Phased Budget:-
February 2018 March 2018 April 2018 May 2018 June 2018
0.00 . .د إ
5,000.00 . .د إ
10,000.00 . .د إ
15,000.00 . .د إ
20,000.00 . .د إ
25,000.00 . .د إ
30,000.00 . .د إ
35,000.00 . .د إ
40,000.00 . .د إ
45,000.00 . .د إ
7,770.00 . .د إ
16,830.00 . .د إ
29,740.00 . .د إ
40,013.13 . .د إ
5,646.88 . .د إ
Cost
Cost
Figure 15: Time Phased Budget 9 Optimistic Scenario)
The change in project duration from 83 (optimistic) to 93 in most likely case and 83 (optimistic) to 111 in pessimistic scenario is resulted due to the change
in planning phase of the project. The planning phase comparison for the three scenarios is shown below,
Activity
Pessimisti
c Most Likely Optimistic
Development Planning 6 4 3
Deployment Planning 7 5 3
Maintenance Planning 5 3 3
Project Planning 6 4 3
Communication Planning 7 5 3
Quality Planning 7 5 3
Risk Management Planning 6 4 3
Procurement Planning 5 3 3
Plans Approval 5 3 2
Total 54 36 26
The change in duration of planning process can be resulted due to the following issues during the process of planning due to factors like,

20FINAL PROJECT REPORT
Change in requirement: the change in requirement or scope of the project is the primary reason behind the occurrence of the change in duration (Kerzner
and Kerzner 2017). The design development includes the consideration of various technical factors like database integration, compatibility issues, and occasional
issues in integration.
Non-availability of resources: The non-availability of the resources would be helpful for the development of effective and improved operations. The non
availability of resources is a major factor that would involve the delay in completion of the project activities.
Time Consumption: The consumption of time for an individual activity might not be completed as expected and the delay in operation of the activities for
the deployment. The consumption of the time for the activities might not be sufficient in practical life.
3d. EVM analysis for project
The earned value management analysis for the three scenarios (pessimistic, most likely, and optimistic) of the project are given below,
Pessimistic Scenario:
Task Name Planned Value - PV
(BCWS)
Earned Value - EV
(BCWP) AC (ACWP) SV CV EAC BAC VAC
Tasks for software development
project AED12,560.00 AED12,560.00 AED12,560.00 AED0.00 AED0.00 AED124,000.00 AED124,000.00 AED0.00
Initiation Phase AED11,280.00 AED11,280.00 AED11,280.00 AED0.00 AED0.00 AED11,280.00 AED11,280.00 AED0.00
Requirement Analysis AED1,920.00 AED1,920.00 AED1,920.00 AED0.00 AED0.00 AED1,920.00 AED1,920.00 AED0.00
Scope Development AED2,560.00 AED2,560.00 AED2,560.00 AED0.00 AED0.00 AED2,560.00 AED2,560.00 AED0.00
Development of project charter AED2,800.00 AED2,800.00 AED2,800.00 AED0.00 AED0.00 AED2,800.00 AED2,800.00 AED0.00
Project Initiation
Documentation AED2,800.00 AED2,800.00 AED2,800.00 AED0.00 AED0.00 AED2,800.00 AED2,800.00 AED0.00
Project Kick off meeting AED1,200.00 AED1,200.00 AED1,200.00 AED0.00 AED0.00 AED1,200.00 AED1,200.00 AED0.00
Planning Phase AED1,280.00 AED1,280.00 AED1,280.00 AED0.00 AED0.00 AED45,840.45 AED45,840.00 (AED0.45)
Development Planning AED1,280.00 AED1,280.00 AED1,280.00 AED0.00 AED0.00 AED3,840.03 AED3,840.00 (AED0.03)
Deployment Planning AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED7,840.00 AED7,840.00 AED0.00
Maintenance Planning AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED5,600.00 AED5,600.00 AED0.00
Project Planning AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED3,840.00 AED3,840.00 AED0.00
Communication Planning AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED4,480.00 AED4,480.00 AED0.00
Quality Planning AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED6,720.00 AED6,720.00 AED0.00
Risk Management Planning AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED4,320.00 AED4,320.00 AED0.00
Procurement Planning AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED3,200.00 AED3,200.00 AED0.00
Plans Approval AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED6,000.00 AED6,000.00 AED0.00
Execution Phase AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED66,880.00 AED66,880.00 AED0.00
Manage Design AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED24,720.00 AED24,720.00 AED0.00
Develop use cases AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED2,400.00 AED2,400.00 AED0.00
Create data and hardware
architecture AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED14,480.00 AED14,480.00 AED0.00
Perform impact analysis AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED3,360.00 AED3,360.00 AED0.00
Develop migration strategy AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED4,480.00 AED4,480.00 AED0.00
Design product AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED42,160.00 AED42,160.00 AED0.00
Design UI AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED6,400.00 AED6,400.00 AED0.00
Design objects and workflow AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED9,700.00 AED9,700.00 AED0.00
Design rules and middle tier AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED4,000.00 AED4,000.00 AED0.00
Design database AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED10,160.00 AED10,160.00 AED0.00
Design connectivity with
other systems AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED8,700.00 AED8,700.00 AED0.00
Design permissions AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED2,080.00 AED2,080.00 AED0.00
Product design approved AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED1,120.00 AED1,120.00 AED0.00
Most Likely Scenario:
Task Name Planned Value - PV
(BCWS)
Earned Value - EV
(BCWP) AC (ACWP) SV CV EAC BAC VAC
Tasks for software development
project AED12,560.00 AED12,560.00 AED12,560.0
0 AED0.00 AED0.00 AED108,640.00 AED108,640.00 AED0.00
Initiation Phase AED11,280.00 AED11,280.00 AED11,280.0
0 AED0.00 AED0.00 AED11,280.00 AED11,280.00 AED0.00
Requirement Analysis AED1,920.00 AED1,920.00 AED1,920.00 AED0.00 AED0.00 AED1,920.00 AED1,920.00 AED0.00
Scope Development AED2,560.00 AED2,560.00 AED2,560.00 AED0.00 AED0.00 AED2,560.00 AED2,560.00 AED0.00

21FINAL PROJECT REPORT
Development of project charter AED2,800.00 AED2,800.00 AED2,800.00 AED0.00 AED0.00 AED2,800.00 AED2,800.00 AED0.00
Project Initiation
Documentation AED2,800.00 AED2,800.00 AED2,800.00 AED0.00 AED0.00 AED2,800.00 AED2,800.00 AED0.00
Project Kick off meeting AED1,200.00 AED1,200.00 AED1,200.00 AED0.00 AED0.00 AED1,200.00 AED1,200.00 AED0.00
Planning Phase AED1,280.00 AED1,280.00 AED1,280.00 AED0.00 AED0.00 AED30,480.00 AED30,480.00 AED0.00
Development Planning AED1,280.00 AED1,280.00 AED1,280.00 AED0.00 AED0.00 AED2,560.00 AED2,560.00 AED0.00
Deployment Planning AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED5,600.00 AED5,600.00 AED0.00
Maintenance Planning AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED3,360.00 AED3,360.00 AED0.00
Project Planning AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED2,560.00 AED2,560.00 AED0.00
Communication Planning AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED3,200.00 AED3,200.00 AED0.00
Quality Planning AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED4,800.00 AED4,800.00 AED0.00
Risk Management Planning AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED2,880.00 AED2,880.00 AED0.00
Procurement Planning AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED1,920.00 AED1,920.00 AED0.00
Plans Approval AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED3,600.00 AED3,600.00 AED0.00
Execution Phase AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED66,880.00 AED66,880.00 AED0.00
Manage Design AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED24,720.00 AED24,720.00 AED0.00
Develop use cases AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED2,400.00 AED2,400.00 AED0.00
Create data and hardware
architecture AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED14,480.00 AED14,480.00 AED0.00
Perform impact analysis AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED3,360.00 AED3,360.00 AED0.00
Develop migration strategy AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED4,480.00 AED4,480.00 AED0.00
Design product AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED42,160.00 AED42,160.00 AED0.00
Design UI AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED6,400.00 AED6,400.00 AED0.00
Design objects and workflow AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED9,700.00 AED9,700.00 AED0.00
Design rules and middle tier AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED4,000.00 AED4,000.00 AED0.00
Design database AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED10,160.00 AED10,160.00 AED0.00
Design connectivity with
other systems AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED8,700.00 AED8,700.00 AED0.00
Design permissions AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED2,080.00 AED2,080.00 AED0.00
Product design approved AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED1,120.00 AED1,120.00 AED0.00
Optimistic Scenario:
Task Name Planned Value - PV
(BCWS)
Earned Value - EV
(BCWP) AC (ACWP) SV CV EAC BAC VAC
Tasks for software development
project AED12,560.00 AED12,560.00 AED12,560.00 AED0.00 AED0.00 AED100,000.00 AED100,000.00 AED0.00
Initiation Phase AED11,280.00 AED11,280.00 AED11,280.00 AED0.00 AED0.00 AED11,280.00 AED11,280.00 AED0.00
Requirement Analysis AED1,920.00 AED1,920.00 AED1,920.00 AED0.00 AED0.00 AED1,920.00 AED1,920.00 AED0.00
Scope Development AED2,560.00 AED2,560.00 AED2,560.00 AED0.00 AED0.00 AED2,560.00 AED2,560.00 AED0.00
Development of project charter AED2,800.00 AED2,800.00 AED2,800.00 AED0.00 AED0.00 AED2,800.00 AED2,800.00 AED0.00
Project Initiation
Documentation AED2,800.00 AED2,800.00 AED2,800.00 AED0.00 AED0.00 AED2,800.00 AED2,800.00 AED0.00
Project Kick off meeting AED1,200.00 AED1,200.00 AED1,200.00 AED0.00 AED0.00 AED1,200.00 AED1,200.00 AED0.00
Planning Phase AED1,280.00 AED1,280.00 AED1,280.00 AED0.00 AED0.00 AED21,840.21 AED21,840.00 (AED0.21)
Development Planning AED1,280.00 AED1,280.00 AED1,280.00 AED0.00 AED0.00 AED1,920.01 AED1,920.00 AED0.00
Deployment Planning AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED3,360.00 AED3,360.00 AED0.00
Maintenance Planning AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED3,360.00 AED3,360.00 AED0.00
Project Planning AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED1,920.00 AED1,920.00 AED0.00
Communication Planning AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED1,920.00 AED1,920.00 AED0.00
Quality Planning AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED2,880.00 AED2,880.00 AED0.00
Risk Management Planning AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED2,160.00 AED2,160.00 AED0.00
Procurement Planning AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED1,920.00 AED1,920.00 AED0.00
Plans Approval AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED2,400.00 AED2,400.00 AED0.00
Execution Phase AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED66,880.00 AED66,880.00 AED0.00
Manage Design AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED24,720.00 AED24,720.00 AED0.00
Develop use cases AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED2,400.00 AED2,400.00 AED0.00
Create data and hardware
architecture AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED14,480.00 AED14,480.00 AED0.00
Perform impact analysis AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED3,360.00 AED3,360.00 AED0.00
Develop migration strategy AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED4,480.00 AED4,480.00 AED0.00
Design product AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED42,160.00 AED42,160.00 AED0.00
Design UI AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED6,400.00 AED6,400.00 AED0.00
Design objects and workflow AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED9,700.00 AED9,700.00 AED0.00
Design rules and middle tier AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED4,000.00 AED4,000.00 AED0.00

22FINAL PROJECT REPORT
Design database AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED10,160.00 AED10,160.00 AED0.00
Design connectivity with
other systems AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED8,700.00 AED8,700.00 AED0.00
Design permissions AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED2,080.00 AED2,080.00 AED0.00
Product design approved AED0.00 AED0.00 AED0.00 AED0.00 AED0.00 AED1,120.00 AED1,120.00 AED0.00

23FINAL PROJECT REPORT
3d. Milestone Report
The milestone report is made on 9th March 2018 for all the three scenarios (pessimistic,
most likely, and optimistic) of the project.
Optimistic Pessimistic Most likely
% Work
Completed
24% 18% 22%
Accomplished
tasks
Initiation Phase (fully
completed) and Planning
phase 8% (Development
planning 67% completed)
Initiation Phase (fully
completed) and Planning
phase 4% (Development
planning 33% completed)
Initiation Phase (fully
completed) and Planning
phase 6% (Development
planning 50% completed)
Remaining
tasks
Rest of the planning
activities (92%) and
project execution
Rest of the planning
activities (96%) and
project execution
Rest of the planning
activities (94%) and
project execution
Associated
Risks
Technical risks like issue
in object designing and
errors in permission
development.
Technical risks like issue
in data management and
errors in use case
development.
Technical risks like issue
in UI development and
errors in database
formation
3e. Other Reports of Project
Communication Matrix Report:
Information Receiver Communication
Medium
Frequency Sender
Project
Requirements
Project Manager Board Meetings Once Project Client
Design for
software
Engineer Pen Drive/External
Storage
Once Designer
Schedule Plan Project Team Scheduler Form Once Planner
Project Progress Client Report
Documentation
Weekly Project Manager
Success
Evaluation
Quality
Department
Checklist Mid-term Users
Risk Assessment Report:
S. no Risk Name Risk type Likelihood Severity Impact Mitigation
1 Delay in
completion
Operational Almost
Certain
Minor Medium Schedule
Management
should be
formed
2 Design Errors Technical Possible Major Extreme SDLC should
be used for

24FINAL PROJECT REPORT
design phase
3 Data
Incompatibility
Performance Unlikely Critical High Independent
data platform
should be used
4 Disagreement
among team
members
Human Rare Major Medium Effective
communication
should be used
5 Cost overrun Financial Likely Moderate High Provisional
budget should
be used

25FINAL PROJECT REPORT
Bibliography
Alshamrani, A. and Bahattab, A., 2015. A comparison between three SDLC models waterfall
model, spiral model, and Incremental/Iterative model. International Journal of Computer
Science Issues (IJCSI), 12(1), p.106.
Batselier, J. and Vanhoucke, M., 2015. Evaluation of deterministic state-of-the-art forecasting
approaches for project duration based on earned value management. International Journal of
Project Management, 33(7), pp.1588-1596.
Chen, M., Wan, J., González-Valenzuela, S., Liao, X. and Leung, V.C., 2014. A Survey of
Recent Developments in Home M2M Networks. IEEE Communications Surveys and
Tutorials, 16(1), pp.98-114.
Chen, W., Delgrossi, L., Kosch, T. and Saito, T., 2016. Automotive networking and applications
[Series Editorial]. IEEE Communications Magazine, 54(2), pp.96-96.
Davies, G. and Gaved, M., 2017. Seeking togetherness: moving toward a comparative evaluation
framework in an interdisciplinary DIY networking project.
Davis, S., 2016. Relocating development communication: Social entrepreneurship, international
networking, and South-South cooperation in the Viva Rio NGO. International Journal of
Communication, 10, p.18.
Deligiannidis, L., Wiseman, C., Yun, M. and Arabnia, H.R., 2014. Security Projects for Systems
and Networking Professionals. In Emerging Trends in ICT Security (pp. 111-122).
Farhady, H., Lee, H. and Nakao, A., 2015. Software-defined networking: A survey. Computer
Networks, 81, pp.79-95.
Fleming, Q.W. and Koppelman, J.M., 2016, December. Earned value project management.
Project Management Institute.

26FINAL PROJECT REPORT
Hakiri, A., Gokhale, A., Berthou, P., Schmidt, D.C. and Gayraud, T., 2014. Software-defined
networking: Challenges and research opportunities for future internet. Computer Networks, 75,
pp.453-471.
Hellmich, S., Schreiber, N., Fath, B. and Hallek, M., 2016. Progress due to networking
structures. Challenges for the Competence Network Malignant Lymphomas in the Era of
Precision Medicine. Bundesgesundheitsblatt, Gesundheitsforschung, Gesundheitsschutz, 59(4),
pp.454-464.
Kay, J.E., Deser, C., Phillips, A., Mai, A., Hannay, C., Strand, G., Arblaster, J.M., Bates, S.C.,
Danabasoglu, G., Edwards, J. and Holland, M., 2015. The Community Earth System Model
(CESM) large ensemble project: A community resource for studying climate change in the
presence of internal climate variability. Bulletin of the American Meteorological Society, 96(8),
pp.1333-1349.
Kerzner, H. and Kerzner, H.R., 2017. Project management: a systems approach to planning,
scheduling, and controlling. John Wiley & Sons.
Kshirsagar, A.B. and Konnur, B.A., 2017. Earned Value Management Tool for Controlling
Project Duration and Budgeted Cost.
Losilla, F., 2017. A web‐based design and assessment tool for educational wireless networking
projects. Computer Applications in Engineering Education, 25(6), pp.992-1000.
Madgunda, S., Suman, U., Praneeth, G.S. and Kasera, R., 2015. Steps in Requirement Stage of
Waterfall Model. International journal of computer & mathematical sciences, pp.86-87.
McNeil, A.J., Frey, R. and Embrechts, P., 2015. Quantitative risk management: Concepts,
techniques and tools. Princeton university press.