Reference no: EM131720527
Last weeks assignment is attached however I received a bad grade of that assignment from another tutor. I am merely attaching it as a reference because this weeks assignment I must update the project charter.
I have included a template of the project charter which is to be updated and the and the final scheduling report template which must also be complete this week along with a one page project scope.
Submit an updated version of your project charter based on the feedback provided by the instructor.
Using the Stakeholder Register Template, post your Stakeholder Register consistent with your updated Project Charter.
Post a one-page Project Scope Statement that:
· Describes the product or service
· Specifies the acceptance criteria
· Defines the project deliverables
· Explains the project exclusions, constraints and assumptions. Final Scheduling Report Overview
In Week 8, you will submit your Final Scheduling Report.
This report is an explanation for and justification of the processes and procedures you used to establish your recommended scope and schedule baselines, and your recommended processes for change management and schedule control.
Each week of the course you will be drafting and submitting the individual components of this report. You will be provided with templates to guide your preparation of most of these components.
As each week's assignment is graded, your instructor will return your work with suggestions to incorporate into your Final Scheduling Report submission. Please remember that you must use APA writing style and it is expected that your writing will be at a scholarly level. At a minimum, this means providing in-text citations and a reference list to support for your analysis.
Audience
The audience for this report is your project sponsor and the senior management team.
Report Format and Organization
The report should be prepared using word processing software, Microsoft Office products if possible. Gantt charts and network/PERT diagrams should be formatted using a PDF application to ensure that the format is maintained. The appendix documents should be submitted as separate documents.
The body of the report should include an analysis and rationale for the processes and procedures you used to create the project schedule. This analysis should be a minimum of 4 pages and be presented in a manner that assumes your audience is not familiar with the procedures you are describing.
Your analysis should reference the documents you prepared for each of your weekly assignments. These documents should be included in an appendix to the report. Please refer to the individual templates included in your weekly resources for detailed instructions for each of these components.
Project Description
The project description is a summary of the project and the deliverables or outcomes expected as a result of conducting the project.
The project description typically includes a statement of the purpose of the project and the justification for undertaking the project from a business perspective. It also includes project objectives, high-level requirements, and how project success will be measured.
Write a project description based on project you have selected to work on throughout this course
• State the purpose and justification for the project.
• Describe the objectives of the project.
• Describe the high-level requirements for the project.
• Describe the tangible measures of project success.
(3-4 paragraphs)
Project Assumptions and Constraints
Project assumptions are factors that may be true but are not confirmed and can impact the project. Constraints are factors that impose limits or boundaries on the project.
Summarize the assumptions and constraints for your project
• Describe the assumptions for the project.
• Describe the constraints for the project.
(2-3 paragraphs)
Project Milestone Timeline Chart
Project milestones represent significant points or events in the project lifecycle. In the project schedule Gantt chart, milestones are represented with durations of 0 and a symbol such as a diamond. For many projects, a milestone timeline chart is developed as a visual that is typically used to communicate to executive stakeholders who most likely won't want to see the detailed schedule.:
• Prepare a milestone timeline chart showing the start and finish dates of the project as well as the name and finish date for each milestone in your project
• Describe each of the project milestones in the milestone timeline chart.
Project Approval Procedure
The project approval procedure is a formalized process for obtaining stakeholder approval and sign-off before the project team can proceed to the next step in the project. Stakeholder approval is typically required at milestones in the project when major project deliverables are completed.
Using the milestone timeline chart created above, describe the approval process for the project. To complete this part of the project:
• Indicate who (person or type of position) will approve each of the milestones in the timeline chart, and describe how the approvals will be obtained.
Attachment:- CheckList.rar