Determining the project scope means defining the specific boundaries, or extent, of the
project. For example, a statement that, payroll is not being produced accurately is very
general, compared with the statement overtime pay is not being calculated correctly for
production workers on the second shift at the Yorktown plant. Similarly, the statement,
the project scope is to modify the accounts receivable system, is not as specific as the
statement, the project scope is to allow customers to inquire online about account
balances and recent transactions.
Some analysts find it helpful to define project scope by creating a list with sections called Must Do, Should Do, Could Do, and Won’t Do. This list can be
reviewed later, during the systems analysis phase, when the systems requirements
document is developed.
Projects with very general scope definitions are at risk of expanding gradually,
without specific authorization, in a process called project creep. To avoid this problem,
you should define project scope as clearly as possible. You might want to use a graphical model that shows the systems, people, and business processes that will be affected.
The scope of the project also establishes the boundaries of the preliminary investigation itself. A systems analyst should limit the focus to the problem at hand and avoid
unnecessary expenditure of time and money.
Along with defining the scope of the project, you need to identify any constraints on
the system. A constraint is a requirement or condition that the system must satisfy or an
outcome that the system must achieve. A constraint can involve hardware, software, time,
policy, law, or cost. System constraints also define project scope. For example, if the system must operate with existing hardware, that is a constraint that affects potential solutions. Other examples of constraints are: The order entry system must accept input from
15 remote sites; the human resources information system must produce statistics on hiring practices; and the new Web site must be operational by March 1. When examining
constraints, you should identify their characteristics.
PRESENT VERSUS FUTURE Is the constraint something that must be met as soon as
the system is developed or modified, or is the constraint necessary at some future time?
INTERNAL VERSUS EXTERNAL Is the constraint due to a requirement within the
organization or does some external force, such as government regulation, impose it?
MANDATORY VERSUS DESIRABLE Is the constraint mandatory? Is it absolutely essential to meet the constraint, or is it merely desirable?
Figure 2-20 shows five examples of constraints. Notice that each constraint has
three characteristics, which are indicated by its position in the figure and by the symbol that represents the constraint. The constraint in Example A is present, external,
and mandatory. The constraint in Example B is future, external, and mandatory. The
constraint in Example C is present, internal, and desirable. The constraint in Example
D is present, internal, and mandatory. The constraint in Example E is future, internal,
and desirable.
Regardless of the type, all constraints should be identified as early as possible to
avoid future problems and surprises. A clear definition of project scope and constraints avoids misunderstandings that arise when managers assume that the system
will have a certain feature or support for a project, but later find that the feature is
not included.