Initiating Planning Implementing Controlling Closing Develop project charter Develop project plans Direct project work

Size: px
Start display at page:

Download "Initiating Planning Implementing Controlling Closing Develop project charter Develop project plans Direct project work"

Transcription

1 and Introduction is a high level guide to project, very similar in structure to the Project Management Institute s (PMI ) Guide to the Project Management Body of Knowledge (PMBoK ). It is important to note that is not a standard against which organisations can be accredited. It is purely a guide to good practice. The aim of this article is to demonstrate that all the good practice defined in is also covered by. Therefore, any organisation that implements can do so in a way that is compliant. Inevitably, there are differences. Some key ones are described below: is specific to project, whereas also covers programmes and portfolios. An obvious consequence of this is that includes change and benefits. These are excluded from. is hierarchical whereas has a flat structure. This means that when describing equivalences, sometimes refers to top level functions, sometimes secondary level functions and sometimes steps in a functional procedure (the latter indicated by italics in the detailed comparisons). adopts the ISO10006 approach to quality. As a result there is no separate section for quality which is seen as being inherent in all other functions. When comparing the two documents, sections 3.6, 3.9 and 4 of are the most relevant. Section 3.6 addresses project governance and this is mainly addressed by the processes. Section 3.9 makes reference to the competency groupings defined by the International Competency Baseline (ICB) published by the International Project Management Association (IPMA) although it does state that these are one example of how competencies can be categorised. In the competency framework, competencies are categorised as delivery, inter-personal and process. Section 4 describes process groups and subject areas as shown in the table below. The subject area titles are annotated with the main equivalent functions or processes. The following sections describe these equivalences in more detail.

2 Subject groups Integration (Life cycle processes) Stakeholder (Stakeholder ) Scope (Scope ) Resource (Organisation and resource ) Time (Schedule ) Cost (Financial ) Risk (Risk ) Quality (Inherent in all functions) Procurement (Resource ) Communication (Stakeholder and information ) Develop project charter Identify stakeholders Establish Develop project plans Define scope Create work breakdown structure Define activities Estimate resources Define project organisation Sequence activities Estimate activity durations Develop schedule Estimate costs Develop budget Identify risks Assess risks Plan quality Plan procurements Plan communications Direct project work Manage stakeholders Develop Control project work Control changes Control scope Control resources Manage Control schedule Control costs Treat risks Control risks Perform quality assurance Select suppliers Distribute information Perform quality control Administer procurements Manage communications Close project phase or project Collect lessons learned

3 Integration The integration subject group in is, in effect, a set of life cycle processes. Since pretty much all authorities agree on the basic phases of a life cycle, this is the common theme between not only and but also and PRINCE2, not to mention any other set of project or programme processes. Integration Develop project charter Identification process Develop project plans Definition process Direct project work Sponsorship process Delivery process Control project work Control changes Close project phase or project Collect lessons learned Closure process Develop products Manage boundaries process Realise benefits Initiating: The Project Charter is broadly similar in content to a brief in, as are the purposes of Develop project charter and the goals of the identification process. These two processes are pretty much serving the same purpose in the same way. The outputs of Develop project plans are the Project plan and the Project plan. These equate to the delivery plans and plans in, so the two processes are effectively the same. Implementing and The three processes collectively perform the same activities as the first three processes. There is no clear one-to-one correlation but collectively they do the same job. does not explicitly support the creation of stages within the delivery phase although it does recognise the creation of sub-projects and work packages. Therefore, there is no equivalent of the manage boundaries process and reduced versions of Develop project plans and Close project phase or project would be combined instead. As with most guides to project, deems that projects do not manage the realisation of benefits and so this aspect is omitted.

4 Closing: The closing process and Close project phase or project are the same in respect of closing a project. Aspects of are included in s manage boundaries process in respect of stages Collect lessons learned is covered by the review activity in the closure process. Stakeholders The approach to stakeholder is very similar to the corresponding subject group with one difference. includes stakeholder communication within the stakeholder function while has a separate communication subject group. While has a communication function, that addresses the interpersonal skill of personal communication rather than dissemination of information. Furthermore, has a separate information function which overlaps with s stakeholder group. The comparison table therefore combines the stakeholder and communication subject groups from and maps these steps from the procedures for stakeholder and information. Stakeholder and communication Identify stakeholders Identify Plan communications Assess Plan communications Manage stakeholders Distribute information Engage Access and disseminate Manage communications Initiating: Identify stakeholders and the identify step in the stakeholder procedure have the same purpose. The assessment step in s stakeholder procedure is really about planning for stakeholder engagement. However, includes this in Manage stakeholders. covers the preparation of a communications plan in Plan communications rather than as part of stakeholder.

5 Implementing and controlling: Manage stakeholders covers both the assessment of stakeholder interests and the engagement with stakeholders according to the communications plan. In this is covered by the engagement step in the stakeholder procedure Distribute information is covered by the access and distribution step from the information procedure Manage communications is covered in by the engagement step from stakeholder and the access and distribution step from the information procedure. Scope The main difference between scope in and is that excludes the possibility of projects incorporating the realisation of benefits Define scope Create work breakdown structure Define activities Control scope Scope Manage requirements Develop solution Scope Scope Benefits Change Change control Configuration Schedule Define scope is a very broad process. Its outputs are requirements and a scope statement. In this requires the application of two functions. Requirements contains a procedure that captures stakeholder want and needs, and then develops a baseline set of requirements. This baseline is used by solutions development to create a specification (equivalent to a scope statement). In the scope statement is the basis for creating a work breakdown structure and defining the work activities that will achieve the project objectives. In these processes are incorporated within scope and schedule respectively.

6 Implementing: In there are no scope implementation processes but it reasonable to assume that these are covered by Control project work. In the implementation of scope is equally covered by the delivery process and the develop products process, although in scope there is specific reference to an implement solution step. Since recognises that scope may include benefits, the benefits and change functions are also about scope implementation. The Control change process is covered by the change control and configuration function in. Resource The resources subject group in combines the organisation and internally sourced delivery resources. separates these out into two functions. Organisation deals with the organisation of projects, programmes and portfolios while the procurement of internal and external delivery resources is covered by resource. In, the procurement of external resources is covered in the procurement subject group. Resource Establish Organisation Resource Estimate resources Define project organisation Resource scheduling Organisation Stakeholder Develop Leadership Teamwork Control resources Manage Schedule Leadership Teamwork Mobilisation Initiating: The Establish is a very wide ranging process that should be seen as being required throughout the life cycle. It does not chronologically precede the planning processes. The broad goals and application of this process are covered by organisation and resource in.

7 Estimate resources relates to delivery resources and these matters are covered by the resource scheduling function in Define project organisation is most relevant to the organisation but also makes reference to internal delivery resources and stakeholders. It therefore draw on aspects that covers in resource scheduling, organisation and stakeholder. Implementing: The Develop process should enhance team motivation and performance. treats these as interpersonal skills of the manager rather than processes. They are primarily covered by leadership and teamwork but are supported by other skills such as delegation, conflict and influencing Control resources deals with monitoring and reviewing the resource aspect of the project schedule. These areas are covered by the schedule function in Manage has very similar outputs to Develop. These two processes appear to simply represent what needs to be managed at different stages of a team s development cycle (such as Tuckman). They are therefore deemed broadly equivalent to teamwork and leadership in. Closing: In the demobilisation of the project organisation is not covered by a specific closing process for resources. In this is covered by the mobilisation functions (which includes demobilisation). Time The timings in a project schedule depend upon the availability of resources as well as the estimated durations of activities. Therefore, combines these in the schedule section which includes time scheduling and resource scheduling. Time Sequence activities Estimate activity durations Develop schedule Schedule Control schedule Control Time scheduling Resource scheduling Planning

8 Sequence activities is covered by time scheduling with numerous detailed references in the encyclopaedia. Estimating applies to many aspects of a project so deals with it in a generic sense in the planning function. Specific techniques relevant to Estimate activity durations are mentioned in time scheduling and explained in detail in the encyclopaedia. There are many aspects to developing a schedule and while there are references to this throughout, the main coverage is in the time scheduling and resource scheduling functions. The detail of Control schedule is covered by the control function in. This works in close conjunction with the delivery process at the life cycle level. Cost The corresponding section in is called financial because it covers more general issues than just cost, such as investment appraisal and funding. Cost Estimate costs Develop budget Planning Budgeting and cost control Control costs Control Budgeting and cost control In the general principles of estimating are covered in the planning function. These are then developed in specific ways by other functions such as budgeting and cost control. These two functions therefore cover the ground described by Estimate costs and Develop budget. The same logic applies to the process Control costs. This is covered by the functions for control and budgeting and cost control.

9 Risk The risk processes in have a close correlation to the steps in the risk procedure in. The techniques used in these processes are covered by the risk techniques function and in Identify risks Assess risks Treat risks Control risks Risk Identify Assess Plan responses Implement responses Identify risks and Assess risks are equivalent to the identification and assessment steps in the risk procedure. Implementing: The ISO process Treat risks is equivalent to the response planning and implementation steps in the procedure. deems Control risks to be simply a repetition of the risk procedure, i.e. new risks are continually identified and assessed with new responses being planned and implemented. Once implementation plans are incorporated into the general delivery plans, their control is covered by the control function and delivery process. Procurement treats procurement as a component of resource. This includes the procurement of internal resources as well as external (contracted) resources. Procurem ent Plan Select Administer procurements suppliers procurements

10 Procurement Solutions development Procurement Contract The Plan procurements process is primarily covered by the plan, research and tender steps in s procurement procedure. The make or buy decision is made as part of solutions development. Implementing: The Select suppliers process is covered by the tender step in s procurement procedure Administer procurements in is equivalent to contract in.