Introduction | What's New in Version 5.5 | International Recognition
About the Author | Sources and References
Content Index | Order Your V5.5 Copy Here!

Schedule Update - to - Scope Interfaces

prev

next

Schedule Update

Revision of the schedule to reflect the most current information on the project. [D01786]

Schedule Variance ("SV")

Either

1. Any difference between the scheduled completion of an activity and the actual completion of that activity, or
2. In Earned Value, BCWP less BCWS.

[D01789]

Any difference between the projected duration for an activity and the actual duration of the activity. Also the difference between projected start and finish dates and actual or revised start and finish dates. [D01787]

The difference between the budgeted cost of work performed and the budgeted cost of work scheduled at any point in time (BCWP - BCWS). [D01788]

The difference between BCWP and BCWS and shows how current schedule compares with the baseline schedule(in terms of time progress). This can be shown as a numeric difference, where positive values indicate that the schedule is ahead of the baseline schedule and negative values which indicate that work is behind schedule. It can also be expressed as a percentage such as: SV(%) = (BCWP-BCWS) x 100 / BCWS [D03612]

Schedule Work Unit

A calendar time unit when work may be performed on an activity. [D01790]

Scheduled Cost ("SC")

The total cost of work when completed as calculated according to the current schedule. [D03609]

Scheduled Cost of Work

See Budgeted Cost of Work Scheduled. [D03255]

Scheduled Finish ("SF")

The date calculated by the resource scheduling program as the earliest date on which an activity can finish, having regard to resource constraints as well as project logic. [D01792]

Scheduled Finish Date ("SF")

The date work was scheduled to finish on an activity. The scheduled finish date is normally within the range of dates delimited by the early finish date and the late finish date. [D01793]

Scheduled Network

A network of project activities for which time planning has been done. [D01794]

Scheduled Performance Indicator ("SPI")

The ratio of BCWP to BCWS i.e. SPI = BCWP / BCWS. A positive value (i.e. greater than 1) indicates that work is ahead of schedule. A negative value (i.e. less than 1) indicates that work is behind schedule [D03610]

Scheduled Performance Ratio ("SPR")

See Scheduled Performance Indicator [D03611]

Scheduled Start ("SS")

The date calculated by the resource scheduling program as the earliest date on which an activity can start, having regard to resource constraints as well as project logic. [D01795]

Scheduled Start Date ("SSD")

The date work was scheduled to start on an activity. The scheduled start date is normally within the range of dates delimited by the early start date and the late start date. [D01796]

Scheduling

The process of converting a general or outline plan for a project into a time-based schedule based on available resources and time constraints. [D01797]

The process of determining when project activities will take place depending on defined durations and precedent activities. Schedule constraints specify when an activity should start or end based on duration, predecessors, external predecessor relationships, resource availability, or target dates. [D01798]

The recognition of realistic time and resource restraints which will, in some way, influence the execution of the plan. [D01799]

Time planning. [D01800]

The determination of when a series of activities should start, and when they should finish, typically in relation to many other activities and depending on the availability of resources. [D03688]

Determination of the best means for achieving a project's general and specific schedule objectives. This involves identification and optimization of the project's overall and stage schedule requirements, resource availability and internal external constraint and activity sequencing. [D03944]

Scheduling Techniques

There are a large variety of scheduling techniques available to the project practitioner for both determination and presentation. For example, arrow diagramming, logic networks, bar charts, PERT, trending, the use of a variety of software, and so on. [D03256]

Scientific Wild Anatomical Guess ("SWAG")

A rapid estimate based on personal experience. Sometimes used in cost and schedule predictions. [D04229]

Scope

The definition that describes the project's product deliverables. See also Managing Scope. [D03765]

The combination of all project goals and tasks, and the work required to accomplish them. [D01801]

The sum of the products and services to be provided as a project. [D01802]

The sum of work content of a project. [D01803]

The work content and products of a project or component of a project. Scope is fully described by naming all activities performed, the resources consumed and the end products which result, including quality standards. A statement of scope should be introduced by a brief background to the project, or component, and the general objective(s). [D01804]

The bounded set of verifiable end products, or outputs, which the project team undertakes to provide to the project sponsor. The required set of end results or products with specified physical or functional characteristics. [D01805]

The deliverables that will be produced by the project. [D02208]

Scope is the way that we describe the boundaries of the project. It defines what the project will deliver and what it will not deliver. For larger projects, it can include the organizations affected, the transactions affected, the data types included, etc. [D05114]

Scope Allowance

See Contingency Reserve. [D02372]

Scope Baseline

A sufficiently detailed description of the project's deliverables, and/or its components, that provides a basis for measurement of changes from that baseline. A key tool in documenting the scope baseline is the work breakdown structure (WBS). [D05115]

See also Baseline. [D01806]

Summary description of the project or component's original content and end product including basic budgetary and time constraint data. [D01807]

Scope Baseline Approval

Approval of the scope baseline by the appropriate authority (project sponsors and senior project management staff). [D01808]

Scope Boundaries

The team determines what processes are included in the project and which are excluded. They also decide what processes or projects might be affected by or affect the project. [D02209]

Scope Change

Any change to the project scope. A scope change almost always requires an adjustment to the project cost or schedule. [D01811]

A deviation from the originally agreed project scope. [D01809]

Any change in a project scope that requires a change in the projectês cost or schedule. [D01810]

Scope Change Control

Controlling changes to the scope. [D01812]

Scope Changes

Any change in the project's deliverables from that which was originally intended, i.e. when compared to the scope baseline. [D05116]

Scope Constraints

Applicable restrictions which will affect the scope. [D01813]

Scope Cost

Basic budgetary constraints. [D01814]

Scope Creep

On-going requirements increase without corresponding adjustment of approved cost and schedule allowances. As some projects progress, especially through the definition and development phases, requirements tend to change incrementally, causing the project manager to add to the project's mission or objectives without getting a corresponding increase in the time and budget allowances. [D02279]

The term often used to describe the continual extension of the scope of some projects. Often leading to a runaway project. [D03945]

Scope Criteria

Standards or rules composed of parameters to be considered in defining the project. [D01815]

Scope Definition

Breaking down a deliverable in to smaller manageable parts to ensure better control. [D01816]

Scope Description

A detailed description of the final deliverable [D02210]

Scope Interfaces

Points of interaction between the project or its components and its/their respective environments. [D01817]