What Is a Project?
Things are not always what they seem. — Phaedrus, Roman writer and fabulist
CHAPTER LEARNING OBJECTIVES
After reading this chapter, you will be able to: N Define a project N List a project’s characteristics N Distinguish a project from a program, activity, and task N Understand the three parameters that constrain a project N Know the importance of defining and using a project classification rule N Understand the issues around scope creep, hope creep, effort creep, and feature creep N Be able to explain the project from the perspective of goal and solution clarity or lack of clarity N Understand the characteristics of the complexity/uncertainty domain that define the project
Defining a Project
To put projects into perspective, you need a definition — a common starting point. All too often people call any work they have to do a “project.” Projects actually have a very specific definition. If a set of tasks or work to be done does
Traditional Project Management
not meet the strict definition, then it cannot be called a project. To use the project management techniques presented in this book, you must first have a project. A project is a sequence of unique, complex, and connected activities having one goal or purpose and that must be completed by a specific time, within budget, and according to specification. This definition tells you quite a bit about a project. To appreciate just what constitutes a project take a look at each part of the definition.
Sequence of Activities
A project comprises a number of activities that must be completed in some specified order, or sequence. An activity is a defined chunk of work.
C R O S S-R E F I expand on this informal definition of an activity later in
The sequence of the activities is based on technical requirements, not on management prerogatives. To determine the sequence, it is helpful to think in terms of inputs and outputs.