Summary of Chapter 2 - PMBoK:
Projects and project management are broader than managing day-to-day activities of the project. The second chapter of the PMBoK covers the key elements of project management, including the following: 12345-
Project phases and project life cycle
Key general management skills
1. Project phases and project life cycle
Because projects involve uncertainty, organizations divide them into project phases to improve management control and make links with the other ongoing operations. Collectively the project phases are known as the project life cycle.
Each project phase consists of one or more deliverables and ends when all of these are completed. At the end of each phase (phase exit/ stage gate/ kill point), both the key deliverables and the project performance to date are reviewed to 1) decide to move to the next phase or not and 2) detect and correct errors cost effectively.
The project life cycle defines the beginning and the end of the project. It determines which transitional actions are included and which are not (feasibility study, etc.). Since the project is divided into phases, deliverables from a phase has to be approved in order to move forward to the next phase. However, a later phase might start before the last phase has been finished if the risk is deemed acceptable. This overlap of phases is called fast tracking. The project life cycle defines: 1) The technical work in each phase (who works in which phase) and 2) who is involved in each phase. This can be very general or very detailed (project management methodologies). Project life-cycle differs from product life-cycle. There can be many projects defined within the product life-cycle.
Common characteristics of project life –cycles are:
1) Costs are low at first, get higher towards the end, and then drop rapidly. 2) Risk and uncertainty are high at first, and hence the probability of successfully completing the project is low at the beginning. This will change as the project proceeds to the end. 3) Changing the outcome is easier at first and gets harder towards the end because of the costs. Note: section 2.1.3 – pp 13 – 15 contains a list of phases within a project life-cycle. These cannot be summarized and should therefore be read from the book itself.
2. Project stakeholders
Project stakeholders are those individuals or organizations that: 1- Are actively involved in the projects
2- Their interests are effected by the project
3- Have influence over the project
Identifying the stakeholders is difficult but key stakeholders on every project are: -
Customer (may have many layers- may be the user or an entity that buys the product and doesn’t use it directly)
In addition to these, there are many names and categories of project stakeholders (see page 16, last paragraph) and some of them may even overlap. Managing the expectations of the stakeholders is difficult as they may come into conflict. In general, the conflicts should be resolved in the favour of the customer without disregarding the needs of the stakeholders. This can be one of the major challenges in project management.
3. Organizational influences
Projects are typically part of an organization larger than the project, therefor some elements in the organization can influence the project itself.
Organizational systems: Organizations are either project-based or nonproject-based. Project based organizations either derive their revenue primarily by performing projects for others, or have adopted management by projects. Project-based companies tend to have management systems in place to facilitate project management. Nonproject-based organizations, however, often lack management systems which makes project management more difficult. The project management team should be aware of how the organization’s...
Please join StudyMode to read the full document