Download and examine the project task list from the link provided in the module. Based on this task list, you will create a PERT chart and write a paper that discusses the following:Identify which set of tasks create the critical path.Determine which task would be best to crash to reduce the critical path.Determine if there is a change to the critical path by crashing the task. Is there a new critical path?What other information would be beneficial to know to see if the selected task was the best option for crashing?Your paper should be 2-to-3-pages, well written and in conformity with the CSU Global Writing Center (Links to an external site.) for style and writing expectations. Your PERT chart is part of your page requirements. Include a title page and a reference page that includes at least two outside references (in addition to your textbook) to support your analysis. Task Task Description Days to Complete Cost Days after Crash Cost after Crash Days Reduced Crash Cost Cost Per Day Reduced AB Develop plans for product 5 $ 1,500.00 3 $ 1,900.00 BC Have programmers customize software 7 $ 2,500.00 4 $ 3,300.00 BD Have engineer customize hardware 6 $ 1,800.00 5 $ 2,200.00 CE Have quality officer test software 4 $ 2,200.00 3 $ 2,800.00 DE Place hardware within casing 3 $ 1,400.00 2 $ 1,900.00 EF Install software onto hardware 7 $ 1,900.00 5 $ 2,200.00 Tasks are in (START) (STOP) formats. So, task AB starts at point A and ends at point B. For tasks BC and BD, they both start when tasks AB ends (point B). Consider this your "dependency" for the project. While most traditional PERT charts have a weighted average, consider the days to complete and crash as the established weighted averages. You must create a PERT chart for both pre- and post-crashing.

OverviewYou are an IT support specialist at a help desk for a large company. Recently, the company created a knowledge base that IT support specialists can refer to when a user calls in with technology issues. The knowledge base has been helpful because the help desk receives many tickets and calls for what turn out to be the same issues. When IT support specialists have documents to refer to during a call or the review of a ticket, the knowledge base increases efficiencies and provides users with more consistent and higher quality support.As an IT support specialist at the company’s help desk, your project is to create documentation that will be added to the company’s knowledge base. This document will speak to the issues that users have experienced frequently within the past 30 days. To complete this activity, review the five ticket submissions. Then you will use your troubleshooting skills to assess the underlying causes of the users’ reported issues and how they should be resolved.PromptTroubleshooting Process: Create a document that explains what you would do for the first five steps of the troubleshooting process to resolve the issue stated in each ticket.The first step in the troubleshooting process is to gather information. Explain how you would identify the problems that users most commonly experience and call the IT help desk for, given the scenario.To explain how you would identify the problems, you might want to write what questions you would ask to gather the information you need to troubleshoot successfully.Since the second step of the troubleshooting process is to identify what has changed, explain how you would identify what may have changed in the system that may have caused the problems, based on the computing issue.Create a hypothesis of what you think the probable causes for the issues are, based on the information gathered in the first step. You may want to come up with several hypotheses.Although you are not physically going to determine the appropriate fix by testing your hypotheses, explain how you would test your hypotheses as a part of the troubleshooting process. You will also want to account for possible ramifications that you could cause by fixing the issue based on your hypotheses.Explain how you would implement the fix to verify the cause of the problem if you were the IT support specialist assisting users at the time.In some cases, it could be that the IT support specialist had already implemented the fix; explain if you would have handled it similarly or differently.Supporting MaterialsThe following resources support your work on the project:Reading: Five TicketsBefore starting your project, review the ticket submissions from the last 30 days to determine the common technical issues that users are experiencing.Guidelines for SubmissionTo complete this activity, you must upload a Word document that highlights the first five steps of the troubleshooting process for all five tickets. You will be graded on your troubleshooting skills for all five tickets in one grade.