Two Major documents of Project Management - Project Charter and Project Scoped Project Scope
Why a project should not start without a Project Charter?
One of the most critical and important documents for every project is the Project Charter. It is the first document for a project and lays down the foundation for the project. A project charter is a document which explains about the project at a very high level and highlights the stakeholders and the approach towards the project. It introduces the Project Manager to the project. A project charter is owned by the project sponsor. Project Sponsor authorizes the Project Charter but it can be created by the Project Manager. Every Project Charter should be approved by the Project Stakeholders. Once the Project Charter is approved, it cannot be changed through out the project life cycle.
What does a Project Charter have?
There is no standard rule what information a project charter should contain. In fact the format of a project charter also can vary from organizations to organizations. We have listed information which a project charter can have.
Project Name – Name of the Project which differentiates it from other projects.
Project Description – A brief description of the project
Project Scope – High level scope of the project
Project Stakeholders – Who are the stakeholders of this project?
Business Case – Why is this project important?
Value proposition of the project Project Objectives – What is the objective of the project?
Project Time line – Start Date and End Date
Project Deliverable – Outcome/Deliverable from the project
Project Constraints – Various constraints faced by the project
Assumptions – What are the assumptions made for the project during the initiation phase
A project charter provides a solid foundation to a project (small or large). All the stakeholders of the project are informed about their roles and the level of efforts required from their end. Project Charter is used during the initial phase and planning phase hence a good project charter can help in the success of the project. It is very important for a project manager to have a project charter before he/she take over a new project. If a project charter is unavailable, it is better to create a project charter and get it approved from the stakeholders before one starts the project.
Project Scope – Why is it really important for a project?
Majority of the project fails because the scope of the project is not defined clearly. For any project to be successful, the project scope has to be clear to all stakeholders without any assumption.
What is Project Scope?
Project Scope as the name suggests is the boundary of the project. Every project team is required to only deliver as defined and agreed in the Project Scope. The information on project scope is documented in a project scope document. It is the foundation on which the schedule, budget are built. As per the PMBOK – Project Scope is all the work required and only the work required to complete the project.
It is extremely important for every project manager to document the scope of the project and get approval from all stakeholders. Project scope can change over a period of time based on the client's requirement change, business scenario change or any other applicable reason. However any change in project scope should be supported by a Change request. The requester of the change should raise a change request and it has to receive approval from the change control board. Any change to the scope of the project will have impact on Time, Cost, Quality, Risk, Staffing (Human Resource), Communication.
Project Scope - Impact
Impact of change in project scope to Time, Cost, Quality, Risk, Staffing (Human Resource), Communication is difficult to ascertain and takes a lot of time for any project manager to identify the impact. If the scope change impact is not ascertained correctly, this will impact the project success adversely.
Define Project Scope
Defining Project Scope is the first step wherein the scope of the project is defined. Scope can be defined in three main ways
– Deliverable, Functionality & Data and Technical Structure.
Deliverable – It includes internal (internal project deliverable) as well as external deliverable (Deliverable for the client)
Functionality – Functional specification of the project. Mention the list of functionality
Technical Structure – The structure diagram can identify the whole system at a high level.
It can be created in a pictorial format or diagram
Defining a scope is a major problem in many projects. An error in a project scope can lead to the project disaster. Unless and until the scope is identified correctly, the project cannot be under control and scope will keep increasing.
Find our PMP® Certification Online Classroom training classes in top cities:
|PMP® Certification||26 Jan -23 Feb 2019, Weekend batch||Your City||View Details|
|PMP® Certification||25 Jan -22 Feb 2019, Weekdays batch||New York City||View Details|
|PMP® Certification||1 Feb -1 Mar 2019, Weekdays batch||Boston||View Details|
Recommended articles for you
Why do we need a project charter?Article
Scope Statement in a Project: What To Do And What Not To?Article
Project Scope Management – Process Groups: PMP Certificati...Article