Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
BS (CS) - SSUET
LECTURE 6
TIME MANAGEMENT FOR SOFTWARE PROJECT
Project Time Management
The process required to manage timely completion of the project.
It includes how activities are prioritized and sequenced so that work is done in order.
Time Management Processes
1.
2.
3.
4.
5.
6.
7.
In small project, defining & sequencing activities, estimating activity resource & duration,
developing schedule are viewed as a single process.
Define Activities is the process where specific actions required to producedeliverables are
identified and documented.
In this process, the work packages from the WBS are broken down into activities.
Activities
Activities are tasks or actions required to produce deliverables. It is the actual work that
goes into making a product.
Page 1
BS (CS) - SSUET
The activities are broken down into small levels so that they can be estimated, scheduled,
monitored and controlled.
Both work packages and activities can be used as a basis for estimating, scheduling,
executing, monitoring and controlling the project work. This is because they are items
which have been broken down to the lowest level.
Page 2
BS (CS) - SSUET
The sequence activities process involves putting the activities and milestone in a sequence.
The activities and milestones will be organized according to the order in which the work
will be done on the project.
The output of Sequence Activities Process is Project Schedule Network Diagram.
The Precedence Diagramming Method uses four types of dependencies. Those dependencies are
as follows:
1.
2.
3.
4.
Page 3
BS (CS) - SSUET
Finish-to-start: The predecessor activity must finish before the successor activity can start. This
is the most common relationship type. Example: The Web server must be running before the
SQL database can connect.
Finish-to-finish: Two activities must finish at the same time. The two activities dont have to
begin at once, but they must end at the same time. Example: The user acceptability testing and
the third-party reviews of the build must complete at the same time.
Start-to-start: Two activities must begin at the same time. The two activities may be of varying
duration, so they dont have to end at the same time, but they have to start at the same time.
Example: The final build of the software and the creation of the online help system should start
at the same time.
Start-to-finish: The predecessor activity must start in order for the successor activity to finish.
This is the most unusual of all the relationship types and is rarely used. You might run across it if
you do just-in-time scheduling or manufacturing. Example: The software testing cant be
completed until the quality control department reviews the testing results.
Leads and Lags
Page 4
BS (CS) - SSUET
Page 5
BS (CS) - SSUET
Page 6
BS (CS) - SSUET
Example:
A project manager used data from past projects to come up with an estimate for an upcoming
software system replacement project. She felt confident about 25-day duration, but also noted
that adding an extra resource could bring the schedule down to 10 days. The test team felt that
the complexity of some completely new features would add additional test cases, adding a few
weeks for a 40-day estimate. Find the Optimistic, Most Likely, Pessimistic and Expected
durations respectively.
Solution:
Optimistic duration = 10d; Most likely duration = 25d; Pessimistic duration = 40d
Expected duration = 40+10+4(25) / 6
Expected duration = 25days
The Develop Schedule process is the core of Time Management. Its the process where you
put it all togetherwhere you take everything youve done so far and combine it into one
final schedule for the whole project.
Page 7
BS (CS) - SSUET
Page 8