Project charter

Last updated

In project management, a project charter, project definition, or project statement is a statement of the scope, objectives, and participants in a project. It provides a preliminary delineation of roles and responsibilities, outlines the project's key goals, identifies the main stakeholders, and defines the authority of the project manager. [1] More broadly, this document may be referred to as a "Team Charter" for the purpose of formalizing team roles and task structure at the outset of any team-oriented initiative. Teams that approach a task with a mindful design of team dynamics and task structure are more likely to be successful. [2]

Contents

The name of this document varies by institution. The Initiative for Policy Dialogue (IPD) refers to this document as the project charter. In customer relationship management (CRM), it is known as the project definition report. Both IPD and CRM require this document as part of the project management process.

Purpose

The project charter is usually a short document that explains a project clearly and concisely, and refers to more detailed documents for additional information. [3] A project charter should:

A project charter typically documents most of the following: [5] [6]

Establishing authority

The project charter establishes the authority assigned to the project manager, especially in a matrix management environment. [7] It is considered industry best practice.

Uses

The three main uses of the project charter are:

Development

A project charter will be created in the initiating process group of a phase or a project at the very start. Developing the charter and identifying the stakeholders are the two main actions of the initiating process group. Typically a project manager takes the lead in developing the charter. The project manager will employ his or her expertise and experience to develop the charter. The project manager will work with the key stakeholders (customers and business sponsors), the PMO, Subject Matter Experts inside and outside the organization, other units within the organization and may also work with Industry groups or professional bodies to develop the charter. The project manager will employ facilitation techniques such as brainstorming, problem solving, conflict resolution, meetings, expectations management etc. to develop the charter.

Inputs to develop a charter can be:

The charter once signed will provide authority to the project manager to officially execute the project and employ organizational funds and resources to make the project successful.

For a large multi-phased project, the charter can be created for each individual phase. [7] For example, there can be an initial charter during the Scope and Seek phase of a project, followed by a Planning charter and an Execution Charter during the build phase of the project.

See also

Related Research Articles

Project management is the process of leading the work of a team to achieve all project goals within the given constraints. This information is usually described in project documentation, created at the beginning of the development process. The primary constraints are scope, time, and budget. The secondary challenge is to optimize the allocation of necessary inputs and apply them to meet pre-defined objectives.

A project plan, according to the Project Management Body of Knowledge (PMBOK), is: "...a formal, approved document used to guide both project execution and project control. The primary uses of the project plan are to document planning assumptions and decisions, facilitate communication among project stakeholders, and document approved scope, cost, and schedule baselines. A project plan may be sumarized or detailed."

<span class="mw-page-title-main">Project Management Body of Knowledge</span> Body of knowledge for project management

The Project Management Body of Knowledge (PMBOK) is a set of standard terminology and guidelines for project management. The body of knowledge evolves over time and is presented in A Guide to the Project Management Body of Knowledge, a book whose seventh edition was released in 2021. This document results from work overseen by the Project Management Institute (PMI), which offers the CAPM and PMP certifications.

The rational unified process (RUP) is an iterative software development process framework created by the Rational Software Corporation, a division of IBM since 2003. RUP is not a single concrete prescriptive process, but rather an adaptable process framework, intended to be tailored by the development organizations and software project teams that will select the elements of the process that are appropriate for their needs. RUP is a specific implementation of the Unified Process.

<span class="mw-page-title-main">Project manager</span> Professional in the field of project management

A project manager is a professional in the field of project management. Project managers have the responsibility of the planning, procurement and execution of a project, in any undertaking that has a defined scope, defined start and a defined finish; regardless of industry. Project managers are first point of contact for any issues or discrepancies arising from within the heads of various departments in an organization before the problem escalates to higher authorities, as project representative.

Communications management is the systematic planning, implementing, monitoring, and revision of all the channels of communication within an organization and between organizations. It also includes the organization and dissemination of new communication directives connected with an organization, network, or communications technology. Aspects of communications management include developing corporate communication strategies, designing internal and external communications directives, and managing the flow of information, including online communication. It is a process that helps an organization to be systematic as one within the bounds of communication.

<span class="mw-page-title-main">Requirements analysis</span> Engineering process

In systems engineering and software engineering, requirements analysis focuses on the tasks that determine the needs or conditions to meet the new or altered product or project, taking account of the possibly conflicting requirements of the various stakeholders, analyzing, documenting, validating, and managing software or system requirements.

<span class="mw-page-title-main">Systems development life cycle</span> Systems engineering terms

In systems engineering, information systems and software engineering, the systems development life cycle (SDLC), also referred to as the application development life cycle, is a process for planning, creating, testing, and deploying an information system. The SDLC concept applies to a range of hardware and software configurations, as a system can be composed of hardware only, software only, or a combination of both. There are usually six stages in this cycle: requirement analysis, design, development and testing, implementation, documentation, and evaluation.

Requirements management is the process of documenting, analyzing, tracing, prioritizing and agreeing on requirements and then controlling change and communicating to relevant stakeholders. It is a continuous process throughout a project. A requirement is a capability to which a project outcome should conform.

In project management, scope statements can take many forms depending on the type of project being implemented and the nature of the organization. The scope statement details the project deliverables and describes the major objectives. The objectives should include measurable success criteria for the project.

The project documentation (PID) is one of the most significant artifacts in project management, which provides the foundation for the business project.

Software project management is the process of planning and leading software projects. It is a sub-discipline of project management in which software projects are planned, implemented, monitored and controlled.

<span class="mw-page-title-main">Internal audit</span> Independent, objective assurance and consulting activity

Internal auditing is an independent, objective assurance and consulting activity designed to add value and improve an organization's operations. It helps an organization accomplish its objectives by bringing a systematic, disciplined approach to evaluate and improve the effectiveness of risk management, control and governance processes. Internal auditing might achieve this goal by providing insight and recommendations based on analyses and assessments of data and business processes. With commitment to integrity and accountability, internal auditing provides value to governing bodies and senior management as an objective source of independent advice. Professionals called internal auditors are employed by organizations to perform the internal auditing activity.

Project governance is the management framework within which project decisions are made. Project governance is a critical element of any project, since the accountabilities and responsibilities associated with an organization's business as usual activities are laid down in their organizational governance arrangements; seldom does an equivalent framework exist to govern the development of its capital investments (projects). For instance, the organization chart provides a good indication of who in the organization is responsible for any particular operational activity the organization conducts. But unless an organization has specifically developed a project governance policy, no such chart is likely to exist for project development activity.

Terms of reference (TOR) define the purpose and structures of a project, committee, meeting, negotiation, or any similar collection of people who have agreed to work together to accomplish a shared goal.

ISO 26000:2010 Guidance on social responsibility is an international standard providing guidelines for social responsibility. It was released by the International Organization for Standardization (ISO) on 1 November 2010 and its goal is to contribute to global sustainable development by encouraging business and other organizations to practice social responsibility to improve their impacts on their workers, their natural environments and their communities.

In business performance management, a third-generation balanced scorecard is a version of the traditional balanced scorecard, a structured report, supported by design methods and automated tools, that can be used by managers to keep track of the execution of activities by the staff within their control, and to monitor the consequences arising from these actions.

A glossary of terms relating to project management and consulting.

<span class="mw-page-title-main">Working group</span> Group of experts working together

A working group is a group of experts working together to achieve specified goals. Such groups are domain-specific and focus on discussion or activity around a specific subject area. The term can sometimes refer to an interdisciplinary collaboration of researchers, often from more than one organization, working on new activities that would be difficult to sustain under traditional funding mechanisms. Working groups are variously also called task groups, workgroups, technical advisory groups, working parties, or task forces.

The following outline is provided as an overview of and topical guide to project management:

References

  1. "The Concord Middle School Building Committee Report". The Concord Journal. Retrieved 24 December 2019.
  2. Mathieu, J. E., & Rapp, T. L. (2009). "Laying the foundation for successful team performance trajectories: The roles of team charters and performance strategies." Journal of Applied Psychology, 94(1), 90-103. https://doi.org/10.1037/a0013257.
  3. Project-Management.com (2021-05-04). "What is a Project Charter?". Project-Management.com. Retrieved 2022-03-19.
  4. Martins, Julia (5 April 2021). "3 Elements Every Project Charter Needs". Asana. Retrieved 2022-03-19.
  5. "Project Charter". Adobe Workfront. Retrieved 2022-03-19.
  6. "What Is a Project Charter in Project Management?". Wrike. Retrieved 2022-03-19.
  7. 1 2 Brown, Alex S. (2005). "The Charter: Selling Your Project". PMI Global Congress 2005. Project Management Institute.