1. Make all revisions as suggested when I reviewed your previous lab submission. Do not re-submit your file with the same mistakes as this will affect your score.2. Use the Resource Sheet in Microsoft Project to create a resource pool. The resource pool is the list of resources that you will need to carry out your project activities, including people working on your project. When the Max-Units value is other than 100%, enter a resource note to explain your scheme. (1 point)3. Assign a standard rate for each resource as appropriate. Enter an overtime rate if you are planning for some of your project personnel to work overtime – this is optional. Entering pay rates allows Microsoft Project to calculate resource and activity costs for you. (1 points)4. Assign resources to all project activities that require resources; note that resources are NOT added to Summary tasks and usually not to milestones. Remember, project activities without resource assignments will not be performed. So you want to ensure that every activity that requires resources has a resource assignment. (2 points)5. When assigning resources, make sure that activity durations remain the same, unless you want them to change. Review your Project Statistics before and after resource assignments to document any change in your project duration. What did you see? Add a task note in Task Zero to share your observation. (1 points)6. Review your resource allocation and resolve all over allocations if there are any. If you believe that an over allocation is reasonable and does not need to be leveled, please add a resource note to explain why. Your explanation has to be realistic. (2 points)7. Switch to the Gantt Chart view, apply the Cost table, and note the total cost of the project. Remember, in MS Project, Task Zero is the project, unless you purposed structured your plan for task 1 to represent the entire project. Calculate 10% of the total cost of the project and add the amount as contingency reserve to your project (see below instructions on how toPlease see my feedback below.1) The project start date should be 7/06/2020 – the first working day of the first week of the class.2) You had too many constrained activities. Schedule constraints have a significant effect on schedule risk analysis results. They should be used sparingly, and only when the constraint reflects reality. Constraints to be particularly aware of are: • Must start on and Must finish on – preceding delays will not delay the task, and preceding time savings will not bring it earlier • Start on or after (SNET) and Finish on or after (FNET) – preceding time savings will not bring the task earlier. Consider removing these constraints and replacing them with logic (e.g. Finish-to-Start links) instead. Other types of constraints are less significant because they do not influence the tasks' dates, only their floats. For example, you can use a Finish on or before constraint to indicate a desired completion date of a task – this will not force the task to finish on that day, but the shortfall will be indicated in the task's float.3) The time unit of the schedule is Day.