Page 55 -

3 - PROJECT MANAGEMENT PROCESSES FOR A PROJECT

with experienced project managers and technical leaders on similar projects, or perhaps managers and leaders on
releases of previous versions of a software product undergoing significant modifications. As indicated previously,
an initiating process is typically conducted on each iterative cycle of an adaptive life cycle project.

3.4 Planning Process Group 3

According to Section 3.4 of the PMBOK Guide, the Planning Process Group consists of those processes
®
performed to establish the total scope of the effort, define and refine the objectives, and develop the course of
action required to attain those objectives.

Section 5 of this Software Extension, explains that the scope of a software project, the objectives to be obtained,
and the courses of action to be followed are often adjusted as a software project evolves. More detailed initial
planning is usually accomplished for a predictive life cycle software project than for an adaptive one.

3.5 Executing Process Group

According to Section 3.5 of the PMBOK Guide, results during project execution may require planning updates
®
and rebaselining. Changes may include changes to planned activity durations and changes in resource productivity
and availability based on unanticipated risks, problems, and other issues.

Changes during execution are the norm for most software projects. Uncertainty that results from initial lack
of information is a major source of risks, problems, and other issues for software projects. Replication of existing
software is a simple process compared to replication of physical artifacts; so most software projects are unique
undertakings and are, therefore, learning experiences characterized by uncertainty.

3.6 Monitoring and Controlling Process Group

According to Section 3.6 of the PMBOK Guide, the Monitoring and Controlling Process Group consists of those
®
processes required to track, review, and orchestrate the progress and performance of the project; identify any
areas in which changes to the plan are required; and initiate the corresponding changes.

Depending on the project life cycle used, monitoring of software projects can vary from traditional techniques
(i.e., preplanned milestones, earned value tracking, and technical performance measurement) to reliance on
frequent demonstrations of working software. Controlling may include rescoping of project and/or product or
changes to tools and techniques.

3.7 Closing Process Group

®
According to the PMBOK Guide, the techniques presented in the Closing Process Group are equally applicable
to software projects. The demonstration of working software is an important element of closing a software project

©2013 Project Management Institute. Software Extension to the PMBOK Guide Fifth Edition 43
®