Search

Managing Successful Projects with PRINCE2®

Apart from Project Management Professional (PMP)®, PRINCE2® (PRojects IN Controlled Environments) is one of the most widely used methods for managing projects across the globe. It is a very methodical way of managing projects based on experience drawn from various projects and from the contributions of numerous people who worked using PRINCE2, such as project sponsors, project managers, project teams, academics, trainers and consultants. Its generic design can be applied to any project regardless of project scale, type, organization, geography or culture. It separates the project management work from specialist contributions, like design or construction Focus is on describing what needs to be done, instead of prescribing how project is to be done. PRINCE2®: is based more on governance for project management is tailored to meet the needs of the organization  is implemented alongside industry-specific models e.g. ’engineering models’ or ‘development lifecycles’ helps participants focus on the viability of the project in relation to objectives mentioned in the business case makes sure that everybody involved is represented in planning and decision-making, appropriately inspires to learn lessons from experience in the projects and helps in continual improvement within the organizations.PRINCE2 in Project Management Some characteristics of project work that differentiates itself from business as usual (BAU) are:- Change - Projects are a great catalyst for introducing change. Temporary - Projects have a definite start and a definite end.   Cross-functional - people having different skills work together Unique - each project will be unique such as it involves a different customer, a different time. a different team, a different location Uncertainty – All projects carry a very high uncertainty – threats and opportunities. What are six project constraints that we wish to control throughout a projectCosts – spending depends on the budget given to the project manager Timescales - A question the project manager is most frequently asked: What is your expected project completion date? Quality - products must be fit for the purpose for which they are produced. Scope – What is in-scope and out-of-scope of the project Benefits – What is the reason for doing this? A very crystal-clear understanding of the purpose of the project is required by the project manager Risk - All projects are risky but project manager must be aware of exactly how much risk we are  in a position to accept PRINCE2 assumes that there will be - a customer who will specify the requirement of a product  a supplier who will provide all skilled resources to deliver that product PRINCE2 StructureThe PRINCE2 Seven Principles are:- 1. Continued business justification - A PRINCE2 project has continued business justification. All PRINCE2 projects require that: for starting the project, there has to be a justifiable reason this justification must be recorded and approved the justification must remain valid and is revalidated, throughout the project life-cycle to ensure that the project remains in line with the benefits which contribute to business objectives justification is documented either as a business case document or may use some business plans or any other similar document 2. Learn from experience - lessons learned (seek), recorded and acted upon throughout the project. 3. Defined roles and responsibilities - within an organization structure engages the business, user and supplier stakeholder interests 4. Manage by stages - A PRINCE2 project is planned, monitored and controlled on a stage-by-stage basis. In PRINCE2, a project must have at least two management stages: an initiation stage at least one further management stage. 5. Manage by exception - tolerances are defined for each project objective, to set limits for delegating authority. 6. Focus on products – focus is more on the defining the products and delivery of products, including quality requirements.7. Tailor to suit the environment - PRINCE2 can be tailored to suit the project size, complexity, team capability, environment, importance and risk. Project manager and project board will have to make choices including decisions on how PRINCE2 should be applied on the project.PRINCE2 Seven Themes The PRINCE2 Seven Themes are - Business Case (Why?): a project usually starts with an idea or a concept which is then considered to have potential value for the organization concerned. This theme addresses how the idea is developed into a viable investment proposition for the organization and how project management maintains the focus on the organization’s objectives throughout the project. Organization (Who?): organization which commissions the project needs to allocate the work to managers who will be responsible for it and steer it through to completion. Projects are cross-functional. This theme describes the roles and responsibilities the project management team is required to have, in order to manage the project efficiently and effectively. Quality (What?): all participants understand the quality attributes of the products to be delivered and then how the project management will ensure that these requirements are ultimately delivered. Plans (How? How much? When?):  project plan for the project as a whole, will usually be a high-level plan, providing indicative timescales, milestones, cost and resource requirements based on estimates detailed stage plan for the current management stage, aligned with the overall project plan timescales, produced before the start of that stage exception plans show actions performed to recover or come back on track from or avoid a forecast deviation from agreed tolerances, applies to project plan or stage plan a number of work packages are developed using detailed team planRisk (What if?): addresses how project management manages uncertainty. Change (What is the impact?): describes how project management assesses and responds to issues which have a potential impact on any of the baseline aspects of the project such as its plans and completed products. Issues may be instances of a product not meeting its specification or requests for change or unanticipated general problems. Progress (Where are we now? Where are we going? Should we carry on?): addresses the ongoing viability of the plans. This theme monitors actual performance, explains the decision-making process for approving plans and the escalation process if events do not go according to plan. Ultimately, it determines how and whether the project should proceed.PRINCE2 Seven Processes The PRINCE2 Seven Processes are:- Starting Up A Project (SU)  Purposeto ensure that the prerequisites for initiating a project are in place by answering the question: Do we have a viable and worthwhile project?  base information needed to make rational decisions such as commissioning of the project is defined, key roles and responsibilities are identified and resources are allocated and a foundation for detailed planning is made available.Objective: To ensure that: a business justification is documented in an outline business case, for initiating the project necessary authorities exist, for initiating the project project brief is available to define and confirm the scope of the project a feasible project approach is selected after evaluating different delivery approaches individuals are appointed who will undertake the project work  the work required for project initiation is planned and documented in a stage planDirecting A Project (DP)  Purpose: To enable project board  to be accountable for the project’s success by making key decisions and exercising overall control of the project and  delegating day-to-day management of the project to the project managerObjectiveTo ensure that some authority exists to initiate the project, to deliver the products and close the project management direction and control are provided to all concerned throughout the project’s life project remains viable at every stage corporate, programme management or the customer has a transparent interface to the project post-project benefits realization plans are reviewed and managedInitiating A Project (IP)  Purposeto establish a sturdy foundation for the project to understand the work that needs to be done to deliver the project’s products before committing to a large spend Objective: to ensure that there is a common understanding of - what are the reasons for doing the project, what benefits are expected and what are the associated risks what is the scope of the work and what are the products to be delivered how the products will be delivered, when should they be delivered and what would be the cost involved at that point of time What the project decision-making team is comprised of  how the required level of quality is be achieved how baselines can be established and controlled how risks, issues and changes can be identified, assessed and controlled how progress of the project can be monitored and controlled who requires which information, in what format and at what point of timeControlling A Stage (CS)  Controlling A Stage (CS)  Purpose: To assign and monitor work, deal with issues, report progress to the project board and take corrective actions to ensure that the management stage remains within tolerance Objective: to ensure that: proper attention is focused on delivery of the management stage’s products by monitoring to avoid uncontrolled change and loss of focus risks and issues are tracked to keep them under control business case is reviewed at appropriate times agreed products for the management stage are delivered to stated quality standards, within cost, effort and time agreed project management team is focused on delivering within the tolerance level setManaging Product Delivery (MPD)  Purpose: is to control the link between the project manager and the team manager(s). Both agree on requirements for acceptance, execution and delivery. Objective: to ensure that: product related work allocated to the team is authorized and agreed upon first team managers, team members and suppliers are clear about what needs to be produced and what is the expected effort, cost or timescales planned products are delivered to expectations and within tolerances accurate information on progress of product development should be provided to the project manager at an agreed frequency to ensure that expectations are managed Managing a Stage Boundary (SB) Purpose: to enable the project manager to provide the project board with sufficient information to be able to: review the current management stage if it has completed successfully approve the next stage plan review the updated project plan confirm continued business justification and acceptability of the risks Hence, this process should either be executed at the end of or close to the end of each management stage.Objective: is to: give an assurance to the project board that all products produced in the stage plan for the current management stage are developed by the team and approved prepare the next management stage plan review the PID documents and if necessary, update the business case, project plan, project approaches, project management team structure and role descriptions provide all the accurate information required by the project board to assess the continuing viability of the project record any information gathered or lessons learned that can help later management stages of the current project and/or other/future projects request authorization to start the next management stage from the project board For exceptions, the objectives are to: review the PID documents and if necessary, update the customer’s quality expectations, project approaches and controls and role descriptions provide all the accurate information required by the project board to assess the continuing viability of the project prepare an exception plan as directed by the project board without fail and further delay project manager must seek approval to replace the project plan or stage plan for the current management stage with the exception plan Managing a stage boundary is not performed towards the end of the final management stage, except an exception plan may be created on need basis.Closing A Project (CP) Purposeprovide a normal termination point at which acceptance of the project’s product is confirmed and accepted by the user group recognize that objectives set out in the original PID documents have been achieved (or approved changes to the objectives have been achieved), or that the project has nothing more to contributeObjectiveverify that the final product has been accepted by the user  make sure that the operations are able to support the products when the project is disbanded review the performance of the project against its baselines assess any benefits that have been realized during the project cycle and update the benefits management approach to include any post-project benefit reviews ensure that provision has been made to address all open issues and risks, with follow-on action recommendationsTeam roles in PRINCE2 Project Board Members: Executive, Senior Users and Senior Suppliers ResponsibilitiesAccountable for the success or failure of the project Provides unified direction to the project Delegates effectively Facilitates integration Authorizes the funds Effective decision-making Supports the project manager Ensures effective communicationExecutive Appointed by Corporate,  Programme management or Customer Ultimately responsible for the project Key decision maker, buck stops at him Ensures project is focused throughout its life on achieving its objectives Ensures project delivers value for money Ensures project is aligned to corporate strategy. ResponsibilitiesDesign and appoint project management team Oversee development of the Project Brief Oversee development of detailed Business Case Secure funding for the project Hold Senior Supplier accountable for the quality and integrity of the product Hold Senior User accountable for realizing the benefits Monitor and control the progress at strategic level Chair Project Board reviews Project Manager Given authority to run the project on a day to day basis  Ensures that the project produces the required products Responsible for producing the result capable of achieving the benefits as stated in the business case Responsibilities  Produce key project documents Prepare key project reports Maintain key project records Liaise with corporate, programme management or customer Liaise with external suppliers Lead and motivate the project management team Manage information flows between various levels of the project Manage production of the required products Establish and manage the project procedures Authorize Work Packages Advise the Project Board of any deviations from the planSenior User Specifies the needs of those who will use the project’s products. Represents the interests of : Those who will use the project’s products. Those for whom the products will achieve an objective Those who will use the products to deliver benefitsResponsibilitiesProvide the customer’s quality expectations Ensure project products deliver the desired outcomes Ensure that expected benefits are realized Resolve user requirements and priority conflicts Ensure availability of user resources Make decisions on escalated issues Undertake Project Assurance from user perspectiveSenior Supplier Represents interest of those producing the project products Accountable for quality of products delivered by the supplier Responsible for technical integrity of the projectResponsibilitiesAssess the viability of the project Ensure that proposals are realistic Advise on the selection of product methods Ensure that supplier resources are made available Make decisions on escalated issues Resolve supplier requirements and priority conflicts Ensure adherence to quality procedures Undertake Project Assurance from supplier perspective.Project Assurance Covers the primary stakeholder interests Has to be independent of the Project Manager Has sufficient credibility May be from corporate, programme management or customer organization.ResponsibilitiesLiaison between business, user and supplier is maintained Risks are controlled Right people are involved in writing product descriptions Right people are planned and involved in quality inspections Staff are properly trained in quality methods Quality methods are adhered to An acceptable solution is being developed Applicable standards are being used Change Authority Authority for approving responses to requests for change or off-specifications Adequately represents the business, user and supplier interests Has sufficiently credibility Change Authority could be assigned to:  Corporate or Programme management Project Board A nominated person / body Project Manager. ResponsibilitiesReview and approve or reject all requests for change and off-specifications within the delegated limits of authority and change budget set by the Project Board. Refer to the Project Board if any delegated limits of authority or allocated change budget are forecast to be exceeded. Project Support Is mainly concerned with providing administrative services or advice and guidance on the use of project management tools. Is the responsibility of the Project Manager. May be delegated to other roles or a separate role. Project Support and Project Assurance roles must be kept separate. ResponsibilitiesSet up and maintain project files Establish document control procedure Collect data – actuals and forecasts Update plans and maintain them Administer quality review progress Administer project board meetings Assist with compilation of reports Contribute expertise in tools and techniques Maintain key records Administer the configuration management procedure.Team Manager Reports to and takes direction from the Project Manager Responsible to ensure production of products allocated by the Project Manager Reasons for allocating a separate Team Manager : Size of the project Specialist skills or knowledge needed Geographical location, or Preferences of the Project Board. ResponsibilitiesPrepare the Team Plan Produce Checkpoint Reports Plan, monitor and manage the team’s work Ensure progress of team’s work and use of team resources Identify any issues and risks associated with a Work Package Advise Project Manager of any deviations Hand over completed and approved products Liaise with Project Assurance and Project Support roles Plan and manage quality activities relating to team’s work. Types of PRINCE2 documentation Throughout PRINCE2 project, documentation is maintained as management products.  There are three types of management product: baselines, records and reports. Baseline management products: are those that define aspects of the project and, when approved, are subject to change control. These are: Benefits management approach Business case Change control approach Communication management approach Plan (covers project plans, stage plans, exception plans and, optionally, team plans) Product description Project brief Project initiation documentation (PID) Project product description Quality management approach Risk management approach Work package Records management products: are dynamic and they maintain information regarding project progress. These are: Configuration item record Daily log Issue register Lessons log Quality register Risk register. Reports management products: provide a snapshot of the status of certain aspects of the project. These are: Checkpoint report End project report End stage report Exception report Highlight report Issue report Lessons report Product status accountSummary PRINCE2 is PRojects IN Controlled Environments separates the management of project work from the specialist contributions, such as design or construction.  focuses on describing what needs to be done, rather than prescribing how everything is to be done focusing on describing what needs to be done, rather than prescribing how everything is done. Characteristics of project work that differentiates itself from business as usual (BAU) are Change, Temporary, Cross-functional, Unique and Uncertainty We wish to control Cost, Timescale, Scope, Quality, Benefits and Risk on a PRINCE2 project PRINCE2 assumes that there will be - a customer who will specify the desired result  a supplier who will provide the resources and skills to deliver that result PRINCE2 principles are :- Continued business justification Learn from experience Defined roles and responsibilities Manage by stages Manage by exception Focus on products Tailor to suit the project PRINCE2 Themes are :- Business Case Organization Quality Plans Risk Change Progress PRINCE2 processes are :- Starting Up a Project (SU) Directing A Project (DP) Initiating A Project (IP) Controlling A Stage (CS) Managing Product Delivery (MPD) Managing a Stage Boundary (SB) Closing A Project (CP) PRINCE2 Team roles are – Project Board (Executive, Senior User and Senior Supplier), Project Manager, Team Manager, Project Assurance, Change Authority and Project Support Throughout PRINCE2 project, documentation is maintained as management products - baselines, records and reports. 

Managing Successful Projects with PRINCE2®

7K
Managing Successful Projects with PRINCE2®

Apart from Project Management Professional (PMP)®PRINCE2® (PRojects IN Controlled Environments) is one of the most widely used methods for managing projects across the globe. It is a very methodical way of managing projects based on experience drawn from various projects and from the contributions of numerous people who worked using PRINCE2, such as project sponsors, project managers, project teams, academics, trainers and consultants. 

Its generic design can be applied to any project regardless of project scale, type, organization, geography or culture. 

  • It separates the project management work from specialist contributions, like design or construction 
  • Focus is on describing what needs to be done, instead of prescribing how project is to be done. 

PRINCE2®: 

  • is based more on governance for project management 
  • is tailored to meet the needs of the organization  
  • is implemented alongside industry-specific models e.g. ’engineering models’ or ‘development lifecycles’ 
  • helps participants focus on the viability of the project in relation to objectives mentioned in the business case 
  • makes sure that everybody involved is represented in planning and decision-making, appropriately 
  • inspires to learn lessons from experience in the projects and helps in continual improvement within the organizations.

PRINCE2 in Project Management 

Some characteristics of project work that differentiates itself from business as usual (BAU) are:- 

  • Change - Projects are a great catalyst for introducing change. 
  • Temporary - Projects have a definite start and a definite end.   
  • Cross-functional - people having different skills work together 
  • Unique - each project will be unique such as it involves a different customer, a different time. a different team, a different location 
  • Uncertainty  All projects carry a very high uncertainty – threats and opportunities. 

What are six project constraints that we wish to control throughout a project

  • ix project constraints that we wish to control throughout a projectCosts  spending depends on the budget given to the project manager 
  • Timescales - question the project manager is most frequently asked: What is your expected project completion date? 
  • Quality - products must be fit for the purpose for which they are produced. 
  • Scope  What is in-scope and out-of-scope of the project 
  • Benefits  What is the reason for doing this? A very crystal-clear understanding of the purpose of the project is required by the project manager 
  • Risk - All projects are risky but project manager must be aware of exactly how much risk we are  in a position to accept 

PRINCE2 assumes that there will be - 

  • a customer who will specify the requirement of a product  
  • a supplier who will provide all skilled resources to deliver that product 

PRINCE2 Structure

PRINCE2 Structure

The PRINCE2 Seven Principles are:- 

1. Continued business justification - A PRINCE2 project has continued business justification. 

All PRINCE2 projects require that: 

  • for starting the project, there has to be a justifiable reason 
  • this justification must be recorded and approved 
  • the justification must remain valid and is revalidated, throughout the project life-cycle to ensure that the project remains in line with the benefits which contribute to business objectives 
  • justification is documented either as a business case document or may use some business plans or any other similar document 

2. Learn from experience - lessons learned (seek), recorded and acted upon throughout the project. 

3. Defined roles and responsibilities - within an organization structure engages the business, user and supplier stakeholder interests 

4. Manage by stages - A PRINCE2 project is planned, monitored and controlled on a stage-by-stage basis. 

In PRINCE2, a project must have at least two management stages: 

  • an initiation stage 
  • at least one further management stage. 

5. Manage by exception - tolerances are defined for each project objective, to set limits for delegating authority. 

6. Focus on products  focus is more on the defining the products and delivery of products, including quality requirements.

7. Tailor to suit the environment - PRINCE2 can be tailored to suit the project size, complexity, team capability, environment, importance and risk. Project manager and project board will have to make choices including decisions on how PRINCE2 should be applied on the project.

PRINCE2 Seven Themes 

The PRINCE2 Seven Themes are - 

  • Business Case (Why?): project usually starts with an idea or a concept which is then considered to have potential value for the organization concerned. This theme addresses how the idea is developed into a viable investment proposition for the organization and how project management maintains the focus on the organization’s objectives throughout the project. 
  • Organization (Who?): organization which commissions the project needs to allocate the work to managers who will be responsible for it and steer it through to completion. Projects are cross-functional. This theme describes the roles and responsibilities the project management team is required to have, in order to manage the project efficiently and effectively. 
  • Quality (What?): all participants understand the quality attributes of the products to be delivered and then how the project management will ensure that these requirements are ultimately delivered. 
  • Plans (How? How much? When?):  
    • project plan for the project as a wholewill usually be a high-level plan, providing indicative timescales, milestones, cost and resource requirements based on estimates 
    • detailed stage plan for the current management stage, aligned with the overall project plan timescalesproduced before the start of that stage 
    • exception plans show actions performed to recover or come back on track from or avoid a forecast deviation from agreed tolerances, applies to project plan or stage plan 
    • a number of work packages are developed using detailed team plan

The PRINCE2 Seven Themes are

  • Risk (What if?): addresses how project management manages uncertainty. 
  • Change (What is the impact?): describes how project management assesses and responds to issues which have a potential impact on any of the baseline aspects of the project such as its plans and completed products. Issues may be instances of a product not meeting its specification or requests for change or unanticipated general problems. 
  • Progress (Where are we now? Where are we going? Should we carry on?): addresses the ongoing viability of the plans. This theme monitoractual performanceexplains the decision-making process for approving plans and the escalation process if events do not go according to plan. Ultimately, it determines how and whether the project should proceed.

PRINCE2 Seven Processes 

The PRINCE2 Seven Processes are:- 

Starting Up A Project (SU)  

Purpose

  • to ensure that the prerequisites for initiating a project are in place by answering the question: Do we have a viable and worthwhile project?  
  • base information needed to make rational decisions such as commissioning of the project is defined, key roles and responsibilities are identified and resources are allocated and a foundation for detailed planning is made available.

Objective: To ensure that: 

  • a business justification is documented in an outline business case, for initiating the project 
  • necessary authorities exist, for initiating the project 
  • project brief is available to define and confirm the scope of the project 
  • a feasible project approach is selected after evaluating different delivery approaches 
  • individuals are appointed who will undertake the project work  
  • the work required for project initiation is planned and documented in a stage plan

Directing A Project (DP)  

Purpose: To enable project board  

  • to be accountable for the project’s success by making key decisions and exercising overall control of the project and  
  • delegating day-to-day management of the project to the project manager

Objective

To ensure that 

  • some authority exists to initiate the projectto deliver the products and close the project 
  • management direction and control are provided to all concerned throughout the project’s life 
  • project remains viable at every stage 
  • corporate, programme management or the customer has a transparent interface to the project 
  • post-project benefits realization plans are reviewed and managed

Initiating A Project (IP)  

Purpose

  • to establish a sturdy foundation for the project 
  • to understand the work that needs to be done to deliver the project’s products before committing to a large spend 

Objective: to ensure that there is a common understanding of - 

  • what are the reasons for doing the project, what benefits are expected and what are the associated risks 
  • what is the scope of the work and what are the products to be delivered 
  • how the products will be delivered, when should they be delivered and what would be the cost involved at that point of time 
  • What the project decision-making team is comprised of  
  • how the required level of quality is be achieved 
  • how baselines can be established and controlled 
  • how risks, issues and changes can be identified, assessed and controlled 
  • how progress of the project can be monitored and controlled 
  • who requires which information, in what format and at what point of time

Controlling Stage (CS)  

Controlling Stage (CS)  

Purpose: To assign and monitor work, deal with issues, report progress to the project board and take corrective actions to ensure that the management stage remains within tolerance 

Objective: to ensure that: 

  • proper attention is focused on delivery of the management stage’s products by monitoring to avoid uncontrolled change and loss of focus 
  • risks and issues are tracked to keep them under control 
  • business case is reviewed at appropriate times 
  • agreed products for the management stage are delivered to stated quality standards, within cost, effort and time agreed 
  • project management team is focused on delivering within the tolerance level set

Managing Product Delivery (MPD)  

Purpose: is to control the link between the project manager and the team manager(s). Both agree on requirements for acceptance, execution and delivery. 

Objective: to ensure that: 

  • product related work allocated to the team is authorized and agreed upon first 
  • team managers, team members and suppliers are clear about what needs to be produced and what is the expected effort, cost or timescales 
  • planned products are delivered to expectations and within tolerances 
  • accurate information on progress of product development should be provided to the project manager at an agreed frequency to ensure that expectations are managed 

Managing a Stage Boundary (SB) 

Purpose: to enable the project manager to provide the project board with sufficient information to be able to: 

  • review the current management stage if it has completed successfully 
  • approve the next stage plan 
  • review the updated project plan 
  • confirm continued business justification and acceptability of the risks 

Hence, this process should either be executed at the end of or close to the end of each management stage.

Objective: is to: 

  • give an assurance to the project board that all products produced in the stage plan for the current management stage are developed by the team and approved 
  • prepare the next management stage plan 
  • review the PID documents and if necessary, update the business case, project plan, project approaches, project management team structure and role descriptions 
  • provide all the accurate information required by the project board to assess the continuing viability of the project 
  • record any information gathered or lessons learned that can help later management stages of the current project and/or other/future projects 
  • request authorization to start the next management stage from the project board 

For exceptions, the objectives are to: 

  • review the PID documents and if necessary, update the customer’s quality expectations, project approaches and controls and role descriptions 
  • provide all the accurate information required by the project board to assess the continuing viability of the project 
  • prepare an exception plan as directed by the project board 
  • without fail and further delay project manager must seek approval to replace the project plan or stage plan for the current management stage with the exception plan 

Managing a stage boundary is not performed towards the end of the final management stage, except an exception plan may be created on need basis.

Closing A Project (CP) 

Purpose

  • provide a normal termination point at which acceptance of the project’s product is confirmed and accepted by the user group 
  • recognize that objectives set out in the original PID documents have been achieved (or approved changes to the objectives have been achieved), or that the project has nothing more to contribute

Objective

  • verify that the final product has been accepted by the user  
  • make sure that the operations are able to support the products when the project is disbanded 
  • review the performance of the project against its baselines 
  • assess any benefits that have been realized during the project cycle and update the benefits management approach to include any post-project benefit reviews 
  • ensure that provision has been made to address all open issues and risks, with follow-on action recommendations

Team roles in PRINCE2 

Project Board 

Members: Executive, Senior Users and Senior Suppliers 

Responsibilities

  • Accountable for the success or failure of the project 
  • Provides unified direction to the project 
  • Delegates effectively 
  • Facilitates integration 
  • Authorizes the funds 
  • Effective decision-making 
  • Supports the project manager 
  • Ensures effective communication

Executive 

  • Appointed by Corporate,  Programme management or Customer 
  • Ultimately responsible for the project 
  • Key decision maker, buck stops at him 
  • Ensures project is focused throughout its life on achieving its objectives 
  • Ensures project delivers value for money 
  • Ensures project is aligned to corporate strategy. 

Responsibilities

  • Design and appoint project management team 
  • Oversee development of the Project Brief 
  • Oversee development of detailed Business Case 
  • Secure funding for the project 
  • Hold Senior Supplier accountable for the quality and integrity of the product 
  • Hold Senior User accountable for realizing the benefits 
  • Monitor and control the progress at strategic level 
  • Chair Project Board reviews 

Project Manager 

  • Given authority to run the project on a day to day basis  
  • Ensures that the project produces the required products 
  • Responsible for producing the result capable of achieving the benefits as stated in the business case 

Responsibilities  

  • Produce key project documents 
  • Prepare key project reports 
  • Maintain key project records 
  • Liaise with corporate, programme management or customer 
  • Liaise with external suppliers 
  • Lead and motivate the project management team 
  • Manage information flows between various levels of the project 
  • Manage production of the required products 
  • Establish and manage the project procedures 
  • Authorize Work Packages 
  • Advise the Project Board of any deviations from the plan

Senior User 

  • Specifies the needs of those who will use the project’s products. 
  • Represents the interests of : 
    • Those who will use the project’s products. 
    • Those for whom the products will achieve an objective 
    • Those who will use the products to deliver benefits

Responsibilities

  • Provide the customer’s quality expectations 
  • Ensure project products deliver the desired outcomes 
  • Ensure that expected benefits are realized 
  • Resolve user requirements and priority conflicts 
  • Ensure availability of user resources 
  • Make decisions on escalated issues 
  • Undertake Project Assurance from user perspective

Senior Supplier 

  • Represents interest of those producing the project products 
  • Accountable for quality of products delivered by the supplier 
  • Responsible for technical integrity of the project

Responsibilities

  • Assess the viability of the project 
  • Ensure that proposals are realistic 
  • Advise on the selection of product methods 
  • Ensure that supplier resources are made available 
  • Make decisions on escalated issues 
  • Resolve supplier requirements and priority conflicts 
  • Ensure adherence to quality procedures 
  • Undertake Project Assurance from supplier perspective.

Project Assurance 

  • Covers the primary stakeholder interests 
  • Has to be independent of the Project Manager 
  • Has sufficient credibility 
  • May be from corporate, programme management or customer organization.

Responsibilities

  • Liaison between business, user and supplier is maintained 
  • Risks are controlled 
  • Right people are involved in writing product descriptions 
  • Right people are planned and involved in quality inspections 
  • Staff are properly trained in quality methods 
  • Quality methods are adhered to 
  • An acceptable solution is being developed 
  • Applicable standards are being used 

Change Authority 

  • Authority for approving responses to requests for change or off-specifications 
  • Adequately represents the business, user and supplier interests 
  • Has sufficiently credibility 
  • Change Authority could be assigned to:  
    • Corporate or Programme management 
    • Project Board 
    • A nominated person / body 
    • Project Manager. 

Responsibilities

  • Review and approve or reject all requests for change and off-specifications within the delegated limits of authority and change budget set by the Project Board. 
  • Refer to the Project Board if any delegated limits of authority or allocated change budget are forecast to be exceeded. 

Project Support 

  • Is mainly concerned with providing administrative services or advice and guidance on the use of project management tools. 
  • Is the responsibility of the Project Manager. 
  • May be delegated to other roles or a separate role. 
  • Project Support and Project Assurance roles must be kept separate. 

Responsibilities

  • Set up and maintain project files 
  • Establish document control procedure 
  • Collect data – actuals and forecasts 
  • Update plans and maintain them 
  • Administer quality review progress 
  • Administer project board meetings 
  • Assist with compilation of reports 
  • Contribute expertise in tools and techniques 
  • Maintain key records 
  • Administer the configuration management procedure.

Team Manager 

  • Reports to and takes direction from the Project Manager 
  • Responsible to ensure production of products allocated by the Project Manager 
  • Reasons for allocating a separate Team Manager : 
    • Size of the project 
    • Specialist skills or knowledge needed 
    • Geographical location, or 
    • Preferences of the Project Board. 

Responsibilities

  • Prepare the Team Plan 
  • Produce Checkpoint Reports 
  • Plan, monitor and manage the team’s work 
  • Ensure progress of team’s work and use of team resources 
  • Identify any issues and risks associated with a Work Package 
  • Advise Project Manager of any deviations 
  • Hand over completed and approved products 
  • Liaise with Project Assurance and Project Support roles 
  • Plan and manage quality activities relating to team’s work. 

Types of PRINCE2 documentation 

Throughout PRINCE2 project, documentation is maintained as management products.  

There are three types of management product: baselines, records and reports. 

Baseline management products: are those that define aspects of the project and, when approved, are subject to change control. These are: 

  • Benefits management approach 
  • Business case 
  • Change control approach 
  • Communication management approach 
  • Plan (covers project plans, stage plans, exception plans and, optionally, team plans) 
  • Product description 
  • Project brief 
  • Project initiation documentation (PID) 
  • Project product description 
  • Quality management approach 
  • Risk management approach 
  • Work package 

Records management products: are dynamic and they maintain information regarding project progress. These are: 

  • Configuration item record 
  • Daily log 
  • Issue register 
  • Lessons log 
  • Quality register 
  • Risk register. 

Reports management products: provida snapshot of the status of certain aspects of the project. These are: 

  • Checkpoint report 
  • End project report 
  • End stage report 
  • Exception report 
  • Highlight report 
  • Issue report 
  • Lessons report 
  • Product status account

Summary 

PRINCE2 is PRojects IN Controlled Environments 

  • separates the management of project work from the specialist contributions, such as design or construction.  
  • focuses on describing what needs to be done, rather than prescribing how everything is to be done focusing on describing what needs to be done, rather than prescribing how everything is done. 

Characteristics of project work that differentiates itself from business as usual (BAU) are Change, Temporary, Cross-functional, Unique and Uncertainty 

We wish to control Cost, Timescale, Scope, Quality, Benefits and Risk on a PRINCE2 project 

PRINCE2 assumes that there will be - 

  • a customer who will specify the desired result  
  • a supplier who will provide the resources and skills to deliver that result 

PRINCE2 principles are :- 

  • Continued business justification 
  • Learn from experience 
  • Defined roles and responsibilities 
  • Manage by stages 
  • Manage by exception 
  • Focus on products 
  • Tailor to suit the project 

PRINCE2 Themes are :- 

  • Business Case 
  • Organization 
  • Quality 
  • Plans 
  • Risk 
  • Change 
  • Progress 

PRINCE2 processes are :- 

  • Starting Up a Project (SU) 
  • Directing A Project (DP) 
  • Initiating A Project (IP) 
  • Controlling A Stage (CS) 
  • Managing Product Delivery (MPD) 
  • Managing a Stage Boundary (SB) 
  • Closing A Project (CP) 

PRINCE2 Team roles are – Project Board (Executive, Senior User and Senior Supplier), Project Manager, Team Manager, Project Assurance, Change Authority and Project Support 

Throughout PRINCE2 project, documentation is maintained as management products - baselines, records and reports. 

KnowledgeHut

KnowledgeHut

Author

KnowledgeHut is an outcome-focused global ed-tech company. We help organizations and professionals unlock excellence through skills development. We offer training solutions under the people and process, data science, full-stack development, cybersecurity, future technologies and digital transformation verticals.
Website : https://www.knowledgehut.com

Join the Discussion

Your email address will not be published. Required fields are marked *

Suggested Blogs

What is a Technical Project Manager?

Many experienced professionals would like to start their career as a Technical Project Manager. This could be a wise decision, but it is always important to know exactly what the role entails and what are the career benefits before you take it up seriously. You need to know what the job description would be, what skills are expected to perform the role, what would be the average salary you would be earning, what would be the responsibilities, what is expected from that role, and so on. Read on to know more! A Technical Project Manager is someone who can be looked at to be more of a technical professional and less of an inspiring leader. They may be good leaders though and could also be instrumental in providing project planning and management for established initiatives, such as planning and management of IT-related projects, within a company. They ensure that projects are completed as per specifications and most importantly within an established time frame and budget. A Technical Project Manager is the lead SME (subject matter expert) within the company for all technology-related concerns and in turn, they would recruit and train additional support members.  So, if you’re looking for a career as a Technical Project Manager, you are, first and foremost,  required to have a high level of mandatory technical expertise. Good organizational, leadership and communication skills are also essentials for this role. What Does a Technical Project Manager Do?Responsibilities of a Technical Project Manager include but not limited to : Developing a project plan which includes developing an approach of how to execute, monitor and control and close a project Developing a project schedule as a part of planning activity (timelines) showing project start date and end date,  all the activities sequenced, how many resources are working on each activity, what is the duration of each activity, estimated cost of each activity, milestones, and understanding the critical path of each project to control project completion on time. Ensuring training processes are established and then implementing them for all the technical professionals Determining what are the intermediate deliverables and the final product Defining clear roles and responsibilities for all team members Conducting regular team meetings to review status of the project and also to help address issues and/or challenges during the course of the project  Detailed research and evaluation of hardware and software technology options for every project Updating and maintaining all technologies installed on production Helping in recruitment to fill positions within the technical department and then further training all employees and new recruits Developing technical, user and training documentation How To Become a Technical Project Manager?1. Educational QualificationsTechnical project managers are expected to hold a bachelor’s degree in computer science or a related field, which ensures that they would be having an in-depth understanding of complete software development process (SDLC). They may also add qualifications such as courses in management information systems (MIS) as an added advantage. In recent times, it is expected that these professionals also hold an MBA degree, which takes two years to complete. MBA can be studied and completed while working (Earn and Learn). This matters a lot, because work experience is also equally important. A technical project manager would already have put in several years of working experience (say 5-7 years) before they take on managerial responsibilities. Since every organization in the world uses computer systems, technical project managers can have industry-specific experiences. An IT experienced technical project manager in a manufacturing environment, is unlikely to become a systems project manager in an educational industry later on in the career. 2. Professional Qualifications Apart from the above-mentioned educational qualifications and industry experience, it would be a great advantage if a Technical Project Manager adds a Project Management Professional (PMP)® credential from Project Management Institute (PMI)® to his/her professional qualification.  3. Benefits of PMPWidely recognized Project Management Certification Worldwide recognition of your knowledge of Project Management practices Demonstrates Proof of Professional Achievement Improves the way you manage your Project Increases your Marketability Displays your willingness to pursue Growth Increases Customer Confidence Valued Globally across Industry Verticals & Companies In order to apply, however, you need to meet the following criteria:EDUCATIONAL BACKGROUNDPROJECT MANAGEMENT EXPERIENCEPROJECT MANAGEMENT EDUCATIONSecondary Degree (High school diploma, associate's degree or global equivalent)Minimum five years/60 months unique non-overlapping professional project management experience during which at least 7,500 hours were spent leading and directing the project*35 contact hours of formal educationFour years degree(bachelor's degree or global equivalent)Minimum three years/36 months unique non-overlapping professional project management experience during which at least 4,500 hours were spent leading and directing the project**Leading and directing the project as identified with tasks, knowledge and skills specific in the project Management professional Examination Content Outline. Experience must be in all five process group across all your project management experience submitted on the application. However, on a single project you do not need to have experience in all five process groups.Your experience leading and directing projects does not refer only to an official project manager’s role, but it can include any of the roles listed below:  Project Lead or Team Lead Assistant Project Manager Project Planner Project Coordinator  Project Expeditor  Any other lead role on a project, which involves managing a small sized team by leading and directing an area of a project Note that you don’t have to be involved in planning a large or complex project in order to be eligible to apply for PMP. If you have been involved in arranging charity functions or small events, even that counts! You must also note that PMP uses waterfall (Plan-driven) methodology to complete projects. The current trend in the industry is that many corporates and organizations are moving to implement Agile methodology, as it is change-driven. This means that changes can be incorporated in the project at any time, and they will be catered to. In the case of Plan-driven waterfall methods, changes if any will have to be carefully managed at the end of the project after the final product is delivered. In short, it means that a Technical Project Manager in the current scenario must be aware of both the methodologies and the technicalities associated with each. PMI has a credential for Agile practitioners, the Agile Certified Practitioner (PMI-ACP)®, which can be also obtained.What’s The Average Salary for a Technical Program Manager?Those who are starting their career as a Technical Project Manager, i.e. as an entry-level professional, can expect to earn a salary between $60,000 to $65,000 p.a. In case you have experience between 1 to 4 years, you can earn a salary between $75,000 to $80,000 p.a. A mid-career Technical Project Manager with experience between 5 to 9 years usually earns a salary between $90,000 to $95,000 p.a.  A senior Technical Project Manager with a good number of years of experience, such as more than 10 years, can earn a salary of up to $105,000 p.a. And those who have 20+ years of experience, can earn upto $120,000+ p.a. as it also depends on how you negotiate. Note: Salaries mentioned above may vary from country-to-country. Technical Skills Requirements-A number of skills are considered as essential skills for a Technical Project Manager. A very clear understanding of the organization’s strategy and objectives is essential Before starting the project, knowledge of the project objective(s), what are we delivering and what the organization is seeking out of it – returns, growth, reputation, relations, knowledge base etc is needed Conduct benefit-analysis with relevant stakeholders to validate project alignment with organizational strategy and expected business value (Is this our cup of tea? Is it contributing to our mission?) Accountability when managing projects A thorough understanding, developing and managing project policies, procedures, templates and other shared documentation (organizational process assets i.e. organization’s knowledge base)  Supervising teams and decision-making capabilities Experience in up-skilling and re-skilling talent in the project management as well as in technology areas Ability to predict and overcome challenges and obstacles Strong competencies such as learning, systems thinking, trustworthiness, time management, adaptability, business acumen, industry knowledge, organization knowledge Apart from these competencies a Technical Project Manager should also possess excellent verbal communication, non-verbal communication, written communication, listening and pro-active skills Skills such as facilitation, leadership and influencing, teamwork, negotiation and conflict resolution and teaching would also add value All the above competencies should be supported by hands-on skills using office productivity tools and technology, project management tools and technology and most importantly communication tools and technology Sample Technical Project Manager Job Description TemplateJob OverviewExample Co. is one of the leading companies in our field in the area. We're proud of our 3.6 rating on Glassdoor from our employees. We are hiring a talented Technical Project Manager professional to join our team. If you're excited to be part of a winning team, Example Co. is a great place to grow your career. You'll be glad you applied to Example Co. Responsibilities for Technical Project Manager Establish and implement training processes and strategies for all technical personnel Analyze, plan and develop requirements and standards in reference to scheduled projects Assign and oversee the daily tasks of technical personnel while ensuring all subordinates are actively working toward established milestones Hold regular technical team meetings to determine progress and address any questions or challenges regarding projects Determine and define clear deliverables, roles and responsibilities for staff members required for specific projects or initiatives Research and evaluate hardware and software technology options and weigh the cost/benefit analysis when making large purchases on behalf of the company Recruit and train exceptional employees to fulfil posted positions within the technical department Update and maintain all production technologies ensuring proper maintenance and installation Qualifications for Technical Project ManagerMaster's degree in Project Management or related technical field required Professional Project Management Certification from accredited institution preferred Demonstrated understanding of Project Management processes, strategies and methods Experience mentoring, coaching and developing rising talent in the technology department Excellent time management and organizational skills and experience establishing guidelines in these areas for others Strong sense of personal accountability regarding decision-making and supervising department teams Experience working in a high-level collaborative environment and promoting collaborative teamwork  Managerial experience applying analytical thinking and problem-solving skills Ability to predict challenges and seek to proactively head-off obstacles Conclusion  A Technical Project Manager is required to have a high level of technical expertise as well as good organization, leadership and communication skills. Any other lead role on a project who is involved in managing a small size team by leading and directing an area of a project can play the role of a Technical Project Manager. Responsibilities of a Technical Project Manager include developing a project plan, developing a project schedule, defining clear roles and responsibilities for all team members, detailed research and evaluation of hardware and software technology options for every project, updating and maintaining all technologies installed on production, for proper maintenance and installation, etc. The minimum educational qualification of a Technical Project Manager should be a degree in science or computer science or any equivalent Global degree or an MBA. A professional who is PMP or PMI-ACP certified will be the icing on the cake. 
9318
What is a Technical Project Manager?

Many experienced professionals would like to start... Read More

How to Project Schedule in Project Management

In project management, project scheduling encompasses listing activities, defining milestones and scheduling deliverables for delivery. This indicates that every project schedule must include a planned start date and planned finish date, estimated resources assigned to each activity and estimated duration of each activity. An effective project schedule is a very critical component of a successful project.The main purpose of project schedule is to deliver the project scope over a fixed period of time (fixed start and fixed end).What is Project Schedule in Project Management?Project scheduling is fundamental for planning and control in project management. All the work that is necessary to complete the deliverables is all accounted for in the project schedule. A project schedule indicates what activities are needed to be performed on each activity, in what sequence, which resources would be performing these activities, estimated duration to complete these activities, the estimated cost of each activity, etc. It also defines the human resources and physical resources needed to complete the activities. The schedule also includes all associated costs as outlined in the project budget.  The project schedule is often used along with a work breakdown structure (WBS) as it defines the scope of the project. The WBS must be created first as it helps to create the project schedule. Hence if there is any change to be carried out in the project schedule, first make changes in the WBS and then make corresponding changes in the project schedule. The project schedule should be updated regularly to gain a better understanding of the project's status. Clearly, the project schedule is an essential tool to deliver a project on time and within budget. Project schedules are created and tracked with project scheduling software, which has key features that allow project managers to monitor the progress of tasks, resources and costs in real time. They can also assign work, link dependent tasks, view dashboards, allocate resources and more. Work Breakdown Structure (WBS) This is how a work breakdown structure can be represented.In project management, WBS is a technique used for completing a complex or a larger project by making it more manageable. Work Breakdown Structure (WBS) is a hierarchical decomposition of the required scope of work needed to achieve project objectives and create the required deliverables. It defines the total scope of work required to complete the project. The deliverables and their component sub-deliverables are represented on the WBS in levels of descending order. Work defined at the lowest level of the WBS for which cost and duration are estimated and managed is called a Work Package. It must describe a deliverable that can be adequately scheduled, budgeted and assigned to an individual person or group. An important distinction to be made here is that the ‘work’ referred to in a WBS is actually the product or deliverable resulting from an individual work package and not necessarily always the work itself. The Project Management Institute (PMI) defines WBS as  A deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables Each WBS level represents a new and increasingly detailed definition of work needed to complete the project.  A WBS structure must be constructed in a way that each new level in the hierarchy includes all the work needed, to complete its parent task. This means that every parent task element must have more than one child task within it to consider the parent task element complete. How to create a work breakdown structure?Before you create a work breakdown structure, it's essential to first assess the project scope by talking to all stakeholders and key team members involved. The final product to be delivered is defined at the top level (level 0). Level 0 is then decomposed to identify all the major deliverables that are required to produce the final product. Each level of the WBS decomposes the work further into more and more layers until the work package is at a level that can be assigned, estimated for cost and duration and tracked individually. The goal is to eventually roll up each work package into the level above within the WBS hierarchy to gain overall time and budget requirements. The work package is the smallest segment and includes the to-do activities, so you can apply duration and estimated cost. Level of decomposition is based on specific project needs and the level of granularity that is needed to manage the project effectively.  Here's an example of work breakdown structure. Each work package is further decomposed into the activities or tasks that are required to complete a work package. Activity names are usually stated as a verb and noun, such as “Make Lunch.”  The difference between an activity and a work package is that a work package has a specific product or outcome - or in project management terms - a deliverable - that contributes to the project, whereas an activity on its own does not produce a finished item or outcome that helps to fulfil the objective of the project.What’s Included in a Project Schedule? The entire WBS has to be transferred to the Project Schedule. During Planning: Project calendar, Project start date, Project end date, Activity list, Activity start date, Activity finish date, Activity dependencies, Work Packages, Activity duration, Estimated cost of each activity, Resources assigned to each activity. During Execution: Actual duration that is actual completion percentages will be updated by the project manager. Reports such as Earned Value Management, Resource Availability, and many other reports can be used for project tracking and control. How to Make a Project Schedule? Many professionals, while creating a project schedule, use a project schedule template from organizational repositories. A project schedule is not just a standard timetable that works for every project. There are different project scheduling techniques and project management tools involved in the scheduling process. Also, every project has different resources, timetables, scope considerations and other unique variables that must be considered in the schedule management plan. Project management software can be integrated into other project management tools, such as Gantt charts, dashboards and reports to monitor the progress of your project. Project scheduling occurs during the planning phase of the project life cycle.  After creating the project schedule plan for your project, set the project start and project end dates of your project. Follow these steps to create a project schedule of your own. Define activities from the WBS after decomposition of work packages: Scope statement should be made available during the initial planning. It contains project description, deliverables, acceptance criteria of each deliverable, in-scope and out-of-scope, and any assumptions and constraints of your project. WBS is created from this scope statement. Be thorough when putting an activity list together, you should not, and you don’t want to leave anything out. By using a Work Breakdown Structure (WBS) you can organize these activities and lay them out in order of completion.  Figure out task dependencies and then sequence activities: Activities are the small jobs that lead to the final deliverable and it’s crucial to map out the sequence of those tasks before diving into them. Most of the times an activity will be dependent on another activity to start or finish. You don’t want to get halfway through an activity before you realize you can’t complete it due to unclear objectives.  Estimate the realistic resources for each activity using each resource availability. Estimate the realistic duration of each activity. Build project schedule: The critical path is a method for scheduling activities in a project to find those which are critical to completion of the project on time. This will allow you to make choices about activities that can be ignored if time and costs become constraints.  Monitor and control project schedules throughout the project life cycle.Which Are the Project Estimating Techniques?Estimating the duration of project activities as realistically as possible is a key to creating a realistic schedule. There are various project estimating techniques known which are very widely used by project managers. Analogous Estimating: In this technique, project managers interview their team and other stakeholders to get their perspective on how long certain tasks can take. This technique relies on actual duration of previous, similar projects as the basis for estimating the duration of the current project, done in early phases of the project when cost of estimation is low. E.g. duration, budget, size, weight and complexity as the basis for estimating the same parameter or measure for a future project. Parametric Estimating: This technique uses an algorithm or a mathematical model, to calculate cost or duration based on historical data and project parameters, done in later phases of the project when cost of estimation is high. E.g. duration on a design project is estimated by the number of drawings multiplied by the number of labor hours per drawing. Three-Point Estimating (Triangular Distribution): In this technique most likely (tM) –based on the duration of the activity, given the resources likely to be assigned their productivity, realistic expectations of availability for the activity, dependencies on other participants and interruptions, optimistic (tO) – based on analysis of the best-case scenario for the activity and pessimistic (tP) – based on analysis of the worst-case scenario for the activity are determined. Depending on the assumed distribution of values within the range of the three estimates, the expected duration, tE, can be calculated as : tE = (tO + tM + tP) / 3 Another technique which is very widely used uses the same three-point estimates of each activity, and is called Program Evaluation and Review Technique (PERT). It uses Beta Distribution. Which Are the Project Scheduling Techniques?Project managers can make use of project scheduling techniques to increase the accuracy of their time estimates to minimize scheduling risks. Some of the commonly used project scheduling techniques are: Critical Path Method (CPM): The critical path method (CPM) is a technique that calculates the Critical Path which is the sequence of activities that represents the longest path through a project, and determines the shortest possible project duration (how quickly?). The longest path has the least total float, usually zero.  Other commonly used project scheduling techniques, schedule compression such as schedule crashing and fast tracking, can reduce the schedule duration without impacting the project scope. But also note there would be risks and costs involved in schedule compression techniques which need to be carefully managed. Simulation, resource-leveling and resource-smoothing are other tools that can help with project scheduling. How to Manage and Maintain Your Project Schedule During Execution Once you’ve got every piece of your schedule together, the last thing you want to do is manually create a document to keep a track of activities and update the status of the project completion.What Are Project Scheduling Tools?Project scheduling tools are used to help managers organize and execute their project’s tasks and resources within a given budget. Software offerings range from rudimentary to sophisticated and provide users with a wide spectrum of features that facilitate the scheduling of their project.There are many project scheduling tools available in the market such as MS Project, Primavera, Open Project, Project Server, etc.  which can be useful for simple as well as complex or large projects. Best Practices for the Project Scheduling ProcessEvery project manager must use a project scheduling tool to track projects, estimate realistically, consider 6:30 hours per day for creating a schedule, involve project team members in estimation after they come on board etc. Project Schedule vs Project PlanA Project schedule is a Timeline. It tells you when each activity should start and when it should end, which resources are working on the activities, duration of each activity, dependencies of each activity, estimated cost of each activity, etc. It is not a plan. A Project Plan is an approach which tells how you are going to manage your project, how you are going to re-plan, how you are going to execute, how you are going to monitor and control and how you are going to close the project.  Conclusion: Project scheduling is fundamental for planning and control in project management.  The main purpose of project schedule is to deliver the project scope over a period of fixed time (fixed start and fixed end). It is an essential tool to deliver a project on time and within budget. The project schedule is often used along with a work breakdown structure (WBS) as it defines the scope of the project. WBS must be created first as it helps to create project schedule. Follow these steps to create a project schedule of your own: Define activities from the WBS after decomposition of work packages  Figure out task dependencies and then sequence activities  Estimate realistic resources for each activity using each resource availability Estimate realistic duration of each activity Build project schedule and note the critical path(s) Monitor and control project schedule throughout the project life cycle. Various project scheduling tools can be used to create and track project schedules such as MS Project, Primavera, Open Project, Project Server, etc. These tools are full of features and functionality that a project manager can use to make effective schedules and lead projects to success. 
7358
How to Project Schedule in Project Management

In project management, project scheduling encompas... Read More

Best Project Management Certifications in 2021

While nothing can replace industry work experience, there is no doubt that a credible certification can open up new opportunities and elevate your current profile. This is true for any area of work and more so in the project management field.With projects getting more complex, pan global and resource intensive, organizations look to hire project managers who come with solid expertise and a recognised certification to back their knowledge and skill.With so many project management credentials to choose from, which one would suit you best in terms of the knowledge and opportunities you will gain? Here is a ready compilation of the best Project Management Certifications for 2021, to help you to make an informed decision.PMP® Certification TrainingCAPM® Certification TrainingPMI-RMP® Certification TrainingPRINCE2® Foundation and Practitioner Certification TrainingProgram Management Professional (PgMP)® Certification TrainingPMI-ACP® Certification Training1. Project Management Professional (PMP)®Arguably the most well-known credential in the Project Management space, the PMP is globally recognized as the gold standard in project management. Offered by the Project Management Institute (PMI)®, the PMP gives you the bandwidth to work in any industry, using any methodology and working on a variety of situations.This certification is a litmus test of your project management knowledge and skills in managing the project "triple constraints", that is time, cost, and scope. And with its new rollout, the PMP helps holders grow and develop diverse project management skills to suit the fast-changing markets of today and beyond.PMP DemandThe reason why PMP is so well received is because the skills one learns during the PMP certification journey can be applied across sectors, geographies and industries including IT, government sectors, telecommunications, manufacturing, banking and more.It allows certified professionals to maximise value, enhance bottom line margins and prove that they can drive business results.PMP continues to remain one among the best Project Management Certifications for 2021.Benefits of getting PMP certifiedValidate your commitment to continued excellence and qualityDemonstrate your proficiency in project managementGrow your career in project management with confidenceManage projects across sectors and industriesGet yourself hired by the bestEarn salaries that are up to 58% higher than those who do not hold the certificationEarn salaries up to $145,000Top companies that hire PMP professionalsExxon MobileAppleSAICEXELONWhere to take training for certification: Aspirants must undertake the training from an Authorized Training Provider of PMI®.Who should take the training for certification:Mid-Level, Senior Project ManagersProject CoordinatorsProject AnalystsProject LeadersProduct ManagersProgram ManagersProject SponsorsTeam LeadersAnyone interesting in building project management skillsEligibility for PMP examTo be eligible for the PMP® exam, you must fulfill the following criteriaEDUCATIONAL BACKGROUNDSecondary Degree (high school diploma, associate’s degree or global equivalent), ORFour-year Degree (bachelor’s degree or global equivalent), ORBachelor's or Post-Graduate degree from a GAC accredited program (bachelor’s degree or master's or global equivalent).PROJECT MANAGEMENT EXPERIENCEMinimum five years/60 months unique non-overlapping professional project management experience, ORMinimum three years/36 months unique non-overlapping professional project management experience, ORMinimum two years/24 months unique non-overlapping professional project management experience.PROJECT MANAGEMENT EDUCATION35 contact hours of formal education, unless you are an active CAPM holder.Exam FormatThe latest (2021) PMP® certification exam pattern is as follows:No of questions: 180 multiple-choice, multiple responses, matching, hotspot and limited fill-in-the-blank.Time: 230 minutesDifficulty level: The questions are populated as per the difficulty level. The questions are randomized so that no two candidates will get similar questions. The easier the question, the higher the passing score determinant and the higher or tougher the question, the easier the passing score. Duration to get certified: After completing your 35 hours of PMP workshop training, you need to rigorously prepare for the exam. Experts suggest dedicating several weeks to studying for the exam to ensure thorough preparation. Your web-based exam results will be visible to you immediately upon completion of the exam.Course fee for certification: In India: INR 14999, America: USD 999, Canada: CAD 1399Application fee: For PMI membership: USD $ 129 plus USD $10 for application fee.Exam fee for certification:In IndiaMember: ₹23,459.00 Non-member: ₹42,863.00In US Member: $405Non-member: $555Retake fee for certificationMember: $275Non-member:$3752. CAPM®: Certified Associate in Project Management Yet another offering from the PMI, the CAPM is a foundational credential that reflects the holder’s expertise in defining and managing new age project management tools and techniques. Based on the PMBOK® Guide-Sixth Edition, the CAPM will help you stand out among non-certified project managers and showcase your proficiency in implementing global project management best practices.  CAPM Demand: The CAPM certifies the holder as being adept in project management practices. An organization having a pool of CAPM qualified professionals has a good reputation and standing in the market. Owing to the benefits that they bring in, CAPM practitioners are much in demand.Benefits of getting CAPM certifiedLearn the right skills in project managementGain insights into project executing, monitoring, controlling and managementBe thorough in estimating project activity costsAchieve quality management and quality assurance at every stageMaster global project management best practicesOpen yourself to new opportunities and lucrative job offersEnhance your market credibility  Gain 23 contact hours/PDUsBe part of the PMI network and gain several benefitsEarn average salaries from $93,500 to $111,500Top companies that hire CAPM professionalsKaiser PermanateAecom CorporationSAP AmericaBooz, Allen, HamiltonInternational Business Machines (IBM) CorpWhere to take training for certification: Aspirants must train from an Authorized Training Partner (ATP) of PMI.Who should take the training for certificationAssociate Project ManagersProject ManagersIT Project ManagersProject CoordinatorsProject Analysts, Project LeadersSenior Project ManagersTeam LeadersProduct ManagersProgram ManagersProject SponsorsProject Team MembersEligibilitySecondary degree (high school diploma, associate’s degree or the global equivalent)23 hours of project management education completed by the time you sit for the examExam FormatNo of questions: 150 questions Time: 3 hoursDifficulty level: Moderate but requires thorough knowledge of project management principlesDuration to get certified: After completing your 23 hours of CAPM workshop training, you need to dedicate around 45-60 hours to ensure complete preparation for the exam. Your web-based exam results will be visible to you immediately upon completion of the exam. Course fee for certification: INR 8999, USD 799Application fee for certification: For PMI membership: USD $ 129 plus USD $10 for application fee.Exam fee for certification:In IndiaMember: ₹17,377.00Non-member: ₹23,169.00In U.S.Member: $435Non-member: $4953. PMI-RMP®: Project Management Institute-Risk Management ProfessionalThe pandemic exposed many vulnerabilities that organizations had not been prepared for. When faced with unprecedented risks, organizations need specialists who can identify and assess project risks, mitigate threats and take advantage of opportunities. The PMI-RMP course and certification prepares professionals to perform this role and successfully steer projects in complex environments.PMI-RMP Demand: According to the 2015 Pulse of the Profession® by PMI, “Eighty-three percent of organizations that are high performers in project management practice risk management frequently while just 49 percent of low performers do so”. This shows the importance of risk management and the emphasis organizations place on qualified risk managers.Benefits of getting PMI-RMP certifiedApply risk management practices for greater competitive advantageIdentify and measure risks in project development and implementationQuantify and create risk response strategies to deliver products that meet stakeholder expectationsUse a proactive and focused approach to preventing problems, rather than dealing with them once they occurIncrease your visibility within the companyAim for greater career growthEarn salaries upto $115,931Top companies that hire PMI-RMP professionalsWhere to take training for certification: Aspirants must train from an Authorized Training Partner (ATP) of PMI.Who should take the training for certificationRisk ManagersRisk Management ProfessionalsProject ManagersProject SponsorsProgram ManagersProject EngineersProject CoordinatorsPlanning ManagersPlanning EngineersProject Cost Control EngineersQuantity SurveyorsCivil EngineersIT Project ManagersProduct ManagersProject AnalystsBusiness AnalystsProject LeadersProject Co-ordinatorsTeam LeadersTeam MembersEligibilityTo apply for the PMI-RMP® Credential, you need to possess a:Secondary degree (high school diploma, associate’s degree, or the global equivalent)4,500 hours of project risk management experience40 hours of project risk management educationORFour-year degree (bachelor’s degree or the global equivalent)3,000 hours of project risk management experience30 hours of project risk management educationExam FormatNo of questions: 170 questions Type: Multiple ChoiceTime: 3.5 hoursDuration to get certifiedApplication fee: For PMI membership: USD $ 129 plus USD $10 for application fee.Course fee for certification: INR12999, USD 999Exam fee for certificationIn U.S.Member: $520Non-member: $670Retake fee for certificationMember: $335Non-member: $4354. PRINCE2® Foundation/PRINCE2 PractitionerThe PRINCE2 (PRojects IN Controlled Environments) Foundation and Practitioner credentials are sought-after offerings from AXELOS. There are a number of credentials offered under PRINCE2 that make it suitable for a wider audience. Axelos keeps the PRINCE2 curriculum regularly updated with the latest industry advances, which makes it suitable for new age project management and intensive, demanding projects.  PRINCE2 Demand: PRINCE2 extends its applicability across industries and sectors. This makes it very popular in the market as it is a one size fits all model. Although PRINCE2 was founded in the UK, it has now firmly established its presence in industries across the world. According to a report in LinkedIn, PRINCE2 is the most popular project management methodology. A professional adept at PRINCE2 and holding the credential is highly valuable and sought after by organizations implementing PRINCE2 for their projects.  Benefits of getting PRINCE2 certifiedGuide projects in their entiretyTailor PRINCE2 to suit the needs of projects and organizationsValidate your commitment to continued excellence and quality Master and demonstrate your proficiency of the PRINCE2® framework Gain project management best practices and grow your career with confidence Work across projects in diverse sectors and industriesShow your ability to work in challenging work environments Command higher salaries (upto $99,012 average) than your non-certified peers Top companies that hire PRINCE2 professionalsShellBPTranspower New ZealandIBMHPAquasoftGetronicsSiemensWhere to take training for certification: Aspirants must undertake training from a Certified Partner of AXELOS and an accredited training organization (ATO) with PeopleCert®.Who should take the training for certification?Project ManagersProject CoordinatorsProject AnalystsProject LeadersProduct ManagersProgram ManagersProject SponsorsTeam LeadersSenior Responsible OwnersProduct Delivery ManagersBusiness Change AnalystsProject and Programme Office PersonnelOperational Line ManagerAnyone who wishes to build up knowledge in project management EligibilityThere are no eligibility requirements for the PRINCE2® Foundation certification exam. To qualify for the PRINCE2 Practitioner exam, you must have at least one of the following certifications: PRINCE2® Foundation or higher (applicable only to certificates obtained after 1 January 2009) Project Management Professional (PMP)® Certified Associate in Project Management (CAPM)® IPMA Level A® (Certified Projects Director) IPMA Level B® (Certified Senior Project Manager) IPMA Level C® (Certified Project Manager) IPMA Level D® (Certified Project Management Associate) Project Management Qualification (PMQ) Project Professional Qualification (PPQ) Exam FormatFoundation ExamDuration: 60 minutes (1 hour) Questions: 60 Multiple choice questions Pass mark: 33 out of 60 available, or 55% Use of textbook: No, it’s a closed book examPractitioner Exam Duration: 150 minutes (2.5 hrs) Questions: 68 Objective type questions Pass mark: 38 out of 68 available, or 55% Use of textbook: Yes, but only the official PRINCE2® manual is permitted. Duration to get certifiedYou will need to attend 32-hours of PRINCE2® Foundation and Practitioner training from an ATO of AXELOS and PeopleCert®, following which you will be required to take the exams to demonstrate your knowledge of PRINCE2 and get certified. The results of your tests are issued within 2 business days from the date of your exam.  Course fee for certification: USD 1999Exam fee for certification: Included in course fee5. PgMP®: Program Management Professional (PgMP)® Certification TrainingAnother project management from the PMI, this credential is more advanced than the PMP and certifies the holder’s ability to manage complex projects that cover functions, organizations, cultures and geographies. The credential mandates holders to be proficient in the six prime focus areas: Governance, Prioritization, Escalation, Resource Management, Benefits Realization, and Stakeholder Management.PgMP Demand: Credentials from the PMI are known for their rigorous standards and testing, which is why they are well accepted in industries across sectors. PgMP holders are better able to promote integration and coordination of multiple projects for the overall benefit of the program. According to PMI’s 2015 Pulse of the Profession® report, an organization’s projects are far more successful with program management than without it — 76 percent compared to 54 percent. This further compounds the demand for PgMP professionals. Benefits of getting PgMP certifiedGet in-depth knowledge of tools and techniques to handle complex multiple related projectsUnderstand Program Lifecycle and its processes, competencies, tools and techniques with practical sample templatesLearn to implement large-scale programs to align with business strategyOpen yourself to lucrative job opportunities and leadership rolesWork in projects across geographiesEarn high salaries, upto $139,000 on averageTop companies that hire PgMP professionalsAmazonGoogleMicrosoftCognizantCapgeminiDeloitteJP Morgan ChaseErnst & YoungWhere to take training for certification: Aspirants must train from an Authorized Training Provider of PMI®Who should take the training for certificationTeam LeadsSponsorsProject DirectorsProgram ManagersPortfolio Managers  Project Management Office (PMO) HeadsEligibilityA Four-year Degree (Bachelor's or Global equivalent), with at least four years of Project Management experience and four years of Program Management experience.ORA Secondary Diploma (High school or Global equivalent), with at least four years of Project Management experience and seven years of Program Management experience. Exam FormatNo of questions: 170 multiple-choice, of which 20 are considered pretest questions which are not scored.Question type: Most questions are scenario based and test a professional's understanding and clarity of thoughts on different Program Management concepts.Time: 4 hoursDifficulty level: DifficultDuration to get certified: You have to complete your 24 hours of training from an Authorized Training Partner (ATP) of PMI. Make a study plan and stick to it religiously. The PgMP is considered to be more difficult than the PMP and requires a fair bit of preparation. Once you pass the 4-hour exam you will be PgMP certified.  Course fee for certification: INR 13,999; USD 1199Application fee for certification: For PMI membership: USD $ 129 plus USD $10 for application fee.Exam fee for certificationIn IndiaMember: ₹46,338.00Non-member: ₹77,230.00In U.S.Member: $800Non-member: $1000Retake fee for certificationMember: $600Non-member: $8006. PMI-ACPPMI-ACP Demand: Agile is a fairly new concept in the context of product development. Though organizations reap immense benefits by adopting Agile, the road to transformation can often turn out to be expensive if not well executed. PMI-ACP professionals are therefore in huge demand as they can bring in project management best practices in Agile environments and ensure project success.  Benefits of getting PMI-ACP certifiedThe shortage of Project Managers has increased job opportunities in the Agile environmentYou will qualify for Agile jobs with expertise in Agile methods like Scrum, FDD, Kanban, etc. which are in demand in the industryEarn salaries in the range of $108,000 on an averageEquips you with knowledge of various Agile methodsMakes you more marketableTop companies that hire PMI-ACP professionalsStandard CharteredOracleIBMVMWareSource: IndeedWhere to take training for certification: Aspirants must train from an Authorized Training Provider of PMI® Who should take the training for certification?Project ManagersProject PlannersQuality Assurance StaffDevelopers/ProgrammersDesigners, TestersProject ControllersProduct OwnersScrum MastersScrum Team MembersEligibilityTo apply for the PMI-ACP®, candidates must meet the following requirements:1. General Project Experience2000 hours of working on project teams within the last 5 years or having an active PMP®/PgMP® credential2. Agile Project Experience1500 hours of working on Agile Project Teams or with Agile Methodologies, in addition to “General Project Experience” above;3. Training in Agile Practices21 contact hours earned in Agile PracticesExam FormatNo of questions: 120 MCQ, of which 20 are pre-testDuration: 3 hoursDuration to get certified: Once you complete the course, you need to schedule the exam date. Exam applications have to be submitted and approved by PMI. Online applications m ay take upto five business days to get processed. Once your application is processed, you can schedule your exam date, and on passing receive the PMI-ACP credential.Course fee for certification: INR 10,999, USD 1099Application fee for certification: For PMI membership: USD $ 129 plus USD $10 for application fee.Exam fee for certificationFor members: $435Non-members: $495Retake fee for certificationMembers: $150Non-members: $200SummaryProject Management is among the most sought after job roles, not only in the tech industry but any industry that executes and manages projects. By 2027, 88 million individuals will need to be skilled in project management-oriented roles. This makes it among the hottest job trends in the coming years, and a credential will go a long way in helping you capitalise on this trend.
2480
Best Project Management Certifications in 2021

While nothing can replace industry work experience... Read More