Miami Dade College Process Improvement Project Plan
INTRODUCTIONProject implementation is one of the most important steps in project management and process improvement. Understanding the steps involved in implementation will ensure you are able to meet project milestones and goals. Providing a good plan for your project can aid in obtaining buy-in from key stakeholders when presenting your project to improve organizational operation. In this task, you will develop a project plan for the process improvement project you proposed in Task 1: Business Case. You will select a project management methodology, create a timeline, and create an acceptance plan for the project. You will also create a communication plan to explain the project's purpose, objective, and other important information. You will explain how the project will be monitored and how you can assess the quality and performance of the project. This task will assess your ability to communicate effectively with leadership and colleagues who are directly impacted by the process improvement initiative. You should complete Task 1 before working on this task. You will need to submit your completed “Business Case Template” from Task 1 with this task for evaluation to reference.SCENARIOThe “Fielder Community Hospital Scenario” can be found in the Supporting Documents section.REQUIREMENTSA. Submit the completed “Business Case Template” from Task 1.Note: The “Business Case Template” will only be used for reference and will not be evaluated in this task.Develop a plan to implement the HIM process improvement project that you proposed in Task 1, using the attached “Process Improvement Project Plan Template,” by doing the following:B. Select the Waterfall or Agile project management methodology for your process improvement project.1. Describe the project management methodology you selected for your process improvement project.2. Explain why you selected the project management methodology.3. Explain the outcome you hope to achieve using the selected methodology.C. List the major milestones, tasks, and deliverables for the process improvement project.D. Explain how the process improvement project will be implemented including the following: implementation process sequencing of the tasks resource allocation project team(s) structureE. Create a project timeline, using the attached “Project Timeline Template,” that includes the following: major milestones appropriate task sequencing task duration estimates task dependencies realistic start and end dates based on the project’s critical path task assignmentsF. Create an approval and acceptance plan for the process improvement project.1. Describe the acceptance criteria.2. Describe the levels of acceptance and approval, including the steps that will be taken if not approved.G. Create a communication plan for the process improvement project, including an explanation of the purpose, objective, frequency, approach, and medium.1. Explain how you will incorporate project meetings into your communication plan.H. Explain how progress will be monitored during the process improvement project.I. Explain how the quality and performance of the process improvement project will be managed.J. Explain how you will manage changes in the project, including change requests and scope creep.K. Explain how you will monitor and control project risks.L. Using the budget for the process improvement project from Task 1: Business Case, explain what factors may affect the budget.1. Explain how to manage changes to the original cost estimates.M. Explain how you will manage your teams, including team dynamics related to the project (e.g., change management, emotional intelligence, functions of a successful team).N. Explain how lessons learned will be documented after the process improvement project is completed.O. Acknowledge sources, using APA-formatted in-text citations and references, for content that is quoted, paraphrased, or summarized.P. Demonstrate professional communication in the content and presentation of your submission.File RestrictionsFile name may contain only letters, numbers, spaces, and these symbols: ! - _ . * ' ( )File size limit: 200 MBFile types allowed: doc, docx, rtf, xls, xlsx, ppt, pptx, odt, pdf, txt, qt, mov, mpg, avi, mp3, wav, mp4, wma, flv, asf, mpeg, wmv, m4v, svg, tif, tiff, jpeg, jpg, gif, png, zip, rar, tar, 7zRUBRICA:BUSINESS CASENOT EVIDENTThe completed “Business Case Template” from Task 1 is not provided.APPROACHING COMPETENCENot applicable.COMPETENTThe completed “Business Case Template” from Task 1 is provided.B:PROJECT MANAGEMENT METHODOLOGY SELECTIONNOT EVIDENTA project management methodology is not provided.APPROACHING COMPETENCEThe project management methodology selected is not appropriate for the process improvement project proposed in Task 1. Or the selected methodology is not Waterfall or Agile.COMPETENTThe project management methodology selected is appropriate for the process improvement project proposed in Task 1. The selected methodology is either Waterfall or Agile.B1:PROJECT MANAGEMENT METHODOLOGY DESCRIPTIONNOT EVIDENTA description of the selected project management methodology is not provided.APPROACHING COMPETENCEThe description of the selected project management methodology is not accurate.COMPETENTThe description of the selected project management methodology is accurate.B2:PROJECT MANAGEMENT METHODOLOGY RATIONALENOT EVIDENTAn explanation of why the project management methodology was selected is not provided.APPROACHING COMPETENCEThe explanation of why the project management methodology was selected is not logical.COMPETENTThe explanation of why the project management methodology was selected is logical.B3:OUTCOME OF USING THE SELECTED METHODOLOGYNOT EVIDENTAn explanation of the hopeful outcome using the selected methodology is not provided.APPROACHING COMPETENCEThe explanation of the hopeful outcome using the selected methodology is not logical.COMPETENTThe explanation of the hopeful outcome using the selected methodology is logical.C:MAJOR MILESTONES, TASKS, AND DELIVERABLESNOT EVIDENTA list of the major milestones, tasks, and deliverables for the process improvement project is not provided.APPROACHING COMPETENCEThe list of the major milestones, tasks, and deliverables for the process improvement project is not logical or not appropriate for the proposed process improvement project.COMPETENTThe list of the major milestones, tasks, and deliverables for the process improvement project is logical and appropriate for the proposed process improvement project.D:PROJECT IMPLEMENTATIONNOT EVIDENTAn explanation of how the process improvement project will be implemented is not provided.APPROACHING COMPETENCEThe explanation of how the process improvement project will be implemented is not logical or does not appropriately address any of the required elements, including implementation process, task sequencing, resource allocation, and project team(s) structure. Or the explanation only addresses some of the required elements.COMPETENTThe explanation of how the process improvement project will be implemented is logical and appropriately addresses all required elements, including implementation process, task sequencing, resource allocation, and project team(s) structure.E:PROJECT TIMELINENOT EVIDENTA project timeline is not provided.APPROACHING COMPETENCEThe project timeline does not include all the given elements, is not logical, or is not appropriate for the process improvement project.COMPETENTThe completed project timeline includes all the given elements, is logical, and is appropriate for the process improvement project.F:APPROVAL AND ACCEPTANCE PLANNOT EVIDENTAn approval and acceptance plan for the process improvement project is not provided.APPROACHING COMPETENCEThe approval and acceptance plan for the process improvement project is not logical.COMPETENTThe approval and acceptance plan for the process improvement project is logical.F1:ACCEPTANCE CRITERIANOT EVIDENTA description of the acceptance criteria is not provided.APPROACHING COMPETENCEThe description of the acceptance criteria is not logical, or the acceptance criteria is not appropriate for the approval and acceptance plan.COMPETENTThe description of the acceptance criteria is logical, and the acceptance criteria is appropriate for the approval and acceptance plan.F2:LEVELS OF ACCEPTANCE/APPROVALNOT EVIDENTA description of the levels of acceptance and approval is not provided.APPROACHING COMPETENCEThe description of the levels of acceptance and approval is not logical or does not address what steps will be taken if not approved.COMPETENTThe description of the levels of acceptance and approval is logical and addresses what steps will be taken if not approved.G:COMMUNICATION PLANNOT EVIDENTA communication plan for the process improvement project is not provided.APPROACHING COMPETENCEThe communication plan for the process improvement project is not logical or does not include a reasonable explanation of the purpose, objective, frequency, approach, and medium.COMPETENTThe communication plan for the process improvement project is logical and includes a reasonable explanation of the purpose, objective, frequency, approach, and medium.G1:PROJECT MEETINGSNOT EVIDENTAn explanation of how project meetings will be incorporated into the communication plan is not provided.APPROACHING COMPETENCEThe explanation of how project meetings will be incorporated into the communication plan is not logical.COMPETENTThe explanation of how project meetings will be incorporated into the communication plan is logical.H:PROGRESS MONITORINGNOT EVIDENTAn explanation of how progress will be monitored during the process improvement project is not provided.APPROACHING COMPETENCEThe explanation of how progress will be monitored during the process improvement project is not logical.COMPETENTThe explanation of how progress will be monitored during the process improvement project is logical.I:QUALITY AND PERFORMANCE MANAGEMENTNOT EVIDENTAn explanation of how the quality and performance of the project will be managed is not provided.APPROACHING COMPETENCEThe explanation of how the quality and performance of the project will be managed is not logical.COMPETENTThe explanation of how the quality and performance of the project will be managed is logical.J:CHANGE MANAGEMENTNOT EVIDENTAn explanation of how changes in the project will be managed is not provided.APPROACHING COMPETENCEThe explanation of how changes in the project will be managed is not logical or does not appropriately address change requests or scope creep.COMPETENTThe explanation of how changes in the project will be managed is logical and appropriately addresses change requests and scope creep. K:MONITOR AND CONTROL PROJECT RISKSNOT EVIDENTAn explanation of how project risks will be monitored and controlled is not provided.APPROACHING COMPETENCEThe explanation of how project risks will be monitored and controlled is not logical.COMPETENTThe explanation of how project risks will be monitored and controlled is logical.L:BUDGET IMPACTSNOT EVIDENTAn explanation of what factors will affect the budget is not provided.APPROACHING COMPETENCEThe explanation of what factors will affect the budget is not logical.COMPETENTThe explanation of what factors will affect the budget is logical.L1:MANAGING CHANGES TO THE ORIGINAL COST ESTIMATESNOT EVIDENTAn explanation of how to manage changes to the original cost estimates is not provided.APPROACHING COMPETENCEThe explanation of how to manage changes to the original cost estimates is not logical.COMPETENTThe explanation of how to manage changes to the original cost estimates is logical.M:TEAM MANAGEMENTNOT EVIDENTAn explanation of how teams will be managed is not provided.APPROACHING COMPETENCEThe explanation of how teams will be managed is not logical or does not appropriately address team dynamics related to the project (e.g., change management, emotional intelligence, functions of a successful team).COMPETENTThe explanation of how teams will be managed is logical and appropriately addresses team dynamics related to the project (e.g., change management, emotional intelligence, functions of a successful team).N:DOCUMENTING LESSONS LEARNEDNOT EVIDENTAn explanation of how lessons learned will be documented after the completed process improvement project is not provided.APPROACHING COMPETENCEThe explanation of how lessons learned will be documented after the completed process improvement project is not logical.COMPETENTThe explanation of how lessons learned will be documented after the completed process improvement project is logical.O:APA SOURCESNOT EVIDENTThe submission does not include in-text citations and references according to APA style for content that is quoted, paraphrased, or summarized.APPROACHING COMPETENCEThe submission includes in-text citations and references for content that is quoted, paraphrased, or summarized but does not demonstrate a consistent application of APA style.COMPETENTThe submission includes in-text citations and references for content that is quoted, paraphrased, or summarized and demonstrates a consistent application of APA style.P:PROFESSIONAL COMMUNICATIONNOT EVIDENTContent is unstructured, is disjointed, or contains pervasive errors in mechanics, usage, or grammar. Vocabulary or tone is unprofessional or distracts from the topic.APPROACHING COMPETENCEContent is poorly organized, is difficult to follow, or contains errors in mechanics, usage, or grammar that cause confusion. Terminology is misused or ineffective.COMPETENTContent reflects attention to detail, is organized, and focuses on the main ideas as prescribed in the task or chosen by the candidate. Terminology is pertinent, is used correctly, and effectively conveys the intended meaning. Mechanics, usage, and grammar promote accurate interpretation and understanding.SUPPORTING DOCUMENTS (attached)
