Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Project Management DP

Introduction

The purpose of the Project Management process is to establish and carry out, in a systematic way, the Tasks of the system development project, which allows complying with the project’s Objectives in the expected quality, time and costs. Many systems fail not because there is no market, but because the cost of creating the system far outstrips any profit. Currently approximately half a million project managers worldwide are responsible for in the region of one million system and software projects each year, which produce products worth USD$600 billion. It is now accepted that many of these projects fail to fulfil acquirers' expectations or fail to deliver the system within budget and on schedule [Jalote02]. Putnam suggests that about one-third of projects have cost and schedule overruns of more than 125% [Putnam97].

Activities

Activity PM 1 - Project Planning

The primary objective of the Project Planning process is to produce and communicate effective and workable project plans. This process determines the scope of the project management and technical activities, identifies process outputs, project tasks and deliverables, establishes schedules for project task conduct, including achievement criteria, and required resources to accomplish project tasks.

Activity PM 2 - Project Plan Execution

The primary objective of the Project Plan Execution process is to implement the actual work tasks of the project in accordance with the project plan.

Activity PM 3 - Project Assessment and Control

The purpose of the Project Assessment and Control process is to determine the status of the project and ensure that the project performs according to plans and schedules, within projected budgets and it satisfies technical objectives. This process includes redirecting the project activities, as appropriate, to correct identified deviations and variations from other project management or technical processes. Redirection may include re-planning as appropriate.

Activity PM 4 - Project Closure

Project Closure typically involves releasing the final deliverables to the acquirer, handing over project documentation to the business, terminating supplier contracts, releasing project resources and communicating project closure to all stakeholders. Often a final step is to undertake a Post Implementation Review (post-mortem) to identify the level of project success and note any lessons learned for future projects.

Navigation Links

Back to the top