Project Management: Planning, Scheduling, Resource Allocation, Feasibility Analysis, Progress Evaluation and Conclusion

This article discusses the project management techniques used in a software development project, including planning, scheduling, resource allocation, feasibility analysis, progress evaluation, and conclusion. It includes a project schedule developed using Ms-Project software, a critical path analysis, and a resource table. The article also describes the scheduling technique used, the Gantt chart, and its advantages. The project plan is divided into six sub-projects, and the critical path is identified.

Running head: PROJECT MANAGEMENT
Project Management
Name of the Student:
Student ID:
Name of the University:
Author’s note:

Table of Contents
A. Project Planning..........................................................................................................................3
A1. Description of Scheduling Technique...................................................................................3
A2. Project Schedule...................................................................................................................3
A3. Resources Required..............................................................................................................6
B. Overall Project Duration and Critical Path.................................................................................7
B1. Description of Overall Project Duration...............................................................................7
B2. Critical Path Analysis............................................................................................................7
C. Resource Allocation....................................................................................................................9
D. Feasibility Analysis and Crashing of the Project......................................................................12
D1. Feasibility Analysis of the Project for Crashing.................................................................12
D2. Crashing of the Project.......................................................................................................13
E. Progress Evaluation of the Project............................................................................................16
F. Second Crashing........................................................................................................................17
G. Modified Project.......................................................................................................................20
G1. Project Progress (50%-70%)...............................................................................................20
G2. Third Corrective Crashing..................................................................................................22
H. Project Conclusion....................................................................................................................25
Bibliography..................................................................................................................................27

A. Project Planning
A1. Description of Scheduling Technique
The project scheduling techniques are some software or tools that are used by the project
managers for developing, controlling, and monitoring of the project operations in a schedule
format. Task List, Gantt chart, and Calender are three main scheduling techniques that are
commonly used by the project managers for the development of project schedule (Cicmil et al.
2017). For the Software Development Project, Gantt chart is being used and it would allow the
easy tracking and progress reporting for the project. The most important benefit of using the
Gantt chart is that it allows the quick estimation and development of the project plan. The Gantt
chart is typically a bar chart for displaying all the activities of project in sequential order along
with a timeline (Hegazy 2013). The activities of the project is represented by a bar reflecting
start date, duration, and date of the activity. The Gantt chart has the following advantages,
 Ease of viewing the progress and modifying the progress
 Assigning the resources and tasks within short time
 Can be adopted in all the projects and industries
A2. Project Schedule
The project plan was developed with the help of Ms-Project Software and it followed the
SDLC for ensuring that the Software Development Project would be aligned easily (Larson and
Gray 2013). The effective development of the operations with the help of the Gantt chart would
allow the development of the software for the organization. The project schedule has been shown
in the table below,

WBS Task Name Duration Start Finish Predecessors
0 Software Development Project 106 days Thu
12/7/17 Thu 5/3/18
1 Project Initialization 27 days Thu
12/7/17 Fri 1/12/18
1.1 Concept review process 5 days Thu 12/7/17 Wed
12/13/17
1.2 Resource Accumulation 10 days Thu
12/14/17
Wed
12/27/17 2
1.3 Initial Documentation 4 days Thu
12/28/17 Tue 1/2/18 3
1.4 Charter Documentation 4 days Wed 1/3/18 Mon 1/8/18 4
1.5 Submission of the Documents 2 days Tue 1/9/18 Wed
1/10/18 5
1.6 Review and Signup 2 days Thu 1/11/18 Fri 1/12/18 6
2 Plan Development 17 days Mon
1/15/18 Tue 2/6/18
2.1 Plan Outline development 5 days Mon
1/15/18 Fri 1/19/18 7
2.2 Review of the plan 3 days Mon
1/22/18
Wed
1/24/18 9
2.3 Complete Plan Development 8 days Thu 1/25/18 Mon 2/5/18 10
2.4 Plan Approval 1 day Tue 2/6/18 Tue 2/6/18 11
3 Designing of the Software 17 days Wed 2/7/18 Thu 3/1/18
3.1 Selection of design platform 2 days Wed 2/7/18 Thu 2/8/18 12
3.2 Obtaining the tool required for
designing 4 days Fri 2/9/18 Wed
2/14/18 14
3.3 Making Design of the software 5 days Thu 2/15/18 Wed
2/21/18 15
3.4 Simulation of the design made 3 days Thu 2/22/18 Mon 16

2/26/18
3.5 Modification of the design made 2 days Tue 2/27/18 Wed
2/28/18 17
3.6 Design Approval 1 day Thu 3/1/18 Thu 3/1/18 18
4 Database Development 20 days Wed 2/7/18 Tue 3/6/18
4.1 Selection of database platform 2 days Wed 2/7/18 Thu 2/8/18 12
4.2 Database Migration 5 days Fri 2/9/18 Thu 2/15/18 21
4.3 Prototype testing 7 days Fri 2/16/18 Mon
2/26/18 22
4.4 Storage Media is selected 2 days Tue 2/27/18 Wed
2/28/18 23
4.5 Stored in the new storage device 3 days Thu 3/1/18 Mon 3/5/18 24
4.6 Database is completed 1 day Tue 3/6/18 Tue 3/6/18 25
5 Software Development 30 days Wed 3/7/18 Tue 4/17/18
5.1 User Interface is developed 5 days Wed 3/7/18 Tue 3/13/18 26, 19
5.2 Functions are aligned 6 days Wed
3/14/18
Wed
3/21/18 28
5.3 Coding the program for the software
function 10 days Thu 3/22/18 Wed 4/4/18 29
5.4 Black box testing 4 days Thu 4/5/18 Tue 4/10/18 30
5.5 White box testing 4 days Wed
4/11/18
Mon
4/16/18 31
5.6 Software is developed 1 day Tue 4/17/18 Tue 4/17/18 32
6 Documentation and closure 12 days Wed
4/18/18 Thu 5/3/18
6.1 Making final reports 6 days Wed
4/18/18
Wed
4/25/18 33
6.2 Submitting the reports 2 days Thu 4/26/18 Fri 4/27/18 35
6.3 Signing off 1 day Mon Mon 36

4/30/18 4/30/18
6.4 Go Live Software 2 days Tue 5/1/18 Wed 5/2/18 37
6.5 Project is closed 1 day Thu 5/3/18 Thu 5/3/18 38
A3. Resources Required
The resource table showing the name, type, and rate of the resources required for the project
Resource Name Type Std. Rate
Project Manager Work $80.00/hr
Documenter Work $50.00/hr
Planner Work $45.00/hr
Designer Work $65.00/hr
IT Engineer Work $70.00/hr
Database Developer Work $75.00/hr
Designing tool Material $599.00
Documents Material $50.00
Simulation Software Material $179.00
Prototype Software Material $189.00
Storage Device Material $499.00
Computer Devices Material $1,299.00
Network Connection Material $349.00
Equipments Material $1,500.00
Coding Software Material $209.00
Testing Software Material $169.00

B. Overall Project Duration and Critical Path
B1. Description of Overall Project Duration
The project plan has been completed in 6 sub-projects or work packages namely Project
Initialization, Plan Development, Designing of the Software, Database Development, Software
Development, and Documentation and closure (Martinelli and Milosevic 2016). These sub-
projects consist of number of activities that comprises the overall project schedule. The project
has run for 106 working days from Thu 12/7/17 to Thu 5/3/18. The project initialization consists
of the following activities concept review process, resource accumulation, initial documentation,
review and signup, submission of the documents, and charter documentation. The plan
development consists of plan outline development, review of the plan, complete plan
development, and plan approval. The designing of the software consists of selection of design
platform, obtaining the tool required for designing, making design of the software, simulation of
the design made, modification of the design made, and design approval. The database
development consists of selection of database platform, database migration, prototype testing,
storage media is selected, stored in the new storage device, and database is completed. The
software development consists of user interface is developed, functions are aligned, coding the
program for the software function, black box testing, white box testing, and software is
developed. The documentation and closure consists of making final reports, submitting the
reports, signing off, go live software, and project is closed.
B2. Critical Path Analysis
The critical path of the project is,

11.11.21.31.41.51.622.12.22.32.444.14.24.34.44.54.
655.15.25.35.45.55.666.16.26.36.46.5
The critical path analysis has divided the project in critical task and summary and non critical
task and summary. They have been sorted in the table below,
Critical Non-critical
Summar
y
Project Initialization, Plan Development, Database
Development, Software Development, and
Documentation and closure
Designing of the Software
Tasks Concept review process, Resource Accumulation, Initial
Documentation, Charter Documentation, Submission of
the Documents, Review and Signup, Plan Outline
development, Review of the plan, Complete Plan
Development, Plan Approval, Selection of database
platform, Database Migration, Prototype testing, Storage
Media is selected, Stored in the new storage device,
Database is completed, User Interface is developed,
Functions are aligned, Coding the program for the
software function, Black box testing, White box testing,
Software is developed, Making final reports, Submitting
the reports, Signing off, Go Live Software, and Project is
closed
Selection of design platform,
obtaining the tool required for
designing, making design of the
software, simulation of the design
made, modification of the design
made, and design approval
The critical path of the project has been shown in the following diagram with the help of
light red colour highlights and the non critical task is highlighted by blue colour.

0
1
1.1
1.2 1.3
1.4 1.5 1.6
2
2.1
2.2
2.3 2.4
3 3.1
3.2 3.3
3.4 3.5 3.6
4
4.1
4.2 4.3
4.4 4.5 4.6
5 5.1
5.2
5.3
5.4 5.5 5.6
6 6.1 6.2
6.3 6.4 6.5
- Software
Development
Project
- Project
Initialization
- Plan
Development
- Designing
of the
Software
- Database
Development
- Software
Development
-
Documentation
and closure
- Concept
review
process
- Resource
Accumulation
- Initial
Documentation
- Charter
Documentation
-
Submission
of the
Documents
- Review
and Signup
- Plan
Outline
development
- Review of
the plan
- Complete
Plan
Development
- Plan
Approval
- Selection
of design
platform
- Obtaining
the tool
required for
designing
- Making
Design of
the
software
- Simulation
of the
design made
-
Modification
of the design
made
- Design
Approval
- Selection
of database
platform
- Database
Migration
- Prototype
testing
- Storage
Media is
selected
- Stored in
the new
storage
device
- Database
is
completed
- User
Interface is
developed
- Functions
are aligned
- Coding the
program for
the software
function
- Black box
tesing
- White box
testing
- Software is
developed
- Making
final reports
- Submitting
the reports
- Signing off - Go Live
Software
- Project is
closed
Figure: Critical Path of the project
C. Resource Allocation
Resource Name Activities involved in Work Cost
Project Manager Concept review process 40 hrs $3,200.00
Resource Accumulation 80 hrs $6,400.00
Review and Signup 16 hrs $1,280.00
Plan Approval 8 hrs $640.00
Database is completed 8 hrs $640.00
Signing off 8 hrs $640.00
Project is closed 8 hrs $640.00
Documenter Initial Documentation 32 hrs $1,600.00
Charter Documentation 32 hrs $1,600.00
Submission of the Documents 16 hrs $800.00

Making final reports 48 hrs $2,400.00
Submitting the reports 16 hrs $800.00
Planner Plan Outline development 40 hrs $1,800.00
Review of the plan 24 hrs $1,080.00
Complete Plan Development 64 hrs $2,880.00
Designer Selection of design platform 16 hrs $1,040.00
Obtaining the tool required for designing 32 hrs $2,080.00
Making Design of the software 40 hrs $2,600.00
Simulation of the design made 24 hrs $1,560.00
Modification of the design made 16 hrs $1,040.00
IT Engineer Design Approval 8 hrs $560.00
Storage Media is selected 16 hrs $1,120.00
User Interface is developed 40 hrs $2,800.00
Functions are aligned 48 hrs $3,360.00
Coding the program for the software function 80 hrs $5,600.00

Black box testing 32 hrs $2,240.00
White box testing 32 hrs $2,240.00
Software is developed 8 hrs $560.00
Go Live Software 16 hrs $1,120.00
Database Developer Selection of database platform 16 hrs $1,200.00
Database Migration 40 hrs $3,000.00
Prototype testing 56 hrs $4,200.00
Stored in the new storage device 24 hrs $1,800.00
Designing tool Obtaining the tool required for designing 1 $599.00
Documents Initial Documentation 1 $50.00
Charter Documentation 1 $50.00
Making final reports 1 $50.00
Simulation Software Simulation of the design made 1 $179.00
Prototype Software Prototype testing 1 $189.00
Storage Device Stored in the new storage device 1 $499.00
Computer Devices Resource Accumulation 1 $1,299.00

Network Connection Resource Accumulation 1 $349.00
Equipments Resource Accumulation 1 $1,500.00
Coding Software Coding the program for the software function 1 $209.00
Testing Software Black box testing 1 $169.00
White box testing 1 $169.00
Software is developed 1 $169.00
D. Feasibility Analysis and Crashing of the Project
D1. Feasibility Analysis of the Project for Crashing
The project crashing is based on the factor that the total increase in the indirect cost would be
less than the decrease in the indirect cost (Nakamura et al. 2015). The critical tasks and resources
would be used for the modification of the project for crashing and it would help in ensuring that
the project would be completed successfully. The feasibility study has shown that following
factors need to be kept in mind for crashing the project,
i. Cost of indirect cost of resources required for crashing should be less than the reduction
in direct costs
ii. Overall project duration would be accepted by the client and feasible for implication
iii. Critical tasks should be crashed only as it would form an impact on the overall project
duration

D2. Crashing of the Project
Previously in the project plan, the testing, simulation, and analysis were done by designer,
database developer, and IT Engineer. However, a Tester was employed at a rate of $40.00/hr for
replacing them for the testing activities. The first crashing of the project has the following
features,
a) Change of the project duration from 106 days to 111 days with the introduction of the
tester
b) Increase of the duration of testing activities by 1 day
c) Decrease of project budget to $66,880.00 from $70,000.00 as the rate of Tester was less
than the designer, database developer, and IT Engineer
d) Reduction in cost of each of the phase of Designing of the Software, Database
Development, and Software Development
WBS Task Name Duration Start Finish Predecessors Resource
Names Cost
0
Software
Development
Project
111 days Thu
12/7/17
Thu
5/10/18 $66,880.00
1 Project
Initialization 27 days Thu
12/7/17
Fri
1/12/18 $18,128.00
1.1 Concept
review process 5 days Thu
12/7/17
Wed
12/13/17
Project
Manager $3,200.00
1.2 Resource
Accumulation 10 days Thu
12/14/17
Wed
12/27/17 2
Project
Manager,
Computer
Devices[1],
Network
Connection[1],
Equipments[1]
$9,548.00
1.3 Initial
Documentation 4 days Thu
12/28/17
Tue
1/2/18 3 Documenter,
Documents[1] $1,650.00

1.4 Charter
Documentation 4 days Wed
1/3/18
Mon
1/8/18 4 Documenter,
Documents[1] $1,650.00
1.5 Submission of
the Documents 2 days Tue
1/9/18
Wed
1/10/18 5 Documenter $800.00
1.6 Review and
Signup 2 days Thu
1/11/18
Fri
1/12/18 6 Project
Manager $1,280.00
2 Plan
Development 17 days Mon
1/15/18
Tue
2/6/18 $6,400.00
2.1 Plan Outline
development 5 days Mon
1/15/18
Fri
1/19/18 7 Planner $1,800.00
2.2 Review of the
plan 3 days Mon
1/22/18
Wed
1/24/18 9 Planner $1,080.00
2.3 Complete Plan
Development 8 days Thu
1/25/18
Mon
2/5/18 10 Planner $2,880.00
2.4 Plan Approval 1 day Tue
2/6/18
Tue
2/6/18 11 Project
Manager $640.00
3 Designing of
the Software 22 days Wed
2/7/18
Thu
3/8/18 $9,378.00
3.1 Selection of
design platform 2 days Wed
2/7/18
Thu
2/8/18 12 Designer $1,040.00
3.2
Obtaining the
tool required for
designing
4 days Fri
2/9/18
Wed
2/14/18 14
Designer,
Designing
tool[1]
$2,679.00
3.3
Making
Design of the
software
5 days Thu
2/15/18
Wed
2/21/18 15 Designer $2,600.00
3.4 Simulation of
the design made 4 days Wed
2/28/18
Mon
3/5/18 16,23
Simulation
Software[1],
Tester
$1,459.00
3.5
Modification
of the design
made
2 days Tue
3/6/18
Wed
3/7/18 17 Designer $1,040.00
3.6 Design
Approval 1 day Thu
3/8/18
Thu
3/8/18 18 IT Engineer $560.00
4 Database
Development 21 days Wed
2/7/18
Wed
3/7/18 $11,008.00
4.1 Selection of
database platform 2 days Wed
2/7/18
Thu
2/8/18 12 Database
Developer $1,200.00
4.2 Database
Migration 5 days Fri
2/9/18
Thu
2/15/18 21 Database
Developer $3,000.00
4.3 Prototype
testing 8 days Fri
2/16/18
Tue
2/27/18 22
Prototype
Software[1],
Tester
$2,749.00

4.4 Storage Media
is selected 2 days Wed
2/28/18
Thu
3/1/18 23 IT Engineer $1,120.00
4.5
Stored in the
new storage
device
3 days Fri
3/2/18
Tue
3/6/18 24
Database
Developer,
Storage
Device[1]
$2,299.00
4.6 Database is
completed 1 day Wed
3/7/18
Wed
3/7/18 25 Project
Manager $640.00
5 Software
Development 33 days Fri
3/9/18
Tue
4/24/18 $16,316.00
5.1 User Interface
is developed 5 days Fri
3/9/18
Thu
3/15/18 26,19 IT Engineer $2,800.00
5.2 Functions are
aligned 6 days Fri
3/16/18
Fri
3/23/18 28 IT Engineer $3,360.00
5.3
Coding the
program for the
software function
10 days Mon
3/26/18
Fri
4/6/18 29
IT Engineer,
Coding
Software[1]
$5,809.00
5.4 Black box
testing 5 days Mon
4/9/18
Fri
4/13/18 30
Testing
Software[1],
Tester
$1,769.00
5.5 White box
testing 5 days Mon
4/16/18
Fri
4/20/18 31
Testing
Software[1],
Tester
$1,769.00
5.6 Software is
developed 2 days Mon
4/23/18
Tue
4/24/18 32
Testing
Software[1],
Tester
$809.00
6 Documentation
and closure 12 days Wed
4/25/18
Thu
5/10/18 $5,650.00
6.1 Making final
reports 6 days Wed
4/25/18
Wed
5/2/18 33 Documenter,
Documents[1] $2,450.00
6.2 Submitting the
reports 2 days Thu
5/3/18
Fri
5/4/18 35 Documenter $800.00
6.3 Signing off 1 day Mon
5/7/18
Mon
5/7/18 36 Project
Manager $640.00
6.4 Go Live
Software 2 days Tue
5/8/18
Wed
5/9/18 37 IT Engineer $1,120.00
6.5 Project is
closed 1 day Thu
5/10/18
Thu
5/10/18 38 Project
Manager $640.00
E. Progress Evaluation of the Project

The project evaluation was done on the basis of keeping the project progress of first third
of the overall duration and it was scheduled on 22nd February, 2018. The following table would
show the progress of the project activities till the mentioned date,
WBS Task Name Duration Start Finish % Complete
0 Software Development Project 111 days Thu 12/7/17 Thu 5/10/18 33%
1 Project Initialization 27 days Thu 12/7/17 Fri 1/12/18 100%
1.1 Concept review process 5 days Thu 12/7/17 Wed
12/13/17 100%
1.2 Resource Accumulation 10 days Thu 12/14/17 Wed
12/27/17 100%
1.3 Initial Documentation 4 days Thu 12/28/17 Tue 1/2/18 100%
1.4 Charter Documentation 4 days Wed 1/3/18 Mon 1/8/18 100%
1.5 Submission of the Documents 2 days Tue 1/9/18 Wed 1/10/18 100%
1.6 Review and Signup 2 days Thu 1/11/18 Fri 1/12/18 100%
2 Plan Development 17 days Mon 1/15/18 Tue 2/6/18 88%
2.1 Plan Outline development 5 days Mon 1/15/18 Fri 1/19/18 100%
2.2 Review of the plan 3 days Mon 1/22/18 Wed 1/24/18 100%
2.3 Complete Plan Development 8 days Thu 1/25/18 Mon 2/5/18 88%
2.4 Plan Approval 1 day Tue 2/6/18 Tue 2/6/18 0%
3 Designing of the Software 22 days Wed 2/7/18 Thu 3/8/18 0%
3.1 Selection of design platform 2 days Wed 2/7/18 Thu 2/8/18 0%
3.2 Obtaining the tool required for
designing 4 days Fri 2/9/18 Wed 2/14/18 0%
3.3 Making Design of the software 5 days Thu 2/15/18 Wed 2/21/18 0%
3.4 Simulation of the design made 4 days Wed 2/28/18 Mon 3/5/18 0%
3.5 Modification of the design
made 2 days Tue 3/6/18 Wed 3/7/18 0%
3.6 Design Approval 1 day Thu 3/8/18 Thu 3/8/18 0%
4 Database Development 21 days Wed 2/7/18 Wed 3/7/18 0%
4.1 Selection of database platform 2 days Wed 2/7/18 Thu 2/8/18 0%
4.2 Database Migration 5 days Fri 2/9/18 Thu 2/15/18 0%
4.3 Prototype testing 8 days Fri 2/16/18 Tue 2/27/18 0%
4.4 Storage Media is selected 2 days Wed 2/28/18 Thu 3/1/18 0%
4.5 Stored in the new storage
device 3 days Fri 3/2/18 Tue 3/6/18 0%
4.6 Database is completed 1 day Wed 3/7/18 Wed 3/7/18 0%
5 Software Development 33 days Fri 3/9/18 Tue 4/24/18 0%
5.1 User Interface is developed 5 days Fri 3/9/18 Thu 3/15/18 0%

5.2 Functions are aligned 6 days Fri 3/16/18 Fri 3/23/18 0%
5.3 Coding the program for the
software function 10 days Mon 3/26/18 Fri 4/6/18 0%
5.4 Black box testing 5 days Mon 4/9/18 Fri 4/13/18 0%
5.5 White box testing 5 days Mon 4/16/18 Fri 4/20/18 0%
5.6 Software is developed 2 days Mon 4/23/18 Tue 4/24/18 0%
6 Documentation and closure 12 days Wed 4/25/18 Thu 5/10/18 0%
6.1 Making final reports 6 days Wed 4/25/18 Wed 5/2/18 0%
6.2 Submitting the reports 2 days Thu 5/3/18 Fri 5/4/18 0%
6.3 Signing off 1 day Mon 5/7/18 Mon 5/7/18 0%
6.4 Go Live Software 2 days Tue 5/8/18 Wed 5/9/18 0%
6.5 Project is closed 1 day Thu 5/10/18 Thu 5/10/18 0%
F. Second Crashing
The analysis of the project progress as on 22 February, 2018 was 33%. However, still the
project required 111 days for completion instead of the previous duration of 106 days. Hence
second crashing was done and an Assistant was added to the planner for deceasing the complete
plan development duration. The second crashing of the project has the following features,
a) Decrease of the plan duration to 4 days instead of the 8 days required in the initial
plan
b) Increase of the overall progress of the project to 35% for the same period
c) Decrease of the project cost to $65,920.00 from $66,880.00
WB
S Task Name Duratio
n Start Finish
%
Complet
e
Predecessor
s
Resource
Names Cost
0
Software
Development
Project
107 days Thu
12/7/17
Fri
5/4/18 35% $65,920.0
0
1 Project
Initialization 27 days Thu
12/7/17
Fri
1/12/18 100% $18,128.00
1.1 Concept 5 days Thu Wed 100% Project Manager $3,200.00

review process 12/7/17 12/13/1
7
1.2 Resource
Accumulation 10 days
Thu
12/14/1
7
Wed
12/27/1
7
100% 2
Project Manager,
Computer
Devices[1],
Network
Connection[1],
Equipments[1]
$9,548.00
1.3 Initial
Documentation 4 days
Thu
12/28/1
7
Tue
1/2/18 100% 3 Documenter,
Documents[1] $1,650.00
1.4 Charter
Documentation 4 days Wed
1/3/18
Mon
1/8/18 100% 4 Documenter,
Documents[1] $1,650.00
1.5
Submission
of the
Documents
2 days Tue
1/9/18
Wed
1/10/18 100% 5 Documenter $800.00
1.6 Review and
Signup 2 days Thu
1/11/18
Fri
1/12/18 100% 6 Project Manager $1,280.00
2 Plan
Development 13 days Mon
1/15/18
Wed
1/31/18 100% $5,440.00
2.1
Plan
Outline
development
5 days Mon
1/15/18
Fri
1/19/18 100% 7 Planner $1,800.00
2.2 Review of
the plan 3 days Mon
1/22/18
Wed
1/24/18 100% 9 Planner $1,080.00
2.3
Complete
Plan
Development
4 days Thu
1/25/18
Tue
1/30/18 100% 10 Planner,
Assistant $1,920.00
2.4 Plan
Approval 1 day Wed
1/31/18
Wed
1/31/18 100% 11 Project Manager $640.00
3 Designing of
the Software 22 days Thu
2/1/18
Fri
3/2/18 11% $9,378.00
3.1
Selection
of design
platform
2 days Thu
2/1/18
Fri
2/2/18 100% 12 Designer $1,040.00
3.2
Obtaining
the tool
required for
designing
4 days Mon
2/5/18
Thu
2/8/18 0% 14 Designer,
Designing tool[1] $2,679.00
3.3
Making
Design of the
software
5 days Fri
2/9/18
Thu
2/15/18 0% 15 Designer $2,600.00
3.4
Simulation
of the design
made
4 days Thu
2/22/18
Tue
2/27/18 0% 16,23
Simulation
Software[1],Teste
r
$1,459.00
3.5
Modification
of the design
2 days Wed
2/28/18
Thu
3/1/18
0% 17 Designer $1,040.00

made
3.6 Design
Approval 1 day Fri
3/2/18
Fri
3/2/18 0% 18 IT Engineer $560.00
4 Database
Development 21 days Thu
2/1/18
Thu
3/1/18 10% $11,008.00
4.1
Selection
of database
platform
2 days Thu
2/1/18
Fri
2/2/18 100% 12 Database
Developer $1,200.00
4.2 Database
Migration 5 days Mon
2/5/18
Fri
2/9/18 0% 21 Database
Developer $3,000.00
4.3 Prototype
testing 8 days Mon
2/12/18
Wed
2/21/18 0% 22
Prototype
Software[1],Teste
r
$2,749.00
4.4
Storage
Media is
selected
2 days Thu
2/22/18
Fri
2/23/18 0% 23 IT Engineer $1,120.00
4.5
Stored in
the new storage
device
3 days Mon
2/26/18
Wed
2/28/18 0% 24
Database
Developer,
Storage
Device[1]
$2,299.00
4.6 Database is
completed 1 day Thu
3/1/18
Thu
3/1/18 0% 25 Project Manager $640.00
5 Software
Development 33 days Mon
3/5/18
Wed
4/18/18 0% $16,316.00
5.1
User
Interface is
developed
5 days Mon
3/5/18
Fri
3/9/18 0% 26,19 IT Engineer $2,800.00
5.2 Functions
are aligned 6 days Mon
3/12/18
Mon
3/19/18 0% 28 IT Engineer $3,360.00
5.3
Coding the
program for the
software
function
10 days Tue
3/20/18
Mon
4/2/18 0% 29
IT Engineer,
Coding
Software[1]
$5,809.00
5.4 Black box
testing 5 days Tue
4/3/18
Mon
4/9/18 0% 30
Testing
Software[1],
Tester
$1,769.00
5.5 White box
testing 5 days Tue
4/10/18
Mon
4/16/18 0% 31
Testing
Software[1],
Tester
$1,769.00
5.6 Software is
developed 2 days Tue
4/17/18
Wed
4/18/18 0% 32
Testing
Software[1],
Tester
$809.00
6 Documentatio
n and closure
12 days Thu
4/19/18
Fri
5/4/18 0% $5,650.00
6.1 Making
final reports 6 days Thu
4/19/18
Thu
4/26/18 0% 33 Documenter,
Documents[1] $2,450.00
6.2 Submitting 2 days Fri Mon 0% 35 Documenter $800.00

the reports 4/27/18 4/30/18
6.3 Signing off 1 day Tue
5/1/18
Tue
5/1/18 0% 36 Project Manager $640.00
6.4 Go Live
Software 2 days Wed
5/2/18
Thu
5/3/18 0% 37 IT Engineer $1,120.00
6.5 Project is
closed 1 day Fri
5/4/18
Fri
5/4/18 0% 38 Project Manager $640.00
G. Modified Project
G1. Project Progress (50%-70%)
The project evaluation was done on the basis of keeping the project progress of two third
of the overall duration and it was scheduled on 13th March, 2018. The following table would
show the progress of the project activities till the mentioned date,
WBS Task Name Duration Start Finish % Complete
0 Software Development Project 107 days Thu 12/7/17 Fri 5/4/18 69%
1 Project Initialization 27 days Thu 12/7/17 Fri 1/12/18 100%
1.1 Concept review process 5 days Thu 12/7/17 Wed
12/13/17 100%
1.2 Resource Accumulation 10 days Thu 12/14/17 Wed
12/27/17 100%
1.3 Initial Documentation 4 days Thu 12/28/17 Tue 1/2/18 100%
1.4 Charter Documentation 4 days Wed 1/3/18 Mon 1/8/18 100%
1.5 Submission of the Documents 2 days Tue 1/9/18 Wed 1/10/18 100%
1.6 Review and Signup 2 days Thu 1/11/18 Fri 1/12/18 100%
2 Plan Development 13 days Mon 1/15/18 Wed 1/31/18 100%
2.1 Plan Outline development 5 days Mon 1/15/18 Fri 1/19/18 100%
2.2 Review of the plan 3 days Mon 1/22/18 Wed 1/24/18 100%

2.3 Complete Plan Development 4 days Thu 1/25/18 Tue 1/30/18 100%
2.4 Plan Approval 1 day Wed 1/31/18 Wed 1/31/18 100%
3 Designing of the Software 22 days Thu 2/1/18 Fri 3/2/18 100%
3.1 Selection of design platform 2 days Thu 2/1/18 Fri 2/2/18 100%
3.2 Obtaining the tool required for
designing 4 days Mon 2/5/18 Thu 2/8/18 100%
3.3 Making Design of the software 5 days Fri 2/9/18 Thu 2/15/18 100%
3.4 Simulation of the design made 4 days Thu 2/22/18 Tue 2/27/18 100%
3.5 Modification of the design
made 2 days Wed 2/28/18 Thu 3/1/18 100%
3.6 Design Approval 1 day Fri 3/2/18 Fri 3/2/18 100%
4 Database Development 21 days Thu 2/1/18 Thu 3/1/18 100%
4.1 Selection of database platform 2 days Thu 2/1/18 Fri 2/2/18 100%
4.2 Database Migration 5 days Mon 2/5/18 Fri 2/9/18 100%
4.3 Prototype testing 8 days Mon 2/12/18 Wed 2/21/18 100%
4.4 Storage Media is selected 2 days Thu 2/22/18 Fri 2/23/18 100%
4.5 Stored in the new storage
device 3 days Mon 2/26/18 Wed 2/28/18 100%
4.6 Database is completed 1 day Thu 3/1/18 Thu 3/1/18 100%
5 Software Development 33 days Mon 3/5/18 Wed 4/18/18 21%
5.1 User Interface is developed 5 days Mon 3/5/18 Fri 3/9/18 100%
5.2 Functions are aligned 6 days Mon 3/12/18 Mon 3/19/18 33%
5.3 Coding the program for the
software function 10 days Tue 3/20/18 Mon 4/2/18 0%
5.4 Black box testing 5 days Tue 4/3/18 Mon 4/9/18 0%
5.5 White box testing 5 days Tue 4/10/18 Mon 4/16/18 0%
5.6 Software is developed 2 days Tue 4/17/18 Wed 4/18/18 0%

6 Documentation and closure 12 days Thu 4/19/18 Fri 5/4/18 0%
6.1 Making final reports 6 days Thu 4/19/18 Thu 4/26/18 0%
6.2 Submitting the reports 2 days Fri 4/27/18 Mon 4/30/18 0%
6.3 Signing off 1 day Tue 5/1/18 Tue 5/1/18 0%
6.4 Go Live Software 2 days Wed 5/2/18 Thu 5/3/18 0%
6.5 Project is closed 1 day Fri 5/4/18 Fri 5/4/18 0%
G2. Third Corrective Crashing
The final crashing was done for ensuring the development of the project in the most
optimistic time and budget. A junior engineer was employed for decreasing the duration of the
remaining activities and ensuring it would be completed in the estimated time duration. The
features of the crashing are,
a) Overall project duration was decreased to 97 days from the 107 days after second
crashing
b) Increase of the progress to 75% till 13th march, 2018 for increasing the project
progress
c) Decrease of the project budget to $61,240.00 from the budget of $65,920.00
WB
S Task Name Duratio
n Start Finish
%
Complet
e
Predecessor
s
Resource
Names Cost
0
Software
Development
Project
97 days Thu
12/7/17
Fri
4/20/18 75% $61,240.0
0
1 Project
Initialization 27 days Thu
12/7/17
Fri
1/12/18 100% $18,128.00

1.1 Concept
review process 5 days Thu
12/7/17
Wed
12/13/1
7
100% Project
Manager $3,200.00
1.2 Resource
Accumulation 10 days
Thu
12/14/1
7
Wed
12/27/1
7
100% 2
Project
Manager,
Computer
Devices[1],
Network
Connection[1]
,
Equipments[1]
$9,548.00
1.3 Initial
Documentation 4 days
Thu
12/28/1
7
Tue
1/2/18 100% 3 Documenter,
Documents[1] $1,650.00
1.4 Charter
Documentation 4 days Wed
1/3/18
Mon
1/8/18 100% 4 Documenter,
Documents[1] $1,650.00
1.5
Submission
of the
Documents
2 days Tue
1/9/18
Wed
1/10/18 100% 5 Documenter $800.00
1.6 Review and
Signup 2 days Thu
1/11/18
Fri
1/12/18 100% 6 Project
Manager $1,280.00
2 Plan
Development 13 days Mon
1/15/18
Wed
1/31/18 100% $5,440.00
2.1
Plan
Outline
development
5 days Mon
1/15/18
Fri
1/19/18 100% 7 Planner $1,800.00
2.2 Review of
the plan 3 days Mon
1/22/18
Wed
1/24/18 100% 9 Planner $1,080.00
2.3
Complete
Plan
Development
4 days Thu
1/25/18
Tue
1/30/18 100% 10 Planner,
Assistant $1,920.00
2.4 Plan
Approval 1 day Wed
1/31/18
Wed
1/31/18 100% 11 Project
Manager $640.00
3 Designing of
the Software 18 days Thu
2/1/18
Mon
2/26/18 100% $9,378.00
3.1 Selection of
design platform 2 days Thu
2/1/18
Fri
2/2/18 100% 12 Designer $1,040.00
3.2
Obtaining
the tool
required for
designing
4 days Mon
2/5/18
Thu
2/8/18 100% 14
Designer,
Designing
tool[1]
$2,679.00
3.3
Making
Design of the
software
5 days Fri
2/9/18
Thu
2/15/18 100% 15 Designer $2,600.00
3.4
Simulation
of the design
made
4 days Fri
2/16/18
Wed
2/21/18 100% 16,23
Simulation
Software[1],
Tester
$1,459.00
3.5 2 days Thu Fri 100% 17 Designer $1,040.00

Modification of
the design made 2/22/18 2/23/18
3.6 Design
Approval 1 day Mon
2/26/18
Mon
2/26/18 100% 18 IT Engineer $560.00
4 Database
Development 14 days Thu
2/1/18
Tue
2/20/18 100% $8,888.00
4.1
Selection of
database
platform
2 days Thu
2/1/18
Fri
2/2/18 100% 12 Database
Developer $1,200.00
4.2 Database
Migration 2 days Mon
2/5/18
Tue
2/6/18 100% 21
Database
Developer,
Junior
Engineer
$1,520.00
4.3 Prototype
testing 4 days Wed
2/7/18
Mon
2/12/18 100% 22
Prototype
Software[1],
Tester, Junior
Engineer
$2,109.00
4.4
Storage
Media is
selected
2 days Tue
2/13/18
Wed
2/14/18 100% 23 IT Engineer $1,120.00
4.5
Stored in
the new storage
device
3 days Thu
2/15/18
Mon
2/19/18 100% 24
Database
Developer,
Storage
Device[1]
$2,299.00
4.6 Database is
completed 1 day Tue
2/20/18
Tue
2/20/18 100% 25 Project
Manager $640.00
5 Software
Development 27 days Tue
2/27/18
Wed
4/4/18 41% $13,756.00
5.1
User
Interface is
developed
2 days Tue
2/27/18
Wed
2/28/18 100% 26,19
IT Engineer,
Junior
Engineer
$1,440.00
5.2 Functions
are aligned 3 days Thu
3/1/18
Mon
3/5/18 100% 28
IT Engineer,
Junior
Engineer
$2,160.00
5.3
Coding the
program for the
software
function
10 days Tue
3/6/18
Mon
3/19/18 60% 29
IT Engineer,
Coding
Software[1]
$5,809.00
5.4 Black box
testing 5 days Tue
3/20/18
Mon
3/26/18 0% 30
Testing
Software[1],
Tester
$1,769.00
5.5 White box
testing 5 days Tue
3/27/18
Mon
4/2/18 0% 31
Testing
Software[1],
Tester
$1,769.00
5.6 Software is
developed 2 days Tue
4/3/18
Wed
4/4/18 0% 32
Testing
Software[1],
Tester
$809.00
6 12 days Thu Fri 0% $5,650.00

Documentatio
n and closure 4/5/18 4/20/18
6.1 Making
final reports 6 days Thu
4/5/18
Thu
4/12/18 0% 33 Documenter,
Documents[1] $2,450.00
6.2 Submitting
the reports 2 days Fri
4/13/18
Mon
4/16/18 0% 35 Documenter $800.00
6.3 Signing off 1 day Tue
4/17/18
Tue
4/17/18 0% 36 Project
Manager $640.00
6.4 Go Live
Software 2 days Wed
4/18/18
Thu
4/19/18 0% 37 IT Engineer $1,120.00
6.5 Project is
closed 1 day Fri
4/20/18
Fri
4/20/18 0% 38 Project
Manager $640.00
H. Project Conclusion
It can be concluded from the assignment that the development of the project would allow
the integration of the operations and it would also allow the analysis of the system integration.
The project plan had been completed in 6 sub-projects or work packages namely Project
Initialization, Plan Development, Designing of the Software, Database Development, Software
Development, and Documentation and closure. The project initialization had consisted of the
following activities concept review process, resource accumulation, initial documentation,
review and signup, submission of the documents, and charter documentation. The plan
development consisted of plan outline development, review of the plan, complete plan
development, and plan approval. The designing of the software consisted of selection of design
platform, obtaining the tool required for designing, making design of the software, simulation of
the design made, modification of the design made, and design approval. The database
development consisted of selection of database platform, database migration, prototype testing,
storage media is selected, stored in the new storage device, and database is completed. The
software development consisted of user interface is developed, functions are aligned, coding the
program for the software function, black box testing, white box testing, and software is

developed. The documentation and closure consisted of making final reports, submitting the
reports, signing off, go live software, and project is closed.

Bibliography
Bury, R. 2017. Carillion under pressure to inject funds amid growing pension concerns. [online]
The Telegraph. Available at: http://www.telegraph.co.uk/business/2017/07/15/carillion-pressure-
inject-funds-amid-growing-pension-concerns/ [Accessed 20 Nov. 2017].
Cable, J. and Cheung, C., 2017. Eight Principles of Effective Online Teaching: A Decade-Long
Lessons Learned in Project Management Education.
Cicmil, S., Cooke-Davies, T., Crawford, L. and Richardson, K., 2017, April. Exploring the
complexity of projects: Implications of complexity theory for project management practice.
Project Management Institute.
Coombs, W.T., 2014. Ongoing crisis communication: Planning, managing, and responding.
Sage Publications.
Devaux, S.A., 2014. Managing Projects as Investments: Earned Value to Business Value. CRC
press.
Fleming, Q.W. and Koppelman, J.M., 2016, December. Earned value project management.
Project Management Institute.
Flyvbjerg, B., 2013. From Nobel prize to project management: getting risks right. arXiv preprint
arXiv:1302.3642.
Ganesh, M.K.S. and Thanushkodi, K., 2015. An efficient software cost estimation technique
using fuzzy logic with the aid of optimization algorithm. International Journal of Innovative
Computing, Vol11 (2) Pp-587-597.

Hegazy, T., 2013. Computer-Based Construction Project Management: Pearson New
International Edition. Pearson Higher Ed.
Heldman, K., 2015. PMP project management professional exam deluxe study guide: updated
for the 2015 Exam. John Wiley & Sons.
Keatley, D.A., Ferguson, E., Lonsdale, A. and Hagger, M.S., 2017. Lay understanding of the
causes of binge drinking in the United Kingdom and Australia: a network diagram
approach. Health education research, 32(1), pp.33-47.
Kerzner, H., 2013. Project management: a systems approach to planning, scheduling, and
controlling. John Wiley & Sons.
Larson, E.W. and Gray, C., 2013. Project Management: The Managerial Process with MS
Project. McGraw-Hill.
Li, T., Qiu, W.G., Wang, L.C. and Man, S., 2013. study of project duration risk in the network
diagram based on matrix algorithm. In Applied Mechanics and Materials (Vol. 405, pp. 3401-
3405). Trans Tech Publications.
Martin, B., 2017. The politics of electricity planning in South Africa: A review of dominant
advocacy coalitions seeking to influence the Integrated Resource Plan of 2010 (IRP2010), and
its update in 2013 (Doctoral dissertation, University of Cape Town).
Martinelli, R.J. and Milosevic, D.Z., 2016. Project management toolbox: tools and techniques
for the practicing project manager. John Wiley & Sons.
Martone, R.G., Erickson, A., Mach, M., Hale, T., McGregor, A., Prahler, E.E., Foley, M.,
Caldwell, M. and Hartge, E.H., 2016, February. EcoPrinciples Connect: A Pilot Project

Matching Ecological Principles with Available Data to Promote Ecosystem-Based Management.
In AGU Fall Meeting Abstracts.
Mir, F.A. and Pinnington, A.H., 2014. Exploring the value of project management: linking
project management performance and project success. International journal of project
management, 32(2), pp.202-217.
Mohammad, I., van den Broek, H., Boots, M.L. and Wong, R., Oracle International Corporation,
2016. Showing relationships between tasks in a Gantt chart. U.S. Patent 9,336,502.
Nakamura, S., Kaneko, K., Okada, Y., Yin, C. and Ogata, H., 2015. Cubic gantt chart as
visualization tool for learning activity data. In 23rd International Conference on Computers in
Education, ICCE 2015. Asia-Pacific Society for Computers in Education.
Nam, S., Lee, D.K., Jeong, Y.K., Lee, P. and Shin, J.G., 2016. Environmental impact assessment
of composite small craft manufacturing using the generic work breakdown
structure. International Journal of Precision Engineering and Manufacturing-Green
Technology, 3(3), pp.261-272.
Nicholas, J.M. and Steyn, H., 2017. Project management for engineering, business and
technology. Taylor & Francis.
Pritchard, C.L. and PMP, P.R., 2014. Risk management: concepts and guidance. CRC Press.
Sallis, E., 2014. Total quality management in education. Routledge.
Schwalbe, K., 2015. Information technology project management. Cengage Learning.

Sears, S.K., Sears, G.A., Clough, R.H., Rounds, J.L. and Segner, R.O., 2015. Construction
project management. John Wiley & Sons.
Siami-Irdemoosa, E., Dindarloo, S.R. and Sharifzadeh, M., 2015. Work breakdown structure
(WBS) development for underground construction. Automation in Construction, 58, pp.85-94.
Svejvig, P. and Andersen, P., 2015. Rethinking project management: A structured literature
review with a critical look at the brave new world. International Journal of Project
Management, 33(2), pp.278-290.
Turner, R., 2016. Gower handbook of project management. Routledge.
Walker, A., 2015. Project management in construction. John Wiley & Sons.
Yildiz, A.E., Dikmen, I., Birgonul, M.T., Ercoskun, K. and Alten, S., 2014. A knowledge-based
risk mapping tool for cost estimation of international construction projects. Automation in
Construction, 43, pp.144-155.