PS0504 Managing the Baseline Schedule, Majerowicz.pdf

8/15/2019 PS0504 Managing the Baseline Schedule, Majerowicz.pdf

1/23

Mid-Atlantic Operations

Managing The Baseline Schedule

Walter MajerowiczPlanning & Schedule Manager

Polar Operational Environmental Satellites Program


2/23

Objective

Provide an overview of proven baseline schedule

control concepts and practices by:

• Summarizing the steps for developing the baselineschedule

• Highlighting the elements of schedule control

• Illustrating the schedule revision process based on lessons-

learned from major projects/contracts



3/23

Agenda

• Introduction

• Developing the Baseline Schedule• Controlling the Baseline Schedule

• Example Baseline Schedule Revision

• Summary & Conclusions



4/23

Introduction



5/23

Time / Schedule Management• Project Schedule Management consists of the processes

required to ensure timely completion of the project: – Activity definitionè what needs to be done

– Activity sequencingè the order things need to occur – Activity duration estimatingè the number of work periods needed

– Schedule developmentè creating the roadmap

– Schedule status accountingè getting the facts

– Schedule analysisè what is the schedule telling us

– Schedule performance reporting è how are we doing and where arewe going

– Schedule controlè managing change

• Project Scheduling is the application of these processes



6/23

Focus on the Baseline Schedule• Premise

– Baseline schedules can, will and should change

– Projects emphasize accurate current operating schedules

– Projects do not always maintain accurate baseline schedules

• Approach

– Freeze the baseline schedule at the start of the project

– Modify the “unstatused” baseline schedule for new scope changes

– Issue baseline schedule revisions

• Findings – A disciplined schedule control process identifies the impact of scope

changes on project/contract deliverables and objectives

– Without schedule control, the schedule impact of new scope changesare difficult to distinguish from performance problems



7/23


The Baseline Schedule• Represents the project team’s schedule commitment• Establishes target dates and time spans for the

accomplishment of activities

• Documents the project’s schedule assumptions

• “Freezes” the original plan at the completion of the initial project planning, but . . . – Will and should change over the life of the project (e.g. new scope)

– Should not be changed to match performance

• Provides a time perspective to the project team

• Sets a benchmark against which schedule performance ismeasured and forecasts projected ~ in order to better determine future courses of action

• Correlates to project’s original cost estimate / budget


8/23

Developing the BaselineSchedule



9/23

Drawing Tree

WBS

3.0

Instruments

1.0 System

Engineering

Total Program

2.0 Spacecraft

S O W

Planning Meetings With Project Team

Previous Projects’ History

Identify the Project Activities


Activity List

• Design

• Build• Test


10/23

Determine the Activity Sequence

Activity List

• Design• Build

• Test


Mandatory

Dependencies

External

Dependencies

Assumptions

Constraints


11/23


Estimate Activity DurationsDesign

BuildTest

DesignBuild

Test

DesignBuild

Test

The Schedule According to Engineering

The Schedule According to Manufacturing

The Schedule According to System Test


12/23

Develop The Project Schedule


Contract

Award

Design

ProcureLong Lead

Fabrication

Assembly

0 days

START ON

8/1/01

100 days

120 days

30 days

15 days 25 days

FS

FS

FS

FS

FS

FS

8-1-01

8-1-01

8-1-01

12-18-01

8-1-011-15-02

12-19-01

1-29-02

1-30-02

2-19-03

2-20-02

3-26-03

12-7-01 = Early Start

10-10-02 = Early Finish

Test

Parts

Deliver

0 days

5-1-01

5-1-01

FNET

5/1/01

FS


13/23

“Freeze” The Baseline ScheduleID Task Name Duration Total Slack 1 Contract Award 0 d 26 d

2 Design 100 d 26 d

3 Procure Long Lead Parts 120 d 36 d

4 Fabrication 30 d 26 d

5 Assembly 15 d 26 d

6 Test & Delivery 25 d 26 d

7 Contract Delivery 0 d 0 d

8/1

8/1 12/18

8/1 1/15

12/19 1/29

1/30 2/19

2/20 3/26

5/1

Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun

2001 2002

REV: Baseline 8-1-01



14/23

Controlling the BaselineSchedule



15/23

Schedule ControlSchedule Control is the process of changing the project schedule in a

timely, disciplined manner in response to a) new work scope, b) the

need for a new schedule baseline, and c) recovery from actual project

problems.

Baseline

Revisions

Workaround

Planning

ScheduleControl

Replanning


REV A, REV B New Baseline Recovery Schedule


16/23

Baseline Schedule RevisionsThe revision process consists of modifying the baseline schedule with

the incorporation of new authorized work scope.

ØBaseline schedule

ØContract

deliverables

Ø New scopeØChange Requests

ØCustomer

authorization

ØBaseline schedule

revisions ~ REV A,

REV B, etc.

ØContract delivery

date modifications

INPUT PROCESS OUTPUT

Incorporate the

change into the

baseline schedule and

issue a revised

schedule



17/23

Schedule Revision Guidelines• Lock the baseline schedule away . . . but keep the key handy!

• Customer contractual authorization needed before incorporating newscope into baseline schedule

• Assume existing baseline schedule is in “on track” at the time customer

authorizes new scope change• Incorporate the change into the existing “unstatused” baseline schedule

• Do not use schedule reserve or slack to absorb impact of new scopechanges

• Review schedule revision with project team, change board and customer

• Release formal baseline schedule revision to the project team

• Continue management process: authorize work and budget to CAMs,submit claim proposal, modify contract, etc.



18/23

The Customer Makes A Change


On 10-1-01, the customer adds a requirement for RF

Testing to the contract

Contractor estimates RF

Testing will take 10 days

1 2

3 4 R E V A

“Unstatused” baseline

schedule is modified with

new RF Test

Revision A of the baseline

schedule is issued


19/23

Baseline Schedule – REV A


ID Task Name Duration Total Slack

1 Contract Award 0 d 26 d

2 Design 100 d 26 d

3 Procure Long Lead Parts 120 d 36 d

4 Fabrication 30 d 26 d

5 Assembly 15 d 26 d

6 Test 25 d 26 d

7 RF Test & Delivery 10 d 26 d

8 Contract Delivery 0 d 0 d

8/1

8/1 12/18

8/1 1/15

12/19 1/29

1/30 2/19

2/20 3/26

3/27 4/9

5/15

Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul

2001 2002

REV A: 10-1-01


20/23

Baseline Schedule Comparison


+26 days+26 daysTotalFloat

5-15-025-1-02

Contract

Delivery

4-9-023-26-02PlannedDelivery

REV ABaseline


21/23

Baseline Schedule Revision Matrix


5-15-02

4-9-02

REV B

(12-6-01)

Add UV

Coating

6-17-2

5-11-02

REV C

(2-4-02)

Delete Spec

1.5.3

5-15-025-1-02

Contract

Delivery

4-9-023-26-02

Planned

Delivery

REV A

(10-1-01)

Add RF

Test

Baseline

(8-1-01)

The baseline revision matrix helps both customer and

contractor maintain visibility of the effect of new scope

changes.


22/23

Without An Accurate Baseline Schedule

• Projects may lose sight of their schedule

objectives and commitments

• Credibility and relevance of schedule performanceand forecasts is questionable

• Projects could lose schedule integration with cost plan

• Contractors may have difficulty segregating theimpact (schedule & cost) of new scope from the

impact of technical or performanceproblems



23/23

Summary & Conclusions• The baseline schedule is a tool that should be

modified as new work scope is authorized

• An accurate baseline schedule is necessary toassess actual performance, put forecasts in

perspective, and determine the significance of

variances

• A structured revision process is required to

maintain an accurate baseline schedule
