Can someone please help me with the following:

Before completing this assignment, be sure you have completed the material for Modules One and Two in uCertify, as this will help you recognize the content and functions of the RACI and WBS charts. In this assignment, you will begin your work with the course case scenario involving the student degree progress project. You will begin by examining three key project documents: the project charter, the RACI chart, and the WBS chart. The project charter is in the Student Degree Progress Project Charter document, while the RACI and WBS charts are included in the Project Management Documents Excel workbook. This workbook has multiple tabs. Using this information, you will address the questions and critical elements in the Milestone One Guidelines and Rubric document. You will compose a brief project description that summarizes the student degree progress project, including its purposes, objectives, and how and where to find further information about it. This is the type of communication project that team members typically provide for stakeholders. Your work on this milestone will help you prepare to compose sections of Part I of your final project, which introduces the student degree progress project and discusses roles and responsibilities within the project team. To complete this assignment, review the Milestone One Guidelines and Rubric document. 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 1, 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 1 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. Use this reference as an example, to assist you with writing a business memo. 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. . Project Scenario Regatta University is a leader in both traditional education and career-path development, including in emerging fields. The university prides itself on staying on the leading edge of curriculum and degree programs, learning methodologies and instructional technologies, student services, and demonstrated student success. "The future is here and now," the university's president, Martha Yoon, likes to say. Regatta serves approximately 8,000 students at locations including the original campus in Augusta, Maine, and satellite campuses in Ventura, California; Dayton, Ohio; and Hilo, Hawaii. In a typical term, approximately 40% of Regatta's students take courses at a distance through the university's online education hub. Enrollment growth has been strong, increasing by 4 to 8% each year for the last decade. You are a key member of the information technology team at Regatta, with a core specialization in student services. You are responsible for providing user-friendly interfaces connecting to a flexible, powerful information structure. Now you have a new project-working with colleagues to create a student degree progress tool that students will use for accurate, instant information on their progress toward program and degree completion. As you may imagine, this tool is eagerly awaited by a variety of stakeholders, including Regatta academic advisors and the Office of Enrollment Management, as tracking and communicating student progress toward degree completion is vital for retention. "We need a tool that will be easy to use but also accurate. No misinformation!" your team manager says. Project: Student Degree Progress DEPARTMENT Information Technology STEP Jane Smith John Doe Arthur Bowmar, Shila Cole Ana Fischer John Jones T A/R A/R A/R A/R A/R 1 2 3 4 5 6 C/I I I I C/I I I C/I I T A/R 7 A/R 8 A/R 9 DESCRIPTION Create the project charter Develop the project management plan Define the project scope Create a formal budget and budget plan Fill in a Gantt chart with the project schedule and milestones Develop a user interface mockup for review Create the architectural design for the front end of the application (user-facing) Create the architectural design for the back end of the application (for data processing) Develop the graphic user interface (GUI) for the degree tracker Develop the web code to receive data from the back end and place data within the GUI Develop the back-end code to process data and send it to the web application Create a defined test plan for all system components Test the scenarios defined in the test plan for proper application behavior Perform integration testing to ensure that the front-end components and back-end components speak to each other as well as integrate seamlessly with the rest of the web application A/R 10 A/R 11 A/R 12 C/I C/I A/R A/R 13 R R 14 I A/R R R 15 C/I A/R A/R I 16 17 18 19 20 Transition web application into production environment (go-live) Monitor project progress throughout its life cycle Manage project deliverables for records and hand-off Assess and manage risks throughout the project life cycle Develop the final project report Perform project reflections A/R A/R A/R A/R A/R R R R I I Project Risk Likelihood Implications There is a risk that severe weather in Sailcloth, Maine (the main campus that houses the development team), will close the campus and impact progress. Medium There is a risk that the ambiguity in the project scope (it only defines "graphical element" but not what type) will lead to requirement changes by the stakeholder during development, affecting both the budget and schedule. High There is a risk that sign-off on project deliverables (charter, Gantt chart, product approval, etc.) from project sponsors and stakeholders exceeds the allotted time. This decision delay will impact the progress schedule. Low There is a risk for rollout issues when deploying to production due to complexity of merging code with the "go-live" of another project on the same system. High Two projects are currently being developed at the same time in the same code base. Delays to the secondary project will cause delays to the Student Progress go-live. High The student portal where the project will be deployed is a high-availability system and is expected to be accessible for students 24/7. There is a risk that the large number of changes occurring during go-live could take the system offline, temporarily impacting system availability. Low There is a risk that an interpersonal conflict will arise within the team, impacting the human resources assigned to the project and potentially impacting the allotted schedule. Low Role Role Description Name Jane Smith John Doe Arthur Bowman Shila Cole Ana Fischer John Jones Document History Document Revision/Release Status Revision Date Description of Changes 0.1 6/29/15 Initial format 8/31/15 Initial draft Author / Editor Jane Smith John Doe 1.0 Executive Summary Students leverage a web portal to access university-related information and resources. Content within it can be targeted to all users or to those within a pre-specified role (e.g., students at a particular campus) or it can be user-specific. As an academic institution, one piece of information critical to students is their current progress in their degree program or programs. The purpose of the student degree progress project is to create an area to display user-specific academic progress. Project Purpose/Justification University leadership requested this project to promote student awareness and provide students easy access to their degree progress. Project Description Preliminary Scope Statement The purpose of this project is to create an area that displays user-specific academic progress within the appropriate roles, leveraging data through a back-end system. This project will include the necessary modifications to the back end to relay this information. More specifically, this project will include the following: Creating the graphical elements in a web-friendly format Creating the necessary web view to accommodate the graphical elements Creating the necessary changes to the back end to prepare data supporting the student information Creating the necessary web service to securely expose the student's information to the graphical elements and web view Out of Scope Due to business-specific processes, some students, particularly those who have been pursuing a degree for over four years, may not be able to see their academic progress using the deliverables of this project. Changes to the back end to expand this functionality are out of scope, as are any changes intended to enhance functionality to provide additional data beyond the academic progress already captured in another system. Project Objectives and Success Criteria The project will provide the functionality described within the preliminary scope statement. The project will be delivered without incurring any additional expenses. The project will be delivered free from any significant defects or without causing any down time. The project will be delivered no later than two weeks from the target time frame defined within the milestone schedule below. Constraints Additional funding is not available. The information available to students is derived from data within the back end and is as accurate, timely, and available as the source data and its structuring. Assumptions No major changes in formatting or scope will be presented during the life of the project. . 4 . Project Deliverables Project Charter Project Management Plan Design o User Interface Mockup o Architectural Design Test Plan Test Scenarios Project Resource Estimate The student degree progress project is estimated to use the following resources: Project Resource Estimate Resource Project Manager Systems Analyst Middleware Applications Developer Backend Systems Analyst Estimated Work Hours 48 Hours 12 Hours 44 Hours 50 Hours 154 Hours Total: Summary Milestone Schedule Summary Milestone Schedule - List key project milestones relative to project start Project Milestone Target Date Project Start September 1 Graphical Component Unit Complete September 23 Web View Unit Complete September 25 Backend Unit Complete October 7 Integration Testing Complete October 14 Submit to Leadership October 26 Leadership Acceptance November 2 Transition to Production November 5 Project Closeout November 13 Summary Budget Fiscal Year Summary Budget - List component project costs Project Component Hardware Software and Licensing Vendor Total Component Cost $0 $0 N/A $0 Project Approval Requirements The project will be completed once all requirements are met and all deliverables have been received and approved by the client. Role Project Sponsor Project Manager Core Stakeholder Vendor Resources Project Team Members Project Organization Name(s) - Department(s) Jane Smith John Doe Arthur Bowman None Shila Cole, Ana Fischer, John Jones Authorization Approval of this project charter provides authorization to move forward in accordance with the information contained in this document. Project Team John Doe, Project Manager Shila Cole, Systems Analyst Ana Fischer, Middleware Application Developer John Jones, Backend Systems Analyst Date: Date: Date: Date: Directors of Assigned Resources Michael Erdmann, Middleware Director Amber McLedon, Applications Director Cynthia Carmom, PMO Director/Acting Student Systems Director Date: Date: Date: Project Sponsor Jane Smith, Project Sponsor Date: Before completing this assignment, be sure you have completed the material for Modules One and Two in uCertify, as this will help you recognize the content and functions of the RACI and WBS charts. In this assignment, you will begin your work with the course case scenario involving the student degree progress project. You will begin by examining three key project documents: the project charter, the RACI chart, and the WBS chart. The project charter is in the Student Degree Progress Project Charter document, while the RACI and WBS charts are included in the Project Management Documents Excel workbook. This workbook has multiple tabs. Using this information, you will address the questions and critical elements in the Milestone One Guidelines and Rubric document. You will compose a brief project description that summarizes the student degree progress project, including its purposes, objectives, and how and where to find further information about it. This is the type of communication project that team members typically provide for stakeholders. Your work on this milestone will help you prepare to compose sections of Part I of your final project, which introduces the student degree progress project and discusses roles and responsibilities within the project team. To complete this assignment, review the Milestone One Guidelines and Rubric document. 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 1, 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 1 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. Use this reference as an example, to assist you with writing a business memo. 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. . Project Scenario Regatta University is a leader in both traditional education and career-path development, including in emerging fields. The university prides itself on staying on the leading edge of curriculum and degree programs, learning methodologies and instructional technologies, student services, and demonstrated student success. "The future is here and now," the university's president, Martha Yoon, likes to say. Regatta serves approximately 8,000 students at locations including the original campus in Augusta, Maine, and satellite campuses in Ventura, California; Dayton, Ohio; and Hilo, Hawaii. In a typical term, approximately 40% of Regatta's students take courses at a distance through the university's online education hub. Enrollment growth has been strong, increasing by 4 to 8% each year for the last decade. You are a key member of the information technology team at Regatta, with a core specialization in student services. You are responsible for providing user-friendly interfaces connecting to a flexible, powerful information structure. Now you have a new project-working with colleagues to create a student degree progress tool that students will use for accurate, instant information on their progress toward program and degree completion. As you may imagine, this tool is eagerly awaited by a variety of stakeholders, including Regatta academic advisors and the Office of Enrollment Management, as tracking and communicating student progress toward degree completion is vital for retention. "We need a tool that will be easy to use but also accurate. No misinformation!" your team manager says. Project: Student Degree Progress DEPARTMENT Information Technology STEP Jane Smith John Doe Arthur Bowmar, Shila Cole Ana Fischer John Jones T A/R A/R A/R A/R A/R 1 2 3 4 5 6 C/I I I I C/I I I C/I I T A/R 7 A/R 8 A/R 9 DESCRIPTION Create the project charter Develop the project management plan Define the project scope Create a formal budget and budget plan Fill in a Gantt chart with the project schedule and milestones Develop a user interface mockup for review Create the architectural design for the front end of the application (user-facing) Create the architectural design for the back end of the application (for data processing) Develop the graphic user interface (GUI) for the degree tracker Develop the web code to receive data from the back end and place data within the GUI Develop the back-end code to process data and send it to the web application Create a defined test plan for all system components Test the scenarios defined in the test plan for proper application behavior Perform integration testing to ensure that the front-end components and back-end components speak to each other as well as integrate seamlessly with the rest of the web application A/R 10 A/R 11 A/R 12 C/I C/I A/R A/R 13 R R 14 I A/R R R 15 C/I A/R A/R I 16 17 18 19 20 Transition web application into production environment (go-live) Monitor project progress throughout its life cycle Manage project deliverables for records and hand-off Assess and manage risks throughout the project life cycle Develop the final project report Perform project reflections A/R A/R A/R A/R A/R R R R I I Project Risk Likelihood Implications There is a risk that severe weather in Sailcloth, Maine (the main campus that houses the development team), will close the campus and impact progress. Medium There is a risk that the ambiguity in the project scope (it only defines "graphical element" but not what type) will lead to requirement changes by the stakeholder during development, affecting both the budget and schedule. High There is a risk that sign-off on project deliverables (charter, Gantt chart, product approval, etc.) from project sponsors and stakeholders exceeds the allotted time. This decision delay will impact the progress schedule. Low There is a risk for rollout issues when deploying to production due to complexity of merging code with the "go-live" of another project on the same system. High Two projects are currently being developed at the same time in the same code base. Delays to the secondary project will cause delays to the Student Progress go-live. High The student portal where the project will be deployed is a high-availability system and is expected to be accessible for students 24/7. There is a risk that the large number of changes occurring during go-live could take the system offline, temporarily impacting system availability. Low There is a risk that an interpersonal conflict will arise within the team, impacting the human resources assigned to the project and potentially impacting the allotted schedule. Low Role Role Description Name Jane Smith John Doe Arthur Bowman Shila Cole Ana Fischer John Jones Document History Document Revision/Release Status Revision Date Description of Changes 0.1 6/29/15 Initial format 8/31/15 Initial draft Author / Editor Jane Smith John Doe 1.0 Executive Summary Students leverage a web portal to access university-related information and resources. Content within it can be targeted to all users or to those within a pre-specified role (e.g., students at a particular campus) or it can be user-specific. As an academic institution, one piece of information critical to students is their current progress in their degree program or programs. The purpose of the student degree progress project is to create an area to display user-specific academic progress. Project Purpose/Justification University leadership requested this project to promote student awareness and provide students easy access to their degree progress. Project Description Preliminary Scope Statement The purpose of this project is to create an area that displays user-specific academic progress within the appropriate roles, leveraging data through a back-end system. This project will include the necessary modifications to the back end to relay this information. More specifically, this project will include the following: Creating the graphical elements in a web-friendly format Creating the necessary web view to accommodate the graphical elements Creating the necessary changes to the back end to prepare data supporting the student information Creating the necessary web service to securely expose the student's information to the graphical elements and web view Out of Scope Due to business-specific processes, some students, particularly those who have been pursuing a degree for over four years, may not be able to see their academic progress using the deliverables of this project. Changes to the back end to expand this functionality are out of scope, as are any changes intended to enhance functionality to provide additional data beyond the academic progress already captured in another system. Project Objectives and Success Criteria The project will provide the functionality described within the preliminary scope statement. The project will be delivered without incurring any additional expenses. The project will be delivered free from any significant defects or without causing any down time. The project will be delivered no later than two weeks from the target time frame defined within the milestone schedule below. Constraints Additional funding is not available. The information available to students is derived from data within the back end and is as accurate, timely, and available as the source data and its structuring. Assumptions No major changes in formatting or scope will be presented during the life of the project. . 4 . Project Deliverables Project Charter Project Management Plan Design o User Interface Mockup o Architectural Design Test Plan Test Scenarios Project Resource Estimate The student degree progress project is estimated to use the following resources: Project Resource Estimate Resource Project Manager Systems Analyst Middleware Applications Developer Backend Systems Analyst Estimated Work Hours 48 Hours 12 Hours 44 Hours 50 Hours 154 Hours Total: Summary Milestone Schedule Summary Milestone Schedule - List key project milestones relative to project start Project Milestone Target Date Project Start September 1 Graphical Component Unit Complete September 23 Web View Unit Complete September 25 Backend Unit Complete October 7 Integration Testing Complete October 14 Submit to Leadership October 26 Leadership Acceptance November 2 Transition to Production November 5 Project Closeout November 13 Summary Budget Fiscal Year Summary Budget - List component project costs Project Component Hardware Software and Licensing Vendor Total Component Cost $0 $0 N/A $0 Project Approval Requirements The project will be completed once all requirements are met and all deliverables have been received and approved by the client. Role Project Sponsor Project Manager Core Stakeholder Vendor Resources Project Team Members Project Organization Name(s) - Department(s) Jane Smith John Doe Arthur Bowman None Shila Cole, Ana Fischer, John Jones Authorization Approval of this project charter provides authorization to move forward in accordance with the information contained in this document. Project Team John Doe, Project Manager Shila Cole, Systems Analyst Ana Fischer, Middleware Application Developer John Jones, Backend Systems Analyst Date: Date: Date: Date: Directors of Assigned Resources Michael Erdmann, Middleware Director Amber McLedon, Applications Director Cynthia Carmom, PMO Director/Acting Student Systems Director Date: Date: Date: Project Sponsor Jane Smith, Project Sponsor Date