PRMG010 - Project Planning & Control Techniques: Feasibility Analysis

This document presents a comprehensive project management solution, developed in accordance with the guidelines provided by The American University in Cairo for the course PRMG010: Project Planning and Control Techniques. It encompasses several key aspects of project management, beginning with project planning using Gantt charts and resource allocation, detailing the resources required along with their costs. The analysis identifies the overall project duration and critical path, distinguishing between critical and non-critical tasks. Further, the study includes a feasibility analysis for project crashing, evaluating the potential benefits of reducing indirect costs. The document also provides a progress evaluation and details of corrective crashing measures implemented to optimize project timelines and costs. The final modified project schedule reflects these adjustments, aiming for efficient project execution and successful completion.

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