Video Description

This lesson focuses on developing a project charter. The project charter gives justification to the project and includes the following:

  • Justification and purpose
  • Success Criteria
  • High Level Scope
  • Constraints and Assumptions
  • Goals for time and cost
  • Project Manager's authority level
  • Stakeholders
  • Project approval requirements

In the project charter, the inputs are the Project Statement of Work, Business Case and Agreements and the tool used is expert judgement. All of this is important to know when taking the exam to obtain the PMP certification. [toggle_content title="Transcript"] Now we are going to get into the processes. For each one of these knowledge areas we are going to cover web processes for all of the knowledge area. As you are studying integration, notice that you start off with project. Develop project charter then we are going to move in to planning which is develop a project management plan, executing is direct the project management project work. Remember in the beginning there is two for monitoring and controlling on that table. This one is monitor and control project work and perform integrated change control. The last process under integration in the very last process in the project is close project phase. The very first process is developing a project charter and the very last process is close project phase. To start off - developing the project charter. To develop the project charter the process creates the project charter...it makes sense. For each one of these processes you are going to have inputs, outputs, and tools. These are must know for the exam. So under the process of develop project charter, you have to produce the project charter, some of them are not that straightforward. The inputs are the project statement or work, the business case and the agreements. Another way of saying inputs; are pieces of information that you need to have to follow that process to come up with an output. The tool used is expert judgement in this case and the tool is - what are the tools in your hands that you can use to do whatever process it is. In this case having expert judgement is knowing how to take this information and develop a project charter. Some of the other processes will have many tools, some of them could be like ten or 12 different tools that you can use. But for the project management professional certification, a must know for each one of these 47 processes are the inputs, the outputs and the tools and then having an understanding of what those inputs, outputs and tools are. The information you need to have is the project statement at work. Project statement at work is going to tell you what you need to do for that project. It is going to be the client's request of what needs to be done. A business case is why are we taking on this project? You don't take on a project just for no reason. There has to be a reason for it. Whether it is economical, it could be a government regulation. For government regulation comes down...that is always the first reason to take a project. The government states that these doors in the building need to be 36 inches wide for regulation rules, you have to take on that project to widen the doors. The last thing are agreements. These are either verbal or they can be formal but they are agreements between the client and the buyer and seller, the client and you as the project manager. These are things that are in place that need to be done with the project. The project charter in general I am going to give you the outputs and what it does. The project charter gives justification to the project. Without the project, charter there is no project according to PMI. With the project charter, the project manager can create the project charter but he can't have the final sign on it. It has to be from upper management or it could be from the sponsor. But the project charter will sign who the project manager is, justification and purpose of the project, success criteria, high-level scope, constraints and assumptions, goals for time and cost. Example on the project charter is this project must be done in three months, or it must to be done before this date, it can't cost more than million dollars. The project manager's authority level, if you think back to the previous slides where we talked about the organization, in a functional organization, the project manager would be called the project coordinator. Doesn't have that much power, he can't get too much done but it's going to tell what the project manager is allowed to do and what he is not allowed to do. The charter will also identify who the key stakeholders are. And it will go over the project approval requirements. One thing for this project charter, you are going to notice it's an impact to a lot of processes within the planning phase. My recommendation for the exam is just to understand that the project charter gives justification for the project. It identifies who the project manager is. The project manager cannot sign off on the project charter. [/toggle_content]

Course Modules

Project Management Professional (PMP) - PMI

Instructor Background