IT 328 Final Project Milestone One Guidelines and Rubric Introduction, Stakeholders, and Roles Overview: In Milestone One, you will begin your progress toward successful completion of your final project, the risk analysis and mitigation memo. It is important to note that this milestone addresses Section I, Parts A and B of your final project. For purposes of this activity, these items have been further broken down in the milestone activity than they will be in the final version of your project. This is meant to help guide you through all the aspects of this point in your learning experience. You will start by reviewing the project scenario and some key documents that contain information about the student degree progress project that are provided for you in the Project Management Documents Excel workbook. Your work on this milestone will help you successfully develop several elements of Section I of the final project, including discussion of the purpose of the student degree progress project, its objectives, the location of information about the project, and the roles and responsibilities of project team members. Prompt: As you go through these documents, think of yourself as a member of this team. In the following activity, you will use those documents to make key connections. While the project charter is in its own Word document, the Student Degree Progress Project Charter, the RACI and WBS charts are included in the Excel workbook that you will use to complete this assignment. Go through each labeled tab to access each key piece of information. You will continue to refer back to these documents throughout your work on the milestones leading to your final submission. You may reference the elements in this document to support your answers, using text and screenshots as needed. Your submission for Milestone One should address the following critical elements: I. Introduction to the Project: Keep this area as concise as possible (1 to 2 paragraphs) while ensuring you fully accomplish the following: Explain the purpose of the student degree progress project. Describe the end objectives or project outcomes. Explain where this information is documented in the artifacts you are using and provide an attachment of the specific documentation you used to obtain this information. Remember, your email memo will want to refer your reader very specifically to key areas in the attachments you provide so that your leadership team can dig into it as needed. II. Key Stakeholders and Roles: In this area, you will describe all of the project roles in a detailed paragraph. These descriptions of each team member's role are important and are often used for stakeholder audiences. For instance, this information may be used when the project work structure is presented to department management for comment and approval. You may organize this area as you wish; as a rule of thumb, you will likely need a complete paragraph to fully address the following for each role: List the team members identified in the project documentation and their project roles accurately. Describe the relevant function or general behavior of each role specific to this project. Explain the significance of each role specific to the phases of the project that the role is involved in. List the assigned tasks for each role. Rubric Guidelines for Submission: Milestone One must be submitted to Blackboard as a Word document. Your submission should be clear, coherent, concise, and free of errors. Instructor Feedback: This activity uses an integrated rubric in Blackboard. Students can view instructor feedback in the Grade Center. For more information, review these instructions. Attempted With Minimal or No Functional Issues (100%) Attempted With Significant Functional Issues (75%) Introduction: Purpose Clearly and concisely explains the purpose of the project with minimal or no issues Explains the purpose of the project, but explanation may be inaccurate, unclear, or too long for the occasion Does not explain the purpose of the project 12.86 Introduction: End Objectives Clearly and concisely explains the end objectives or project outcomes with minimal or no issues Explains the end objectives or project outcomes, but explanation may be inaccurate, unclear, or too long for the occasion Does not explain the end objectives or project outcomes 12.86 Clearly and specifically explains where information is documented Explains where information is documented but explanation may be inaccurate, unclear, lacking in specificity, or not supported by the artifacts in the attachment Does not explain where information is documented 12.86 Stakeholders/Roles: Members Lists the team members and their project roles with minimal or no issues related to accuracy Lists the team members and their project roles but with significant issues related to accuracy Does not list the team members and their project roles 12.86 Stakeholders/Roles: Relevant Function of the Role Describes the relevant function or general behavior of each role with minimal or no issues related to accuracy Describes the relevant function or general behavior of each role but with significant issues related to accuracy Does not describe the relevant function or general behavior of each role 12.86 Stakeholders/Roles: Significance Explains the significance of the role specific to the phases of the project that the role is involved in with minimal or no issues related to accuracy Explains the significance of the role specific to the phases of the project that the role is involved in but with significant issues related to accuracy Does not explain the significance of each role specific to the phases of the project that the role is involved in 12.86 Stakeholders/Roles: Assigned Tasks Lists the assigned tasks for each role with minimal or no issues related to accuracy Lists the assigned tasks for each role but with significant issues related to accuracy Does not list the assigned tasks for each role 12.86 Articulation of Response Submission has no major errors related to grammar, spelling, syntax, or organization Submission has major errors related to grammar, spelling, syntax, or organization that negatively impact readability and articulation of main ideas Submission has critical errors related to grammar, spelling, syntax, or organization that prevent understanding of ideas 9.98 Total 100% Critical Element Introduction: Documentation Not Evident in Submission (0%) Value