Lesson 8: Tracking

1
Lesson 8 Tracking Controlling the Project
Software Engineering II
2
Lesson Objectives

• Understand why OO developments require detailed
  tracking
• Learn how to avoid the perpetually 90 complete
  syndrome
• Understand ways to evaluate OO development success

3
OO PROJECT CONTROL IS AN ACTIVE PROCESS

• Continuous assessment
• progress
• risks
• resource availability
• Timely response to changes

early warning system against a losing year, one
day at a time. - Fred Brooks
4
ESTABLISH BASELINE PLAN FOR MEASUREMENT
Resource Utilization
Integrated Schedule
Object Dependencies and Critical Path
5
DEVELOP OO TRACKING SYSTEM
6
SAMPLE WORKPACKAGE
Link to master project schedule

• Identification section

Definition section estimates work to be completed
Link to detailed software schedule and PERT
network
Allocation section defines current status and
costs
Link to engineers performing work and metrics
database
7
PROJECTS EARN VALUE AS WORKPACKAGES ARE COMPLETED

• Track only completed workpackage to avoid
  perpetually 90 complete syndrome
• Use inspections to certify complete workpackages

8
MONITOR PROGRESS WITH WORKPACKAGES

• Critical path changes
• Creeping Elegance
• Overbudget areas
• Extended schedules
• Excessive rework
• Resource saturation

9
SHINGOS RULES OF RESPONSE

• Control upstream, as close to the source of the
  potential defect as possible
• Establish controls in relation to the severity of
  the problem
• Think smart and small. Strive for the simplest,
  most efficient, and most economical intervention
• Dont delay improvement by overanalyzing

Shigeo Shingo, Toyota
10
DID YOUR OO PROJECT SUCCEED?
Conduct an off-site postmortem

• What worked? - What didnt?
• quantitative statistics
• qualitative feelings
• What helped? - What hurt?
• significant deviations from plan?
• effective solutions?
• impact of tools and training?
• effective organization?

11
TRACKING AND CONTROLLING SUMMARY

• 1. Project control is an active process
• 2. Establish tracking system based upon
  workpackages
• 3. Respond to metrics with timely, measured
  responses
• 4. Conduct project postmortem reviews