University Software Development Project: Final Project Report

This report presents a comprehensive analysis of a software development project, focusing on the application of project management tools and principles. It begins with an introduction outlining the project's objectives and scope, followed by a detailed examination of project assumptions, including resource availability and project constraints. The core of the report includes a Work Breakdown Structure (WBS) that outlines task dependencies and a project timeline, cost analysis, and resource allocation. The report then presents various project reports, such as a baseline report, scenario plans, progress and cash flow reports, Earned Value Management (EVM) analysis, and milestone reports. The report also considers project crashing to shorten the project duration. The project utilizes a traditional waterfall approach. The document provides a valuable resource for students studying project management and software development, offering insights into the practical application of project management methodologies.

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