Cloud Computing Project Crashing Analysis

This assignment delves into the complexities of project management by analyzing a cloud computing implementation project. It focuses on crashing techniques, examining how shortening project duration impacts budget and resource allocation. Students must interpret PERT diagrams, assess the consequences of crashing specific tasks, and understand the factors influencing successful project crashing.

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

1PROJECT MANAGEMENT
1) What is the estimated completion time for this project? What is the estimated project budget?
What is the probability that the project can be completed in 35 weeks? What is the critical path to
the project?
The estimated completion time for the project without crashing is given below,
WBS Task Name Duration Start Finish
0
Cloud Computing
Implementation in B & W
Organization
185 days Mon 1/1/18 Fri 9/14/18
1 Requirements 3 wks Mon 1/1/18 Fri 1/19/18
2 Market Assessment 7 wks Mon 1/22/18 Fri 3/9/18
3 Design 6 wks Mon 1/22/18 Fri 3/2/18
4 Development 7 wks Mon 3/5/18 Fri 4/20/18
5 Testing 9 wks Mon 4/23/18 Fri 6/22/18
6 Revising 5 wks Mon 6/25/18 Fri 7/27/18
7 Documentation 6 wks Mon 4/23/18 Fri 6/1/18
8 Quality Assurance 4 wks Mon 6/25/18 Fri 7/20/18
9 Pricing 2 wks Mon 3/12/18 Fri 3/23/18
10 Production 4 wks Mon 7/30/18 Fri 8/24/18
11 Distribution 3 wks Mon 8/27/18 Fri 9/14/18
Table 1: Estimated Time Duration of the Project without Crashing
The estimated completion time for the project with crashing is given below,
WBS Task Name Duration Start Finish
0
Cloud Computing
Implementation in B & W
Organization
165 days Mon 1/1/18 Fri 8/17/18
1 Requirements 3 wks Mon 1/1/18 Fri 1/19/18

2PROJECT MANAGEMENT
2 Market Assessment 6 wks Mon 1/22/18 Fri 3/2/18
3 Design 5 wks Mon 1/22/18 Fri 2/23/18
4 Development 6 wks Mon 2/26/18 Fri 4/6/18
5 Testing 8 wks Mon 4/9/18 Fri 6/1/18
6 Revising 4 wks Mon 6/4/18 Fri 6/29/18
7 Documentation 4 wks Mon 4/9/18 Fri 5/4/18
8 Quality Assurance 3 wks Mon 6/4/18 Fri 6/22/18
9 Pricing 2 wks Mon 3/5/18 Fri 3/16/18
10 Production 5 wks Mon 7/2/18 Fri 8/3/18
11 Distribution 2 wks Mon 8/6/18 Fri 8/17/18
Table 2: Estimated Time Duration of the Project with Crashing
The project budget for the project without Crashing is estimated to be,
WBS Task Name Cost
0 Cloud Computing Implementation in B & W
Organization $205,000.00
1 Requirements $10,000.00
2 Market Assessment $20,000.00
3 Design $15,000.00
4 Development $45,000.00
5 Testing $10,000.00
6 Revising $15,000.00
7 Documentation $20,000.00
8 Quality Assurance $10,000.00
9 Pricing $5,000.00

3PROJECT MANAGEMENT
10 Production $40,000.00
11 Distribution $15,000.00
Table 3: Project Cost Estimation of the Project without Crashing
The project budget for the project with Crashing is estimated to be,
WBS Task Name Cost
0 Cloud Computing Implementation in B & W
Organization $293,000.00
1 Requirements $10,000.00
2 Market Assessment $25,000.00
3 Design $30,000.00
4 Development $65,000.00
5 Testing $20,000.00
6 Revising $18,000.00
7 Documentation $30,000.00
8 Quality Assurance $15,000.00
9 Pricing $5,000.00
10 Production $50,000.00
11 Distribution $25,000.00
Table 4: Project Cost Estimation of the Project with Crashing
The probability that the project can be completed in 35 weeks can hold true when the
project is crashed or most optimistic scenario is considered. The probability of occurrence of the
event can be calculated as,
P(project can be completed in 35 weeks)= (Event(Most Optimistic)+ Event(Project
Crash))/ (Event(Most Optimistic)+ Event(Project Crash)+ Event(Most Likely)+ Event(Most
Pessimistic))

4PROJECT MANAGEMENT
= 2/4
= 0.5
The critical path for the project is,
014561011
The image for the critical path (shown in red boxes in the diagram) for the project is
given below,

5PROJECT MANAGEMENT
0
Cloud Computing
Implementation in B &
W Organization
1
Requirements
2
Market Assessment
3
Design
4
Development
5
Testing
6
Revising
7
Documentation
8
Quality Assurance
9
Pricing
10
Production
11
Distribution
0
1234567891 01 1
185 days 0%
1/1/18 9/14/18
3 weeks 0%
1/1/18 1/19/18
7 weeks 0%
1/22/18 3/9/18
6 weeks 0%
1/22/18 3/2/18
7 weeks 0%
3/5/18 4/20/18
9 weeks 0%
4/23/18 6/22/18
5 weeks 0%
6/25/18 7/27/18
6 weeks 0%
4/23/18 6/1/18
4 weeks 0%
6/25/18 7/20/18
2 weeks 0%
3/12/18 3/23/18
4 weeks 0%
7/30/18 8/24/18
3 weeks 0%
8/27/18 9/14/18
Figure 1: Critical path for the project

6PROJECT MANAGEMENT
2) What is the minimum expected time in which this project can be completed? What is the
probability of completing the project in this time?
The minimum expected time for the completion of the project is the most optimistic
scenario of the project and it is shown in the table below,
WBS Task Name Duration Start Finish
0
Cloud Computing
Implementation in B & W
Organization
145 days Mon 1/1/18 Fri 7/20/18
1 Requirements 2 wks Mon 1/1/18 Fri 1/12/18
2 Market Assessment 4 wks Mon 1/15/18 Fri 2/9/18
3 Design 5 wks Mon 1/15/18 Fri 2/16/18
4 Development 6 wks Mon 2/19/18 Fri 3/30/18
5 Testing 7 wks Mon 4/2/18 Fri 5/18/18
6 Revising 4 wks Mon 5/21/18 Fri 6/15/18
7 Documentation 3 wks Mon 4/2/18 Fri 4/20/18
8 Quality Assurance 2 wks Mon 5/21/18 Fri 6/1/18
9 Pricing 2 wks Mon 2/12/18 Fri 2/23/18
10 Production 3 wks Mon 6/18/18 Fri 7/6/18
11 Distribution 2 wks Mon 7/9/18 Fri 7/20/18
Table 5: Shortest Time Duration of the Project
The probability of occurrence of the event can be calculated as,
P(project can be completed in shortest)= Event(Most Optimistic)/ (Event(Most Optimistic)+
Event(Project Crash)+ Event(Most Likely)+ Event(Most Pessimistic))
= 1/4
= 0.25

7PROJECT MANAGEMENT
3) What is the additional cost for reducing the project time to the required 35 weeks? Which
specific tasks do you recommend crashing in order to achieve this milestone?
The additional cost for the project to complete in required 35 weeks= $293,000.00 - $205,000.00
= $88,000.00
The tasks that need to be crashed are given below,
Tasks Before Crashing Duration After Crashing Duration
2. Market Assessment 7 6
3. Design 6 5
4. Development 7 6
5. Testing 9 8
6. Revising 5 4
7. Documentation 6 4
8. Quality Assurance 4 3
9. Pricing 2 2
10. Production 4 5
11. Distribution 3 2
4) What are implications of crashing a project? In order to crash a project successfully, what are
factors need to be in place and considered?
The crashing of the project has the following impacts on the project Cloud Computing
Implementation in B & W Organization,
 Decrease of the duration of the project from 37 weeks to 35 weeks
 Increase of the project budget to $293,000.00 from $205,000.00
5) What is the impact on the crashing solution if the expected time for task B is increased from
seven to nine weeks?
The change in the crashing solution of the project when task B is increased from seven to nine
weeks is shown below,

8PROJECT MANAGEMENT
ID Task
Mode
WBS Task Name Duration Start Finish Predecessors
0 0 Cloud Computing
Implementation in B &
W Organization
165 days Mon 1/1/18 Fri 8/17/18
1 1 Requirements 3 wks Mon 1/1/18 Fri 1/19/18
2 2 Market Assessment 9 wks Mon 1/22/18 Fri 3/23/18 1
3 3 Design 5 wks Mon 1/22/18 Fri 2/23/18 1
4 4 Development 6 wks Mon 2/26/18 Fri 4/6/18 3
5 5 Testing 8 wks Mon 4/9/18 Fri 6/1/18 4
6 6 Revising 4 wks Mon 6/4/18 Fri 6/29/18 2,5
7 7 Documentation 4 wks Mon 4/9/18 Fri 5/4/18 4
8 8 Quality Assurance 3 wks Mon 6/4/18 Fri 6/22/18 3,5
9 9 Pricing 2 wks Mon 3/26/18 Fri 4/6/18 2
10 10 Production 5 wks Mon 7/2/18 Fri 8/3/18 6,7,8,9
11 11 Distribution 2 wks Mon 8/6/18 Fri 8/17/18 10
12/24 1/14 2/4 2/25 3/18 4/8 4/29 5/20 6/10 7/1 7/22 8/12 9/2
November 21 January 11 March 1 April 21 June 11 August 1 September 21
Figure 2: Change in the project
From the diagram, it can be seen that the overall duration of the project would remain unchanged.
6) What is the impact on the crashing solution if the expected time for task D is decreased to seven weeks?
The change in the crashing solution of the project when task D is decreased to seven weeks is shown below,

9PROJECT MANAGEMENT
ID Task
Mode
WBS Task Name Duration Start Finish
0 0 Cloud Computing
Implementation in B &
W Organization
170 days Mon 1/1/18 Fri 8/24/18
1 1 Requirements 3 wks Mon 1/1/18 Fri 1/19/18
2 2 Market Assessment 6 wks Mon 1/22/18 Fri 3/2/18
3 3 Design 5 wks Mon 1/22/18 Fri 2/23/18
4 4 Development 7 wks Mon 2/26/18 Fri 4/13/18
5 5 Testing 8 wks Mon 4/16/18 Fri 6/8/18
6 6 Revising 4 wks Mon 6/11/18 Fri 7/6/18
7 7 Documentation 4 wks Mon 4/16/18 Fri 5/11/18
8 8 Quality Assurance 3 wks Mon 6/11/18 Fri 6/29/18
9 9 Pricing 2 wks Mon 3/5/18 Fri 3/16/18
10 10 Production 5 wks Mon 7/9/18 Fri 8/10/18
11 11 Distribution 2 wks Mon 8/13/18 Fri 8/24/18
12/24 1/14 2/4 2/25 3/18 4/8 4/29 5/20 6/10 7/1 7/22 8/12 9/2
November 21 January 11 March 1 April 21 June 11 August 1 September 21
Figure 3: Change in the project
From the diagram, it can be seen that the overall duration of the project would change by 1 week.
7) Document the PERT diagram in MS Project?

10PROJECT MANAGEMENT
Figure 4: PERT diagram in MS Project