PROJECT SCHEDULING

BY:
PRABJOT KAUR
YOGITA
 PROJECT
SCHEDULING

DETERMINING THE DEVELOPING THE

OVERALL SCHEDULE DETAILED SCEDULEOF
WITH THE MILESTONES THE VARIOUS TASKS
 PROJECT SCHEDULE (p)
• A project Schedule is at two levels -
Overall Schedule and Detailed Schedule.

• Overall Schedule comprises of major

milestones and final date.

• Detailed Schedule is the assignment of

lowest level tasks to resources
OVERALL SCHEDULE (yogita)
• A schedule is modeled as depending on the total
effort, which in turn depends on the size.
• The IBM Federal Systems Divisions found that
the total duration M, in calendar months can be
estimated by
M=4.1E
• In COCOMO, the equation for schedule for an
organic type of software is

M=2.5 E
 Also….(y)
• Depends heavily on the effort estimate.

• For an effort estimate, some flexibility

exists depending on resources assigned.

• Stretching a schedule is easy;

compressing is hard and expensive.
 Square Root Check(y)
• Example
A 56 Person-Month
project can be done in
8 Months (7 People)
or 7 Months (8 People).
MILESTONES
IN THE
PROJECT
Manpower Ramp-up (prabjot)

PTS

Design Build Test

 COCOMO GIVES…..(p)

19% for design

62% for programming
18% for integration
 (yogita)
• Major tasks fixed while planning the
milestones are broken into small schedule
activities.
• This is done in hierarchical manner.
• Developing the detailed design for each
module.
• Review of each detailed design.
• Fixing of defects found and so on.
 SCHEDULING IS AN ITERATIVE
PROCESS(p)
• Firstly, when the detailed design are broken into
tasks, the effort estimates re set.
• At each level of refinement, the project manager
determines the effort and checks it against the
effort estimates.
• If this detailed schedule is not consistent with the
Overall Schedule and effort estimates, the
schedule is changed.
• If it is found that the Detailed Schedule cannot
match the milestone effort and schedule, then
the earlier estimates must be revised.
 Detailed Schedule(p)
• Detailed Scheduling not done completely
in the start.
• MS Project for keeping it.
• Detailed Schedule is the most lively
document for managing the project.
• Any activity to be done must get reflected
in the Detailed Schedule.
 Detail schedule(y)
• Each task has name, date, duration,
resource etc assigned
• % done is for tracking (tools use it)
• The detailed schedule has to be
consistent with milestones
– Tasks are sub-activities of milestone level
activities, so effort should add up, total
schedule should be preserved
Rest is team structure, will do in
sumtym…or read 4m d buk…