Hello, please help with week 2 assignment providing all refrences.

Project Charter (Individual project)

Overview

The purpose of this Indivdual assignment is to develop a project charter based on the Case Study. The charter is the initial document that ensures everyone has a common understanding of the project and authorizes the project to proceed. Details of the project will be developed later.

Details of the Project Charter assignment

Read "Mamma's Bakery and Sandwich Shoppe Case Study" (Course Resources).

Determine the initial project management roles of each team member (assume a team size of 6-8) on the IT project team for planning, designing, and installing the IT system.

Some team roles might include:

Project Manager

Functional or technical managers, such as telecommunications, application software designer,

database developer, Web page designer, etc.

Budget/Finance

Project Management Support such as procurement or human resources

Use the textbook and other academically credible sources, as a minimum, to define an IT System and then to determine the proposed scope for this project. For example, including a scheduling software package may be within the scope. Providing a learning application for new employees might be not be within the scope of this IT project.

Use the Case Study to be clear on the basic requirements for this project. What will the IT project team provide if the proposed plan is accepted? You may email the client/stakeholder (your instructor) to further define requirements, if you do not have enough information.

As in many real-world projects, the requirements are the weakest part of the project. The lack of detail is deliberate to encourage identify what might be missing and then work with the client/customer to fill in the blanks. Does it seem as though perhaps there is not enough information to complete the project and the charter? If so, please ask the customer (your instructor).

Now prepare a Project Charter for your project. This document becomes the basic agreement to describe the project with enough detail that the approximate scope and magnitude is clear and understandable by both the team and the client/customer or executive sponsor.

Project Charter Contents

Executive Summary

Begin the document with an Executive Summary, which contains:

A summary of the document's purpose.

A problem statement (need for the project).

Project objectives and how they align with the business strategy.

The project management approach.

Technical solution (a high-level description of the IT system, which might include a graphic).

This is a Summary, so it should be a paragraph or two, not to exceed one page.

Project Scope

The scope statement expands on the Executive Summary with a clear and concise statement of what the outcome of the project will be. Although it is the anticipated scope at this time, the intent is to set the project boundaries as you know them at this time. State (at a high level) what the project will deliver.

Project Charter (Individual project)

You should be able to draw this from the Case Study. Do not over promise here. State what is in scope (to be delivered) as well as what is not in scope (not to be delivered).

Project Estimates

At a high level, show the estimated project schedule. The easiest to understand is a list (perhaps in table format) of projected major milestones/deliverables for the project and their forecasted completion dates. This information is preliminary only, or a Rough Order of Magnitude (ROM). Once the project has been approved to move forward, a comprehensive project plan will be developed

In addition, show the current estimated project costs, as a ROM. Identify the source of the needed funding, i.e., Software, Hardware, Networking, Internal Resources, Contractor Resources. Include a Total ROM Budget Estimate.

Primary Stakeholder(s)

List the individual(s) who will use the final product, influence decisions about the project, and (most importantly) pay for the project.

Project Team

Identify team roles and responsibilities on the project (you can use actual names based on who is in your group).

Project Constraints and Assumptions

Constraints are any events or circumstances that may restrict or limit a project (and the team's options). Examples of constraints are things such as due dates, fixed budget, skill levels, or resource availability.

Assumptions are the driving force that determines project success and they are typically outside the total control of the project team. Stakeholders must agree on these assumptions to produce a shared understanding of project success.

Preliminary Risk Statement

List any risks that can be identified from, for example, the project constraints and assumptions. Included briefly stated (short sentence) risk mitigation strategies.

Preliminary Communication Plan

Lay out the proposed methods of gathering and communicating project progress to the sponsor. This could include team standups, task progress updates, project status reports, project reviews, project post-mortem. Also identify the communication frequency, i.e., daily, weekly, at milestones, at end of project.

Change Threshold

This identifies the magnitude of changes requested by the customer that would exceed the bounds of the original charter with relation to cost, resources or schedule. Once the threshold is met or exceeded, a new Project Charter would be required with signature from the customer.

Definition of Project Complete

This is a high-level statement of the criteria that define when the project has been completed. This is date and funding agnostic. In other words, "End date reached" or "Funding is exhausted" do not define Project Complete. This statement should present the completed deliverables that evidence a completed project.

Signatures

This includes signature blocks of the parties that are agreeing to the charter.

Project Charter (Individual project)

Formatting Your Assignment

Consider your audience - you are writing in the role of a project manager and your audience is Mamma Mia. Do not discuss Mamma's Bakery as if the reader has no knowledge of the organization. Do not use the term "case study" - this is terminology used in a classroom and would not be in a business report. Use third person consistently throughout the report. In third person, the writer avoids the pronouns I, us, you, your, we, my, and ours. The third person is used to make the writing more objective by taking the individual, the "self," out of the writing. This method is very helpful for effective business writing, a form in which facts, not opinion, drive the tone of the text. Writing in the third person allows the writer to come across as unbiased and thus more informed.

The format could be modified to improve readability. You could use tables in certain spots, i.e., Project Estimates. Tables are single-spaced, so that would make the document neater looking.

Create an APA format title page that includes: The title of report (Project Charter), your name, Course and Section number and date (use assignment due date); do not include graphics or themes.

No running header required for this document.

The body of the paper should be double spaced, and no longer than 7 pages.

Tables should be single-spaced, and use no shading.

Use 1" margins on all sides.

Font should be 11-point Calibri, 11-point Arial, 10-point Lucida Sans Unicode, 12-point Times

New Roman, 11-point Georgia, or 10-point Computer Modern.

Font should remain consistent throughout the paper, i.e., not changing from one font to

another.

Use at least one external reference and one from the course content (from the class reading

content, not the assignment instructions or case study itself) with APA formatted citation and reference. For information on general APA format and specifics related to citing from the class content, refer to ContentCourse ResourcesWriting Resources. Resources must not use Wikipedia, general information sites, blogs, or discussion groups.

The list of References must be its own page at the end of the document and it must be in APA format, i.e., double spaced, .5" hanging indent. No more than 10% of the paper may be in the form of a direct citation from an external source. All in-text citations must appear in the References list and all entries in the References list must be used as in-text citations.

Run Microsoft Word's grammar/spell checker; there should be no errors in grammar, verb tenses, pronouns, spelling, punctuation, first person usage, or contractions.

If headings are used, do not leave blank lines after the previous section, and do not use sub- headers.

Submit your paper as a Word document, or a document that can be read in Word.