Project Management: Difference between revisions

From Wiki :-)
Jump to navigation Jump to search
No edit summary
No edit summary
Line 61: Line 61:


=== Manage Stakeholders ===
=== Manage Stakeholders ===
A stakeholder is  
A stakeholder is a '''person, group, or entity that may affect or be affected by a project'''.


First, you need to identify the stakeholders, then you need to assess/analyse their impact on the project.
First, you need to identify the stakeholders, then you need to assess/analyse their impact on the project.
Line 67: Line 67:
Classify stakeholders using the following tools depending on what is most import to the Project Manager:
Classify stakeholders using the following tools depending on what is most import to the Project Manager:
* Power/interest grid
* Power/interest grid
** Monitor Low Power/Low interest: give the what they need
** '''Monitor''' Low Power/Low interest: give the information they need
** t
** '''Keep informed''' Low Power/High interest: people interest and impact can change over time
** '''Keep satisfied''' High Power/Low interest (e.g. senior level manager): keep them updated to the appropriate level (maybe not everyday)
** '''Manage closely''' High Power/High interest: this person has the power to impact the project, he should kept updated
* Power/influence grid
* Power/influence grid
* Influence/impact grid
* Influence/impact grid
* Salience model: ability to impose their will on the project
* Salience model: ability to impose their will on the project
* Stakeholder cube
* Stakeholder cube
A stakeholder register helps record the stakeholder prioritization. It contains the name, role, type and how they want to be communicated with and how often.


== Resources ==
== Resources ==

Revision as of 05:36, 21 December 2018

Iron Triangle

Scope, Cost and Time defines the quality of the work.

Project Organization Type

  • Functional Organization: Staff members belong to its own functional unit under the clear supervision of a functional manager. Production, marketing, engineering, or accounting is an example of functional unit. Each functional unit works independently. Functional managers is responsible for project coordination.
  • Matrix Organization: Staff members still belong to its own functional unit but the project manager authority is greater. The strongest the matrix is, the greater the Project Manager power and influence.
    • Weak: Really close to a functional organization but the Project Manager has a little more power. The role of the Project Manager is more of a coordinator. The Project Manager handles the communication but he cannot enforce or make decisions.
    • Balanced:The Project Manager can enforce and make decisions but he does not have full authority on the project and the funding.
    • Strong: A full-time project Project Manager with considerable authority on the project.
  • Project-based Organization: Staff members do no belong to a functional unit but to a project under the supervision of a Project Manager who has full authority of the project. Staff members are fully dedicated to the project. The project coordination is on the project unit only and does not encompass multiple functional units.
  • Composite Organization: This organization is a mix between different organization types at different levels.
Organization Structure Functional Weak Matrix Balanced Matrix Strong Matrix Projectized
Project Manager's Authority Little Low Moderate High Total
Resource

Availability

Little Low Moderate High Total
Who manages the

project budget

Functional Manager Functional Manager Mixed Project Manager Project Manager
Project Manager's

Role

Part-time Part-time Full-time Full-time Full-time
Project Management

Administrative Staff

Part-time Part-time Part-time Full-time Full-time

Project Organization Chart

Manage Stakeholders

A stakeholder is a person, group, or entity that may affect or be affected by a project.

First, you need to identify the stakeholders, then you need to assess/analyse their impact on the project.

Classify stakeholders using the following tools depending on what is most import to the Project Manager:

  • Power/interest grid
    • Monitor Low Power/Low interest: give the information they need
    • Keep informed Low Power/High interest: people interest and impact can change over time
    • Keep satisfied High Power/Low interest (e.g. senior level manager): keep them updated to the appropriate level (maybe not everyday)
    • Manage closely High Power/High interest: this person has the power to impact the project, he should kept updated
  • Power/influence grid
  • Influence/impact grid
  • Salience model: ability to impose their will on the project
  • Stakeholder cube

A stakeholder register helps record the stakeholder prioritization. It contains the name, role, type and how they want to be communicated with and how often.

Resources

Iron Triangle https://en.wikipedia.org/wiki/Project_management_triangle
A Guide to the Project Management Body of Knowledge (PMBOK® Guide) http://suncoastpmi.org/images/downloads/BusinessAnalysis/pmbok_5th_edition.pdf