Project Charter - Input to Management Plans

Submitted by chullan88 on Sun, 04/20/2014 - 05:40

Hi all,

 

I have only recently started my PMP preparations and with lack of PMI oriented project management experience,is having a tough time understanding the concepts.I've been trying to understand the main inputs and outputs for each processes and from where each of them are derived.

For eg: Project Charter gets created in the first process.It serves as input to the next process,Identify Stakeholders.

Also it is an input to requirements collection,define scope and all management plans except quality,HR,communications and procurement.

Can anyone give the reason for this??

Forums: 
General Discussion
  • Log in to post comments
  • 473 reads

vishwadeep

Sun, 04/20/2014 - 09:44

Hi Mate,

Thats a nice question, below is how i would answer this:

The answer lies in the contents of the Project Charter, it is a very high level document with the below contents:

• Project purpose or justification,
• Measurable project objectives and related success criteria,
• High-level requirements,
• Assumptions and constraints,
• High-level project description and boundaries,
• High-level risks,
• Summary milestone schedule,
• Summary budget,
• Stakeholder list,
• Project approval requirements (i.e., what constitutes project success, who decides the project is
successful, and who signs off on the project),
• Assigned project manager, responsibility, and authority level, and
• Name and authority of the sponsor or other person(s) authorizing the project charter.
 
Now to your question:
 
Quality : Quality requirements are different for different projects and are determined by the project manager by always keeping the COQ in mind. The charter cannot add any value in the planing of this process.
 
HR :  HR plan is more concerned with the R&R, Org Chart, Staffing  etc for which again the charter canot be of help.
 
Communications : Since the Stakeholder Register is already been created, and seperately maintained, hence in place of referring the stakeholder list in the charter, referring the Stakeholder Register is the obvious option in an ideal case scenario, hence again the charter is not required.
 
Procurement: Procurement Requirements as you know are decided in the planing phase, and the Charter does not has that level of info, as its a high level document created in initiating phase, so again the need of charter gets eliminated.
 
Hope my answer is useful in your preperation.
 
Best of luck
 

chullan88

Sun, 04/20/2014 - 13:40

Hi vishwadeep

Thanks for the clarification.It really sums it up.

 

Regards

Binas

vishwadeep

Sun, 04/20/2014 - 21:26

Thax for your comments mate, hope you crack the exam asap

philstinnet

Mon, 04/21/2014 - 16:42

When one starts reading for PMP exam, the initial impression is that the 'Processes' and 'Knowledge Area (KA)' are like 'one-way' roads. But, they are not like so. The KA and Processes and Project Documents and Project Plans are interacting with each other all the time from Initiation of the project to the close of the projects. Therefore, there are many many interactions going on at any point of time. It is extremely hard for PMBOK or any other book to list all these interactions as an input or output.

Therefore, PMBOK lists the one which seems to be more important in the eyes of PMI.

And this is why they say - PMBOK is just a guide.

Now, coming back to your question. You are asking that why the project charter is not an input for HR Mgmt plan.

And, my answer is that it is an Input for HR mgmt plan.

How ? How can it be an input for HR mgmt plan ?  

And, here is your answer - 

Along with many things, the Project Charter also shows the presence or absence of 'Resources pre-assigned'. Check the examples of Project Charter given on Page 111 and Page 114 in Rita's book. Now, go to the 'Acquire the Team' process in the HR knowledge area. Check one of the tool there - 'Pre-assigned'. And, if someone is pre-assigned to your project, you are going to take that into consideration while building your HR mgmt plan.

You can see that Project Charter just interacted with the HR knowledge area. And yet, Project Charter is not an input for the 'Acquire the Team' process or the 'HR Mgmt Plan' process !!!

I hope i am able to convey my message.

Being said that, when you take your exam, use this philosophy - "Common sense is important to solve the problems but PMBOK is the bible."

Thanks

 

 

 

 

 

  

chullan88

Sat, 04/26/2014 - 09:21

Thanks philstinnet