55 53 56 54 Load software to deployed hardware 57 55 Testing 58 56 Validate startup on deployed hardware 59 60 57 58 Perform OS testing Perform application testing 61 59 Obtain formal sign-off from users 42 40 43 41 44 42 Obtain approval for project plan Executing Hardware 2 7 4 V 45 43 Procure hardware from suppliers 10 24 32 23 V 46 44 Software 47 45 Obtain software OS licenses 6 11 20 12 V 48 46 Obtain software application licenses 6 8 17 9 49 47 Pilot Testing 50 48 Setup test area 1 2 2 2 51 49 Load software onto pilot machines 4 6 8 6 V 52 50 53 51 54 52 Validate functionality Deployment Configure production hardware Deploy production hardware 3 6 8 6 10 25 33 24 V 11 19 23 18 V 12 17 19 17 V 4 9 18 10 V 4 8 17 9 4 19 28 18 V 6 17 24 16 62 60 Monitoring and Controlling 63 61 Formal Customer Review 1 64 62 Hold formal customer review after project plan approval 1 3 4 3 V 65 63 Update project plan 4 10 20 11 66 64 Formal Customer Review 2 67 65 Obtain updates regarding key deliverables from project te 5 18 22 17 V 68 66 Hold formal customer review after pilot testing 5 7 11 7 V 69 67 Update project plan 4 8 15 9 70 68 Closing 71 69 External 72 70 Finalize procurement with suppliers 5 18 24 17 73 71 Customer Approval 74 72 Hold final customer review 1 2 2 2 V 75 73 Prepare/submit final customer report 3 6 10 6 V 76 74 Audit against contractual deliverables 3 5 8 5 77 75 Obtain final customer approval 2 3 4 3 V 78 76 Internal 79 77 80 78 Hold lessons learned meeting Update final internal report 1 1 1 1 4 6 12 7 V 81 79 Hold project team celebration event 1 1 2 1 V 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 Expected Project Finish Time: days Total Critical Path Variance: Total Critical Path Standard Deviation: Probability of finishing the project in 287 days is Probability of finishing the project in 273 days is 000000 days days Optimistic Duration ID Task (days) Most Likely Duration Pessimistic Duration (days) (days) PERT Expected Duration (days) Critical Path Variance 1 TECHNOLOGY REFRESH (VERSION B) PROJECT 2 Initiating 3 Meet with key stakeholders 4 Finalize statement of work 5 Secure project team leads 6 Finalize stakeholder register 7 Develop project charter 8 9 Planning 10 11 12 Finalize project charter Scope Planning Requirements Develop/finalize functional requirements 2 3 12 2 10 15 4 10 V V 2 2 4 2 2 10 13 9 V 2 5 17 7 2 4 8 4 v 10 18 28 18 V 13 Develop/finalize hardware requirements 12 16 18 16 14 Develop/finalize software requirements 10 16 30 17 15 Develop/finalize requirements traceability matrix 11 14 28 16 16 Finalize project deliverables 2 2 3 2 V 17 Develop scope statement 4 9 10 8 V 18 Finalize/Update WBS 2 3 5 3 V 19 Schedule (Time) and Cost Planning 20 Finalize hardware/software costs 2 4 5 4 21 Update activities and duration estimates 6 12 14 11 V 22 Human Resource Planning 23 Finalize resource requirements 6 10 14 10 24 Finalize project costs 4 11 19 11 25 Identify training requirements 2 4 5 4 26 Complete training activities 6 12 14 11 V V 27 Quality Planning 28 Determine impacted quality processes 2 3 4 3 V 29 Finalize quality management plan 2 10 18 10 30 Risk Planning 31 Update project risks 3 6 12 7 V 32 Draft risk register 2 3 8 4 33 Finalize risk management plan 2 4 7 4 34 Finalize Project Plan 35 Finalize communications management plan 2 3 4 3 36 Finalize procurement management plan 2 6 14 7 37 Finalize stakeholder management plan 2 2 5 3 38 39 Finalize project schedule/cost baseline Finalize project plan 2 13 19 12 2 5 16 6 40 Obtain approval for project plan 2 4 7 4 V V 41 Executing 42 Hardware 43 Procure hardware from suppliers 10 24 32 23 V 44 Software 45 Obtain software OS licenses 6 11 20 12 V 46 Obtain software application licenses 6 8 17 9 47 Pilot Testing 48 Setup test area 1 2 2 2 49 Load software onto pilot machines 4 6 8 6 V 50 Validate functionality 3 6 8 6 51 Deployment 52 Configure production hardware 10 25 33 24 V 53 54 Deploy production hardware Load software to deployed hardware 11 19 23 18 V 12 17 19 17 V 55 Testing 56 Validate startup on deployed hardware 4 9 18 10 V 57 Perform OS testing 4 8 17 9 58 Perform application testing 4 19 28 18 V 59 Obtain formal sign-off from users 6 17 24 16 60 Monitoring and Controlling 61 Formal Customer Review 1 62 Hold formal customer review after project plan approval 1 3 4 3 V 63 Update project plan 4 10 20 11 64 Formal Customer Review 2 65 Obtain updates regarding key deliverables from project te 5 18 22 17 V 66 Hold formal customer review after pilot testing 5 7 11 7 V 67 Update project plan 4 8 15 9 68 Closing 69 External 70 Finalize procurement with suppliers 5 18 24 17 71 Customer Approval 72 Hold final customer review 1 73 Prepare/submit final customer report 3 26 2 2 V 10 6 V
Calculate the following:
1. The expected project finish time.
2. The variances for the applicable tasks.
3. The total critical path variance.
4. The total critical path standard deviation.
The customer has seen the Technology Refresh (Version B) Project schedule and the expected project finish time. However, the customer is concerned about the schedule risk of the project. Therefore, he wishes to know the following (i.e., determine the following):
5. The
6. The probability of finishing the project in 273 days.
Hint: Before answering the questions, review the "PERT Variance and Probability of Project Completion" video, located in the Topic 4 Resources.
7. If you wish to solve probabilities of finishing using the Z-value approach, refer to "Table E - The Standard
8. Note also that Microsoft Excel's NORM.DIST
Trending now
This is a popular solution!
Step by step
Solved in 2 steps