The Project Charter

Course Project Part 1 (Due Week 4)

The Course Project Part 1 assignment is the integration of all the sections including the Introduction and Sections A through E. Part 1 should be completely integrated and presented in a logical order, written professionally and free of spelling and grammar errors, and updated with any changes that occurred along the way, including corrections and advice provided by your professor.

Introduction

• What is the project about and what are the project goals and objectives?
• Who will manage and how is the project going to be managed?
• Describe the impact of internal and external factors that may promote or hinder individual decisions and the management of people, procedures, processes, and projects.

Section A: The Project Charter

For this section, you will watch the Getta Byte Software video located in the Week 1 Lesson. Populate all sections of this Project Charter Template with content related to the Getta Byte Project Charter and improve its content. There are sections in the template which are not covered in the video for which the student is still responsible to complete by elaborating and adding its missing content. Here is a list of the Project Charter Template sections.

• Mission or purpose
• Project and product description
• ObjectivesMilestones
• Budget
• User acceptance criteria
• High-Level assumptions
• High-Level constraints
• Exclusions and boundaries
• Major risks
• Key stakeholders

Section B: Stakeholder Management

For this section, you will watch the Getta Byte Software video located in the Week 2 Lesson and use the information in the video to complete the Stakeholder Engagement Plan Template for the Getta Byte project.

• Identify each stakeholder and include influence, interest, and support.
• Define the approach to each stakeholder or stakeholder group, communication method, and frequency.

Section C: Communications Management Plan

In this section, you will create a simple communications management plan for the execution of the Getta Byte project. Complete the Communications Management Plan Template using the information in the Week 2 Getta Byte Software video.

• Communication vehicle
• Target audience
• Description or purpose
• Frequency
• Sender
• Distribution vehicle
• Internal or external

Section D: The Project Scope Statement

Populate all sections of this Scope Statement Template with content related to the Getta Byte project scope and improve its content. Watch the Getta Byte Project Scope video in the Week 3 Lesson and complete the missing sections by adding content. Here is a list of the Scope Statement Template sections.

• Project description
• Project requirements
• Project deliverables
• Project does not include (exclusions)
• Acceptance criteria
• Estimated project schedule
• Resource requirements
• Estimated cost of project
• Project constraints
• Project assumptions

Section E: The Work Breakdown Structure (WBS) and Project Schedule

Instructions

1. Create the work breakdown structure (WBS) hierarchical chart for the Getta Byte project using the information learned in the Week 4 Getta Byte WBS and Schedule video. Remember that the WBS starts with the project name at the highest level. The lower levels have the work package required to complete those deliverables. Review the Canvas Week 4 Lesson, the Contemporary Project Managementtextbook, and the PMBOK^®Guide for some suggestions on how to create a WBS hierarchical chart.
2. Create the project schedule using Microsoft Project with the information provided in the Week 4 Getta Byte WBS and Schedule video. Complete the following steps.
   1. In the Task Name column enter the Project Name, Milestones, and Task Names. As you develop the task list, make sure to use verb-object task names (i.e., develop software).
   2. In the Duration column enter the duration only for the tasks. Be sure to use consistent unit such as hours or days for all tasks. The milestones and project duration will be automatically calculated by MS Project.
   3. In the Predecessor column enter the task dependencies that is the predecessor relationship. Do not enter dependencies nor assign resources for milestones or summary tasks.

As you develop the task list, make sure to use verb-object task names (i.e., develop software). In an MS Project schedule, enter tasks, create the predecessor relationships in the predecessor column, but do not link summary tasks or assign resources (i.e., milestones do not have dependencies).