13
Chapter 2
Project Scoping
If project content is allowed to change freely, the rate of change will
eventually exceed the rate of progress.
—
Unknown
Developing the scope of a project is the early work where we decide what
boundaries we will set to limit the work of the project. Those boundaries (in
a network vulnerability assessment project) are defined by:
What physical limits will exist?
What parts of the organization will be included?
How much (if not all) of the network will be reviewed?
How many people will be consulted?
How many people will be working on the project?
Most failed projects come to grief because the scope of the project was
poorly defined to begin with, or because the scope was not managed well
and was allowed to ”creep” until it was out of control. If we are going to
manage the project well, then setting the scope for the project is key to its
success.
Setting the scope for a network vulnerability assessment (NVA) project
means that we will start with a Project Overview Statement and then develop
the Project Scope Document. The Project Scope Document consists of elements
of the Project Overview Statement, a Task List, and the documents that set
limits on the Task List. The Task List and the documents that set limits on the
tasks will form the basis of our project plan for the NVA.
This chapter presents a general overview of Project Overview Statements
and the documents that go together to make up the Project Scope Document,
and then discusses how to define the scope (using those two documents) for
a network vulnerability analysis. (A blank Project Overview Statement is shown
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.