Conclusion on project management

The executive summary provides a brief overview of the entire project report, including the project's objectives, scope, and outcomes.

The project overview provides a detailed explanation of the project, including its purpose, goals, and the benefits it will provide.

This section includes a link to the exc

el sheet that shows the forward pass, backward pass, and critical path.

Without Leveling

This section includes links to two separate Projectlibre files; one file with resource over allocation and the second file showing after resources have been leveled.

The main motive behind crashing a project is to shorten the overall time taken to complete the project. It is done by reducing the time taken to complete individual task within the project by deploying additional resources. However, the project manager has to be varied of the deployment of additional resources and has to meticulously allocate the resources to the designated task in way that the cost of crashing the project is kept to the bare minimum.

In the project of Memory Caster, the owner has demanded us to complete the project within 30 days as she is very eager to start the business in the new location owing to increasing demand and overwhelming response from her clients.

In keeping with the demand from the owner of the Memory Caster, our team as the project managers have very meticulously calculated the possible ways the duration of the project can be shortened by crashing the project all the while containing the cost of crashing to the bare minimum, by following the below mentioned steps:

a) Identifying the Critical Task: The critical task in the project can be identified by drawing network diagram by applying the activity node method which uses arrows to identify the dependency of every task with each other. Then the Early Start, Early Finish, Late Start and Late Finish time is determined with the help of network diagram with help of the forward pass and back ward pass by using the duration allocated to each task. This will help us to determine the slack and the task which has zero slack time are the once that are identified as critical. The critical task are the tasks whose duration has to be shortened in order to efficiently crash the project. The below mentioned images identify the critical task in the network diagram:

Image: Network Diagram With all the Dependencies and Critical Task

The above image demonstrates the preparation of the network diagram using the activities on node method to identify the critical task in the project we are working on. All the activities in the blue box have a slack time of zero and hence they are identified as the critical task. The below mentioned tables highlights the activities and the slack time:

Thus, the critical path identified in the first stage are 1.1, 1.2, 1.3, 1.4, 1.6, 1.8, 1.9 and 1.10.

b) Determining the cost of crashing and the maximum crashing duration for each task:

After identify the critical path we have identified cost of crashing and the maximum crashing duration for each activity. The same has been calculated as per the below mentioned table:

In the above table the crash time denotes the minimum time required to complete a given task, with help of this number we have calculated the maximum number of days, a given task can be crashed. We have considered 150% of the normal cost while calculating the crash cost.

c) Calculating the impacting of crashing each critical path:

We have calculated the impact of crashing each critical task by one day in order to determine the task that can be crashed without baring on the cost of the project. Given below is the summarized table of Appendix_____ calculating the impact of crashing each critical task for a day:

Observation:

i. Task 1.4: The normal duration of the project is 33 days1.4., crashing the critical task 1.4 does not have any impact on the duration of the project, this is because of its dependency with the task 1.6 which starts together.

ii. Task 1.6: Again, critical task 1.6 does not have any impact on the duration of the project as its starts along with the 1.4.

iii. Task 1.4 and 1.6: When both the task 1.4 and 1.6 are crashed by 1 day the duration of the entire project moves up by 1 day however the cost of the increases by 0.72%.

iv. Task 1.8: On crashing the critical task 1.8 the duration of the entire project gets crashed by 1 day and the cost of the project increases by 0.21%.

v. Task 1.9: On crashing the critical task 1.9 by one day the duration of the project gets reduced by one day and the cost of the project increases by just 0.11%.

vi. Task 1.10: Similar to the critical task 1.9, task 1.10 reduces the duration of the project 1 day and the cost increases by just 0.11%.

Thus, we came to the conclusion that crashing the critical task 1.8, 1.9 and 1.10 will be the best option to crash the project without having severe impact on the cost of the project.

d) Implementing the best option for crashing the project:

Thus after meticulously calculating all the prospects of crashing the project following is the calculation of the crashing after choosing the best possible options:

On crashing the task 1.8 by 2 days, 1.9 by one day and 1.10 by one day we were able to crash the project to 29 days with a increase of just 1.42% in the cost of project.

The Network Diagra after crahing of the project is given below:

This section includes the project closure report, which outlines the project's successes, challenges, lessons learned, and recommendations for future projects.

The conclusion summarizes the key findings and outcomes of the project.

The recommendations section provides actionable suggestions for future projects based on the lessons learned from the current project.

10.1. Crashing:

10.1.A.