What you need to do:

• 1. 500-to-750- summary describing the purpose and key attributes of a project charter and why it is critical for effective project management.
• 2. what a project charter is, including it's key attributes of a project charter
• 3. why it is critical for effective project management
  • Include 3 or 4 references throughout
• Use Google Scholar to find the sources:https://scholar.google.com.au/

Purpose:

Why is a project charter used?

• The charter helps all project stakeholders, often being publicly shown beyond the project team to aid with communication.

There are Four Major Purposes for a Charter

• .

2. Help the project team and sponsor develop a common understanding

3. Help the project team and sponsor commit to the spirit of the project

4. Quickly screen out obviously poor project

1. Authorize the project manager to proceed.

• The charter formally grants approval for the project, empowering the project manager and outlining the requirements of the business and customer that the new product, service, or outcome aims to fulfill. Often project managers do not have the authority to commit resources without a charter.

1. Help the project team and sponsor develop a common understanding.

• Define the project justification, scope boundaries, schedule, success criteria, risks, resource estimates, and stakeholders' involvement, allowing for a shared understanding among all stakeholders.
• critical for effective project management because it:
  1. Achieve enhanced teamwork, trust, communication, and commitment among the sponsor, project manager, and project team; reducing concerns about management acceptance and sponsor-initiated changes.

1. Help the project team and sponsor commit.

• Each person needs to personally and formally commit to doing their level best to achieve the agreed-upon project results, even when things do not go as planned.
• critical for effective project management because:
  1. This formal commitment often helps a person decide to keep working hard on a project when things are not going well.

1. Quickly screen out obviously poor projects

• A charter is much quicker to put together than a full, detailed project plan and schedule.
• critical for effective project management because:
  1. If the charter does determine that the project is likely to fail, much planning time (and therefore money) will be saved

What is a Project Charter and it's Key elements:

• A project charter:
  • Is the first and most important elements of a project
    • Particularly for project managers, team members, and project sponsors.
  • It is a relatively short document (usually about three pages), which serves as an informal contractbetween the project team and the sponsor.
    • Similar to a contract that is entered into freely by two or more parties.
    • One party cannot change it on their own volition.
    • Contains something of value for each party
    • Is a living document that can evolve in response to changing conditions and with agreement between all parties.
  • It signals the beginning of the formalisation and planning of a project.
  • Once signed, the charter represents the transition from the high-level conceptual project initiation stage into the more detailed project planning stage.

Key elements:

Title

• A meaningful project title is critical particularly if there are a number of projects concurrently being executed in an organisation.
• The title can be used to quickly identify any project in question.

Scope Overview.

• The high-level "what and why" of the project, often referred to as the "elevator pitch" as it describes the project very briefly.
• It often includes additional background and will defines the project boundaries.

The business Case.

• It is the project purpose or justification statement, answering the "why?"
• Aligns the project with the organization's strategies and goals, outlining the expected benefits to persuade decision makers and inspire team members and stakeholders to contribute to its successful completion.

Background

• It helps other stakeholders to understand the background more fully behind these statements and can be any length. It is more of an external view or what is happening, or why the project is being conducted.

Milestone schedule with acceptance criteria.

• The milestone schedule provides "a summary-level schedule that identifies the major schedule milestones or significant points or events in the project".
• list major milestones and deliverables, when they should be completed, who will assess the deliverables and an acceptance criterion to for key decision makers to judge from.

Risks, assumptions, and constraints (uncertainties).

• A risk is an uncertain event or condition that could affect the project objectives.
• Assumptions are "factors in the planning purposes, that are considered to be true, real, or certain without proof or demonstration."
• A constraint is anything that can restrict project implementation or activity.
• Together, these can be referred to project uncertainty.

Resource estimates.

• Includes an outline of the resources needed to attain the return on that investment of the project.

Stakeholder list.

• It identifies and prioritizing stakeholders, helping the team to managing strong relationships with them because making decisions that satisfy stakeholder objectives are key to project success.

Team operating principles.

• Created to improve the function of a team through increasing team effectiveness and ensuring that all parties are aware of expectations.
• They often outline the approach for conducting meetings, making decisions, accomplishing work, and treating others with respect.

Lessons learned.

• An outline of the knowledge gained during the execution of the, which help to improving performance in future projects.

Signatures and commitment.

• Lists those who are involved in the projects and at times, describes the extent to which they have decision-making power and/or their expected time commitment.