Unit 2 - Software Project Scheduling III
Unit 2 - Software Project Scheduling III
• Co‐ordination>>>
▫ When do the staff in different departments need to be available to work on a
particular project and when do staff need to be transferred between projects?
Er. Rajan Karmacharya
When to plan
• Planning is an ongoing process of refinement, each iteration becoming more detailed
and more accurate than the last.
• During feasibility study and project start up>>>
▫ the main purpose of planning will be to estimate timescales and the risks of not
achieving target completion dates or keeping within budget
• As the project proceeds beyond the feasibility study, the emphasis will be placed upon
the production of activity plans for ensuring resource availability and cash flow
control.
• Throughout the project, until the final deliverable has reached the customer,
monitoring and re‐planning must continue to correct any drift that might prevent
meeting time or cost targets.
Er. Rajan Karmacharya
Project Schedule
• Before work commences on a project, the project plan must be developed to the level
of showing dates when each activity should start and finish and when and how much
of each resource will be required.
• One the plan has been refined to this level of detail, we call it a project schedule.
• Creating a project schedule comprises four main stages.
▫ The first step in producing the plan is to decide what activities need to carried out and
in what order they are to be done. ‐‐‐‐‐ creating an activity plan
▫ The ideal activity plan will then be the subject of an activity risk analysis, aimed at
identifying potential problems.
▫ The third step is resource allocation.
▫ The final step is schedule production. Once resources have been allocated to each
activity, we will be in a position to draw up and publish a project schedule, which
indicates planned start and completion dates and a resource requirement statement for
each activity.
6
• Too great depth will result in a large number of small tasks that will be difficult to
manage.
• Too shallow structure will provide insufficient detail for project control.
• Each branch should, however, be broken down at least to a level where each leaf may
be assigned to an individual or responsible section within the organization.
Er. Rajan Karmacharya
Data Take-on
▫ Code and Data Take‐on can therefore be said to be precedents of Program Test and Program
Test is precedent of Install
Er. Rajan Karmacharya
Correct Diagnose
Errors Errors
Er. Rajan Karmacharya
Write User
Manual
Er. Rajan Karmacharya
Formulating a Network Model
Design Code Test Install
Program Program Program Program
Write User
Manual
▫ We might come across situations where we wish to undertake two activities in parallel so long
as there is a lag between the two.
▫ Eg. We would designate an activity “test and document amendments which would make it
impossible to show that amendment recording could start say 1 day after testing has begun
and finishing a little after the completion of testing.
▫ The figure indicates that the document amendments can start one day after the start of prototype
testing and will be completed two days after prototype testing us completed.
Build Test Revise
Prototype Prototype Specification
1 2
Document
Amendments
Concept Check
State what is wrong with each of them and redraw
where possible.
Answer
Activity Labelling Er. Rajan Karmacharya
26
Event
Number
Earliest Latest
Date Date
Slack
• The earliest date for an event is the earliest finish date for all the activities terminating
at the event.
• Where more than one activity terminates at a common event we take the latest of the
earliest finish dates for those activities.
The Backward Pass Rule
• The latest date for an event is the latest start date for all the activities that may
commence from that event.
• Where more than one activity commences at a common event, we take the earliest of
the latest start dates for those activities.
• Slack : it is the difference between the earliest date and the latest date for an
event – it is a measure of how late an event may be without affecting the end
date of the project.
• The critical path is the path joining all nodes with a zero slack.
34