Schedule Analysis Activities

Preparing for Analysis › Schedule Analysis Activities

More information:

Schedule Analysis Activities

The project manager and the analysis team establish a project schedule that is based on the project scope. The task structure and management of the project depends on:

Development life cycle route chosen
Variations in the life-cycle route tasks or checkpoints, as dictated by the project objectives and scope
Whether the project is intended to develop a stand-alone system or systems that are part of a set of systems within a Business Systems Architecture
Whether Rapid Application Prototyping (RAP) techniques are used
Whether current systems and data are analyzed
Whether packaged solutions are evaluated
Whether the distribution of procedures or data is among the technical possibilities

It is important to distinguish between technical facilities that are currently installed and those that is implemented in time for the transition of the systems to be developed. For example, this constrain the choice of distributed processing and use of client/server techniques. Where a system is to use new technical facilities, the project schedule allow for coordination with the necessary technical development work.

Review the analysis techniques to be used and develop a schedule using either automated or manual techniques.

Decide about the alternative courses of action available during analysis. Your choices affect the content of the task list and the project duration. These choices include:

What facilitated sessions and more interviews are required for information gathering.
Level of detail that is required for data analysis; for instance, complete attribute detail is deferred until after decisions about system scope.
Level of detail that is required for activity analysis.
Not all activities fully subdivided to decide about the scope of the system. The business objectives for the project suggest which activities must be investigated thoroughly.
Requirements for, and timing of, current systems analysis.
The analysis is performed to reuse or to replace current data or systems.
The volume of work, or the availability of resources, require work to be started in parallel with activity and data analysis. Work can also be postponed until after decisions about the scope of the system have been made.
Requirements for defining expected effects for all elementary processes. The expected effects are described in Analyzing Activities.
Level of detail define process logic. Some business rules are defined during analysis, but many can be deferred until the design phase when detailed procedure definitions are created.
Requirements for formal and informal coordination with other development projects and the timing of this coordination.