Project Management - Revision history

Savoundg at 11:00, 21 December 2018

2018-12-21T11:00:09Z

← Older revision		Revision as of 11:00, 21 December 2018
Line 1:		Line 1:
			A '''Project''' is a temporary endeavour which uses a series of tasks that have defined start and end dates, consume resources, have funding limits, and create a lasting outcome.

	=== Iron Triangle ===		=== Iron Triangle ===
	Scope, Cost and Time/Schedule defines the quality of the work.		Scope, Cost and Time/Schedule defines the quality of the work.

Savoundg at 10:22, 21 December 2018

2018-12-21T10:22:37Z

@@ Line 137: / Line 137: @@
 * Execution Approach: How the Project should be executed?
 * Change Management Plan
 == Resources ==

Savoundg at 09:57, 21 December 2018

2018-12-21T09:57:09Z

← Older revision		Revision as of 09:57, 21 December 2018
Line 1:		Line 1:
	=== Iron Triangle ===		=== Iron Triangle ===
	Scope, Cost and Time defines the quality of the work.		Scope, Cost and Time/Schedule defines the quality of the work.

	=== Project Organization Type ===		=== Project Organization Type ===
Line 103:		Line 103:
	Also called Project Frame, Scoping Document. Often, it is part of a contract.		Also called Project Frame, Scoping Document. Often, it is part of a contract.

	~~Inputs~~:		This is a one to two pages documents. It formally authorizes the Project. It contains the Project name, description, purpose, scope, requirements, deliverable, schedule, financial resources, assumptions/constrains, known risks, references and the '''Key Stakeholders''' section.

			The '''Key Stakeholders section''' should at least include: Owner/Client, Project Sponsor, Project Manager. In addition to that, it should include the '''level of authority''' of the Project Manager, the '''Project Approval Requirements''' and the '''Project Exit Criteria'''.

			The input to the Project Charter are:
	* '''Benefits Managements Plan'''		* '''Benefits Managements Plan'''
	** Target benefits, Strategy, time frame, ...		** Target benefits, Strategy, time frame, ...
Line 127:		Line 131:
	*** NPV(1, N)=R(0) + R(1)/2 + R(2)/4 + ... + R(N)/2^N		*** NPV(1, N)=R(0) + R(1)/2 + R(2)/4 + ... + R(N)/2^N
	* Internal Rate of Return (IRR)=discount rate '''i''' where the NPV is '''0'''		* Internal Rate of Return (IRR)=discount rate '''i''' where the NPV is '''0'''

			==== Project Management Plan ====
			This document describes how the Project will be planned, executed, monitored, controlled. Each function unit owns a section in the Project Management Plan. For instance, this document may contain the Cost Management Plan or the Quality Management Plan. It can also include the:
			* Executive Summary
			* Execution Approach: How the Project should be executed?
			* Change Management Plan

	== Resources ==		== Resources ==

Savoundg at 08:45, 21 December 2018

2018-12-21T08:45:04Z

@@ Line 89: / Line 89: @@
 * Interpersonal skills: building trust, resolving conflict, active listening,  change management, cultural & political awareness, observation
 * Management skills: influence people, facilitate cooperation, negotiation, influence or modify organizational behaviour
 == Resources ==
@@ Line 94: / Line 132: @@
+!
+!
 |-
 |Iron Triangle

Savoundg at 06:35, 21 December 2018

2018-12-21T06:35:13Z

← Older revision		Revision as of 06:35, 21 December 2018
Line 78:		Line 78:

	A '''stakeholder engagement plan''' contains:		A '''stakeholder engagement plan''' contains:
	* their desired and current level of engagement		* their desired and current level of engagement: Unaware, Resistant, Neutral, and Leading
	* their scope and impact of change		* their scope and impact of change
	* interrelationship		* interrelationship

Savoundg at 06:30, 21 December 2018

2018-12-21T06:30:52Z

@@ Line 75: / Line 75: @@
 * 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.
+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 ==

Savoundg at 05:36, 21 December 2018

2018-12-21T05:36:54Z

← Older revision		Revision as of 05:36, 21 December 2018
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 ==

Savoundg at 05:30, 21 December 2018

2018-12-21T05:30:51Z

← Older revision		Revision as of 05:30, 21 December 2018
Line 59:		Line 59:

	==== Project Organization Chart ====		==== Project Organization Chart ====

			=== Manage Stakeholders ===
			A stakeholder is

			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 what they need
			** t
			* Power/influence grid
			* Influence/impact grid
			* Salience model: ability to impose their will on the project
			* Stakeholder cube

	== Resources ==		== Resources ==

Savoundg at 08:43, 19 December 2018

2018-12-19T08:43:54Z

← Older revision		Revision as of 08:43, 19 December 2018
Line 6:		Line 6:
	* 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.		* 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.		** 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 decisions and		**Balanced:The Project Manager can enforce and make decisions but he does not have full authority on the project and the funding.
	**Strong:		**Strong: A full-time project Project Manager with considerable authority on the project.
	* Project-based Organization		* 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.
	{\| class="wikitable"		{\| class="wikitable"
	!Organization Structure		!Organization Structure

Savoundg at 08:36, 19 December 2018

2018-12-19T08:36:45Z

@@ Line 3: / Line 3: @@
 === Project Organization Type ===
-* Functional Organization
+* 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
+* 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
+** 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 decisions and
 * Project-based Organization
 ==== Project Organization Chart ====