Monday, May 26, 2014

Prince 2 Overview


What is PRINCE2?

PRojects IN Controlled Environment [PRINCE2] is a non-proprietary method used extensively in more than 150 countries around the world, and its take-up grows daily. It is widely considered as the leading method in project management, with in excess of 20,000 organizations already benefiting from its pioneering and trusted approach. This is largely due to the fact that PRINCE2 is truly generic: it can be applied to any project regardless of scale, type, organization, geography or culture.
PRINCE2 comprises a set of principles; a set of control themes, a process lifecycle and guidance on matching the method to the project’s environment (see Figure 1). PRINCE2 provides a process model for managing a project. This consists of a set of activities that are required to direct, manage and deliver a project.

Benefits of PRINCE2

PRINCE2 provides the following benefits:

  • PRINCE2 can be applied to any type of project
  • It provides a common vocabulary and approach
  • PRINCE2 integrates easily with industry-specific models
  • The product focus clarifies for all parties what the project will deliver to agreed quality standards
  • PRINCE2 applies ‘management by exception’ providing efficient use of senior management time
  • It ensures a focus on the continuing viability of the project
  • It provides explicit definitions of roles and responsibilities so that everyone understands what

Principles

The PRINCE2 principles are the guiding obligations for good practice that a project should follow if it is using PRINCE2. These are derived from lessons, both good and bad, that have affected project success.
The principles provide a framework of good practice for those people involved in a project – ensuring that the method is not applied in an overly prescriptive way or in name only, but applied in a way sufficient to contribute to the success of the project.


Figure 1 Structure of Prince 2

Principle
 Definition
Continued business justification
A PRINCE2 project has continued business justification
Learn from experience
PRINCE2 project teams learn from previous experience (lessons are sought, recorded and acted upon throughout the life of the project)
Defined roles and responsibilities
A PRINCE2 project has defined and agreed roles and responsibilities with an organizational structure that engages the business, user and supplier stakeholder interests
Manage by stages
A PRINCE2 project is planned, monitored and controlled on a stage-by-stage basis
Manage by exception
A PRINCE2 project has defined tolerances for each project objective to establish limits of delegated authority
Focus on products
A PRINCE2 project focuses on the definition and delivery of products, in particular their quality requirements
Tailor to suit the project environment
PRINCE2 is tailored to suit the project’s size, environment, complexity, importance, capability and risk

Themes

The PRINCE2 themes are those aspects of project management that need to be addressed continually throughout the project lifecycle (i.e. not once only). They provide guidance on how the process should be performed. For example, numerous processes in PRINCE2 involve creating or approving plans and explanatory guidance on this can be found in the plans theme.

The set of PRINCE2 themes describes:
·         How baselines for benefits, risks, scope, quality, cost and time are established (in the Business Case, quality and plans themes)
·         How the project management team monitors and controls the work as the project progresses (in the progress, quality, change and risk themes).
The organization theme supports the other themes with a structure of roles and responsibilities with clear paths for delegation and escalation.

Theme
 Questions answered by the theme
Business Case
 Why?
Organization
 Who?
Quality
 What?
Plans
 How? How much? When?
Risk
 What if?
Change
 What’s the impact?
Progress
 Where are we now? Where are we going? Should we carry on?

Processes


Figure 2 Prince 2 Process Model

PRINCE2 provides a process model for managing a project. This consists of a set of activities that are required to direct, manage and deliver a project.
Starting up a Project:  Covers the pre-project activities required to commission the project and to gain commitment from corporate or programme management to invest in project initiation by answering the question: ‘Do we have a viable and worthwhile project?’
Directing a Project:  Describes the Project Board’s activities in exercising overall project control. The activities focus on the decision making necessary for Project Board members to fulfil their accountabilities successfully while delegating the day-today management of the project to the Project Manager.
Initiating a Project:  Describes the activities the Project Manager must lead in order to establish the project on a sound foundation. Every PRINCE2 project has an initiation stage. The key deliverable from this stage is the Project Initiation Documentation, which includes an overall Project Plan and defines baselines for the six project performance targets of time, cost, quality, scope, risk and benefits.
Managing a Stage Boundary:  Describes the activities the Project Manager must undertake to provide the Project Board with sufficient information to enable it to review the success of the current stage, approve the next Stage Plan, review the updated Project Plan and confirm continued business justification and acceptability of the risks.
Controlling a Stage:  Describes how the Project Manager manages the project execution/delivery activity during a stage, and reports progress and exceptions to the Project Board.
Managing Product Delivery:  Addresses the Team Manager’s role in supervising the detailed work of creating the project’s products and provides the link between the Project Manager and the teams undertaking the project work.
Closing a Project:  Describes the closure activity towards the end of the final stage of the project. The Project Manager leads the process which provides for an orderly decommissioning, including any remaining project acceptance and handover requirements.

The project environment

It is a PRINCE2 principle that the method must be tailored to suit the particular project context.
Tailoring refers to the measures taken to apply the method properly to an individual project, ensuring that the amount of governance, planning and control is appropriate – neither too burdensome for a simple project nor too informal for a large or complex project.

The adoption of PRINCE2 across an organization is known as embedding.

Embedding (done by the organization to adopt PRINCE2)
Tailoring (done by the project management team to adapt the method to the context of a specific project)
Focus on:
Focus on:
·         Process responsibilities
·         Scaling rules/guidance (e.g. score card)
·         Standards (templates, definitions)
·         Training and development
·         Integration with business processes
·         Tools
·         Process assurance
·         Adapting the themes (through the strategies and controls)
·         Incorporating specific terms/language
·         Revising the Product Descriptions for the management products
·         Revising the role descriptions for the PRINCE2 project roles
·         Adjusting the processes to match the above



Sunday, May 25, 2014

15) PMP Formulas and Calculation

PMP Formulas and Calculation for the Certification Demystified

Many consider the most difficult part of the PMP exam to be the calculations and PMP formulas. Luckily PMP calculation is not quantum physics, you just need to understand and memorize the following PMP Calculation formulas.


PMP Formulas
Name (Abbreviation)
Formula
Interpretation
No. of Communication Channels
n (n-1)/2
n = number of members in the team
n should include the project manager

e.g. if the no. of team members increase from 4 to 5, the increase in communication channels:
5(5-1)/2 – 4(4-1)/2 = 4
Schedule Performance Index (SPI)
SPI = EV/PV
EV = Earned Value
PV = Planned Value
< 1    behind schedule
= 1    on schedule
> 1    ahead of schedule
Cost Performance Index (CPI)
CPI = EV/AC
EV = Earned Value
AC = Actual Cost
< 1    Over budget
= 1    On budget
> 1    Under budget

sometimes the term ‘cumulative CPI’ would be shown, which actually is the CPI up to that moment
Schedule Variance (SV)
SV = EV – PV
EV = Earned Value
PV = Planned Value
< 0    Behind schedule
= 0    On schedule
> 0    Ahead of schedule
Cost Variance (CV)
CV = EV – AC
EV = Earned Value
AC = Actual Cost
< 0    Over budget
= 0    On budget
> 0    Under Budget
Estimate at Completion (EAC) if original is flawed
EAC = AC + New ETC
AC = Actual Cost
New ETC = New Estimate to Completion
if the original estimate is based on wrong data/assumptions or circumstances have changed
Estimate at Completion (EAC) if BAC remains the same
EAC = AC + BAC – EV
AC = Actual Cost
BAC = Budget at completion
EV = Earned Value
the variance is caused by a one-time event and is not likely to happen again
Estimate at Completion (EAC) if CPI remains the same
EAC = BAC/CPI
BAC = Budget at completion
CPI = Cost performance index
if the CPI would remain the same till end of project, i.e. the original estimation is not accurate
Estimate at Completion (EAC) if substandard performance continues
EAC = AC + (BAC -EV)/(CPI*SPI)
AC = Actual Cost
BAC = Budget at completion
EV = Earned Value
CPI = Cost Performance Index
SPI = Schedule Performance Index
use when the question gives all the values (AC, BAC, EV, CPI and SPI), otherwise, this formula is not likely to be used
To-Complete Performance Index (TCPI)
TCPI = (BAC – EV)/
(BAC – AC)
BAC = Budget at completion
EV = Earned value
AC = Actual Cost
TCPI = Remaining Work
/Remaining Funds
BAC = Budget at completion
EV = Earned value
CPI = Cost performance index
< 1    Under budget
= 1    On budget
> 1    Over budget
Estimate to Completion 
ETC = EAC -AC
EAC = Estimate at Completion
AC = Actual Cost
Variance at Completion
VAC = BAC – EAC
BAC = Budget at completion
EAC = Estimate at Completion
< 0    Under budget
= 0    On budget
> 0    Over budget
PERT Estimation
(O + 4M + P)/6
O= Optimistic estimate
M= Most Likely estimate
P= Pessimistic estimate
Standard Deviation
(P – O)/6
O= Optimistic estimate
P= Pessimistic estimate
this is a rough estimate for the standard deviation
Float/Slack
LS – ES
LS = Late start
ES = Early start
LF – EF
LF = Late finish
EF = Early finish
= 0    On critical path
< 0    Behind

Hope, the series of my blogs in PMI - PMP (PMBOK 5)  is informative and useful inputs for your exam if you are preparing for PMP Certificate. All the very best!

14) Professional and Social Responsibility

Professional and Social Responsibility

Responsibility

  • in the best interest of the society, public and environment
  • accept assignments consistent with skills and fulfill commitments
  • accept stretch assignment when the assigner is fully aware of the skill gaps
  • own error and make corrections
  • uphold laws and regulations
  • report illegal/unethical activities substantiated with facts
  • ask for direction should the decision is beyond assigned authority

Respect

  • show respect to others
  • listen and understand others
  • conduct in a professional manner, even if not reciprocated
  • resolve conflicts directly
  • negotiate in good faith
  • do not influence others for personal benefits
  • respect others rights

Fairness

  • transparency in decision making
  • be objective
  • provide equal access to information, equal opportunities
  • disclose any conflict of interests and refrain from making decisions in case of conflict of interest
  • do not deny opportunities base on personal considerations
  • do not discriminate
  • apply rules without favoritism or prejudice

Honesty

  • understand the truth and be truthful
  • honor commitments
  • not to deceive others
  • not engage in dishonest behavior for personal gain / at the expense of others

13) STAKEHOLDER Management

 |  STAKEHOLDER Management
  • stakeholders are groups/individuals who may affect / be affected by the project
  • identify stakeholders is a continually process throughout the project life cycle
  • identify stakeholders, communicate and engage them, manage expectations and focus on satisfaction
  • stakeholder satisfaction is a key project objective
  • the Project Manager is responsible for the engaging and managing the various stakeholders in a project
Project Stakeholder Management PITTOs:

Processes
Inputs
Tools & Techniques
Output
Identify Stakeholders
Project Charter
Procurement Documents
Enterprise Environment Factors
Organization Process Assets
Stakeholder Analysis
Expert Judgment
Meetings
Stakeholder Register
Plan Stakeholder Management
PM Plan Stakeholder Register
Enterprise Environment Factors
Organization Process Assets
Expert Judgment
Meetings
Analytical Techniques
Stakeholder Management Plan
Project Documents Updates
Manage Stakeholder Engagement
Stakeholder Management Plan
Communication Management Plan
Change Log
Organization Process Assets
Communication Methods
Interpersonal Skills
Management Skills
Issue Log
Change Requests
PM Plan Updates
Project Document Updates
OPA Updates
Control Stakeholder Engagement
PM Plan
Issue Log
Work Performance Data
Project Documents
Information Management Systems
Expert
Judgment
Meetings
Work Performance Information
Change Requests
PM Plan Updates
Project Document Updates
OPA Updates

Identify Stakeholders

  • identify stakeholders and document their importance/influence (=active involvement) /impact/interest/involvement
  • 3 ‘I’s: importance, interest, influence
  • stakeholders from operation process needed to be included
  • determine the stakeholders’ hot buttons (what response in specific situations) and develop support strategies
  • procurement documents are used for determining external stakeholders such as the seller
  • stakeholders have the greatest influence in the initial stage of the project
  • stakeholder analysis matrix is part of the stakeholder management strategy (output of identify stakeholders)
  • Salience Model: describing stakeholders based on the power (influence), urgency and legitimacy
  • document only influential stakeholders if there is a large number of stakeholders
  • document the impact using a power/influence grid, power/interest grid, influence/impact grid, salience model

Plan Stakeholder Management

  • management strategies to engage stakeholders throughout project life-cycle
  • Stakeholder Management Plan contains: current/desired engagement levels, scope and impact to stakeholders, interrelationships, communication requirements and forms, how to update the plan
  • The distribution of this plan requires precautions as the engagement level of stakeholders is a very sensitive information
  • Engagement Level
    • Unaware
    • Resistant: resistant to change
    • Neutral
    • Supportive: supportive of change
    • Leading: actively engaged for project success
  • Stakeholder Engagement Assessment Matrix: (C-current level, D-desired level)

Manage Stakeholder Engagement

  • aim: increase support and minimize resistance from stakeholders by addressing issues
  • the communication requirements of individual stakeholder are recorded in the Project Communication Plan
  • PM may call upon sponsor for assistance
  • communicate and work with stakeholders to meet their needs/expectations and address issues
  • build trust and resolve conflicts, negotiation skills, communication skills
  • need to communicate bad news/issues in a timely manner
  • feedback from stakeholders is stored in OPA
  • the Issue Log (Action Item Log): to identify issues/define impacts, owner (most important element) and priority/with due date

Control Stakeholder Engagement

  • monitor overall stakeholder relationships and adjusting strategies