Location:
PMKI > Organizations
& Governance > Defining Projects and
Programs.
- Project Definition and Typology
- Program Definition and Typology
- Useful External Web-links &
Resources.
Other related sections of the PMKI:
Defining
the nature of a project and its parameters.The definition
of a project used by almost every authority is an
inclusive definition ie; 'a project is a temporary
endeavour undertaken to create a unique product, service
or result' PMBOK(R) Guide. This definition can
apply equally well to genuine projects, other endeavours
(Paul C. Dinsmore 'Everything in business is a project or
project-related') and to processes that are definitely not
projects. Before the true value of projects to an
enterprise can be properly assessed and the
responsibilities of a Project Manager identified, the
definition of "projects" must be tightened so that
endeavours that are not projects are excluded as
effectively as endeavours that are projects are included.
Modifying the definition of a project to distinguish projects from other endeavours suggests a definition along these lines:
Under the enhanced definition proposed in this section, a project can only exist if its stakeholder community agrees. The outcome to be expected from bringing the stakeholder community directly into the project management processes, is to ensure more projects deliver to their full potential to the benefit of their host organizations and the community.
PP: Project Fact or Fiction. Constructing an unambiguous definition the definition of the terms 'project', 'project manager', and 'project management': Project: A temporary organisation established to accomplish an objective, under the leadership of a person (or people) nominated to fulfil the role of project manager. And the reasons why this is important.
Prs: The Entropy at the heart of Project Management. This paper tracks the emergence and convergence of modern project management through to the early part of the 21st century, then maps the rapidly diverging strands that are now encompassed by the concept of ‘project management’. From this basis it seeks to identify the challenges inherent in this increasing entropy, and offer some suggestions for the shape of the profession, associations, and qualifications going forward.
Art: De-Projectising IT Maintenance. Not everything needs to be a project – by de-projectizing maintenance work major improvements in delivery are possible.
Defining the different characteristics, types, and sizes of project and their effect on the skills needed to manage them effectively.
WP: Project Size and Categorization. There are four basic dimensions to every project that affect its management: size, difficulty, uncertainty and complexity.
Blg: Differentiating normal, complex and megaprojects. A look at the additional layers of competency needed to manage complex projects and megaprojects and a suggested framework for classifying these different types of project.
PP:
Scheduling Challenges in Agile & Distributed
Projects. The focus of this paper is to define
the challenge and look at practical options for managing
work efficiently in a wide range of projects where the CPM
paradigm does not apply. To facilitate this, it develops a
classification framework of project characteristics to
help define the potential usefulness of CPM scheduling
across different project types. See pages 5 through 7):
1. Physically constrained – there is only one
viable work sequence - The CPM paradigm is ideal for this
type of project.
2. Practically constrained – management has agreed
the one best work sequence. The CPM paradigm is ideal for
this type of project.
3. Overarching constraints – there is a required
overall sequence of working, with a degree of flexibility
in the way the detailed work is performed to achieve the
overall objectives. The CPM paradigm may be useful at the
high level in a Class 3 project, but has significant
limitations at the detail level.
4. Arbitrary constraints – there is no required
sequence of working (as in Class 1 or 2), but management
has decided to impose a detailed sequence of work as a
matter of choice. The CPM paradigm is imposed for little
or no practical benefit.
Defining the nature of a program and its parameters. A
program is defined as a group of related projects managed
in a coordinated way to obtain benefits and control not
available when managing them individually.
Note: The English and ISO spelling of programme
and the more common spelling program refer
to the same type of entity.
WP: Program Management. Program management focuses on the coordination of a number of related projects over time to deliver benefits that would not be available if the projects were managed separately.
For more on the difference between projects and programs see: Differentiating Programs from Projects
Defining the different characteristics and types of program and their effect on the skills needed to manage them effectively.
WP: Defining Program
Types. This White Paper defines the different
types of programs based on the GAPPS Program Types.
Download
the GAPPS Program Typology.
Blg: Differentiating normal, complex and megaprojects. A look at the additional layers of competency needed to manage complex projects and megaprojects and a suggested framework for classifying these different types of project.
TBA