Project Management

Project Scheduling
• Project-task scheduling is an important project
planning activity.
• Identify all the tasks needed to complete the project.
• Break down large tasks into small activities.
• Determine the dependency among different activities.
• Establish the most likely estimates for the time durations
necessary to complete the activities.
• Allocate resources to activities.
• Plan the starting and ending dates for various activities.
• Determine the critical path.
• A critical path is the chain of activities that determines the
duration of the project.
 Project Scheduling
• Work breakdown structure
– The root of the tree is labeled by the problem name. Each node of the tree is
broken down into smaller activities that are made the children of the node.
 Project Scheduling
Determine the activity network for the MIS development art. Determine the
duration and dependencies for each task shown in Table

T1 specification 15 days --
T2 Design database 45 T1 dependent
T3 Design GUI 30 T1
T4 Code database 105 T2
T5 Code GUI part 45 T3
T6 Integrate and test 120 T4 and T5
T7 Write user manual 60 T1
 Project Scheduling
• Activity Network
• Activity on Node ( AoN) – Each activity is represented by a rectangular (or circular)
node
• Activity on Edge (AoE) – Activities are represented using activity on edge (AoE)
 Project Scheduling
Critical Path Method ( CPM)
Minimum Time (MT) – Minimum time to finish the project. It is the maximum
of all paths from start to finish.

Tasks
Earliest start (ES)- time of task is maximum of all paths from the start to this
task.
Latest start time (LST) – difference between MT and the maximum of all paths
from this task to the finish.
Earliest finish time (EF) – for a task is sum of earliest start time of the task and
duration of the task.
Latest finish ( LF)- latest time by which a task can finish without affecting the
final completion time of the project.
Slack time ( ST) – total time that a task may be delayed before it affect the end
time of the project.
 Project Scheduling
• Use the activity network to determine the ES (Earliest start ) and Earliest finish time
(EF) for every task.
 Project Scheduling
• Gantt
Chart
 Project Scheduling
• PERT chart
• PERT chart represents the statistical variations in the
project estimates assuming a normal distribution.
Thus, in a PERT chart instead of making a single
estimate for each task, pessimistic, likely, and
optimistic estimates are made.
• Estimated time = (optimistic + 4 * most likely + worst
case ) / 6
• The boxes of PERT charts are usually annotated with
the pessimistic, likely, and optimistic estimates for
every task.
 Project Scheduling
• PERT chart
 Project Scheduling
• The following table (Table A ) indicates the
various tasks involved in completing a software
project, the corresponding activities, and the
estimated effort for each task in person-months.
• The precedence relation Ti <= {Tj, Tk} implies
that Ti must complete before either task Tj or Tk
can start. Preccedence relation : T1 <= T2 <= {T3,
T4, T5, T6 } <= T7
• Draw activity network,
• Determine ES, EF and LS, LF for every task.
• Develop a Gantt chart for the project.
 Project Scheduling
Table A Activity Effort (PM)
T1 Requirement specification 1
T2 Design 2
T3 Code actuator interface 2
module
T4 Code sensor interface 5
modiule
T5 Code user interface part 3
T6 Code control processing 1
part
T7 Integrate and test 6
T8 Write user manual 3
 Project Scheduling
• The following table (Table B ) indicates the
activities, duration in weeks, and the
immediate predessor .
• Draw activity network,
• Determine ES, EF and LS, LF for every task.
• Develop a Gantt chart for the project.
Table B Activity Duratio Immediate
(Activity n predecessor
) (weeks)
1 Obtain Requirement 4 --
2 Analyse operations 4 --
3 Define subsystems 2 1
4 Develop database 4 1
5 Make decision analysis 3 2
6 Identify constraints 2 5
7 Build module 1 8 3,4,6
8 Build module 2 12 3,4,6
9 Build module 3 18 3,4,6
10 Write report 10 6
11 Integration and test 8 7,8,9
12 Implementation 2 10,11
 Staffing level estimation
• Once the effort required
to develop a software has
been determined, it is
necessary to determine
the staffing requirement
for the project.
• Putnam first studied the
problem of what should
be a proper staffing
pattern for software
projects.
 Putnam’s work
• Rayleigh-Norden curve can be used to relate the number of delivered lines
of code to the effort and the time required to develop the project. By
analyzing a large number of army projects, Putnam derived the following
expression:
• K is the total effort expended (in PM) in the product development and L is
the product size in KLOC.
• td can be approximately considered as the time required to develop the
• software.
• Ck =2 for poor development environment ( no methodology poor
documentation), Ck = 8 for good software developmnent environment, Ck
= 11 for an excellent environment ( automated tools techniques)
Putnam’s work
 Putnam
• The nominal effort and duration of a project
have been estimated to be 1000 PM and 15
months. The project cost has been negotiated
to be Rs 200, 000, 000. The needs the product
to be developed and delievered in 12 months.
What should be the new cost to be
negotiated.
 Putnam
• The nominal effort and duration of a project have
been estimated to be 1000 PM and 15 months.
The project cost has been negotiated to be Rs
200, 000, 000. The needs the product to be
developed and delivered in 12 months. What
should be the new cost to be negotiated.
• New cost = 200,000,000 * (15/12) * (15/12) *
(15/12) * (15/12)
=488,281,250
 Putnam
• Explain how putnam’s model can be used to
compute the change in project cost with project
duration.
• Consider a real timesoftware project estimated at
33,000 LOC , 12 person-years of effort. If 8 people
are assigned to the project team, the project can
be completed in approximately 1.3 years. If
however, we extend the end date to 1.75 year
then ____person-years.
 Putnam
• Explain how putnam’s model can be used to
compute the change in project cost with project
duration.
• Consider a real timesoftware project estimated at
33,000 LOC , 12 person-years of effort. If 8 people
are assigned to the project team, the project can
be completed in approximately 1.3 years. If
however, we extend the end date to 1.75 year
then 3.8 person-years. Effort in PM= (LOC * LOC
* LOC) / (Parameter * Parameter * Parameter) * (
t * t* t*t)
 Team structures
• Chief Programmer Team
• Democratic Team
• Mixed Control Team Organization
Team structures (chief programmer
versus democratic )
 Team structures (mixed team
structures)
The mixed control team organization is
suitable for large team sizes. The
democratic arrangement at the
senior engineers level is used to
decompose the problem into small parts.
Each democratic setup at the programmer
level attempts solution to a single part.
Thus, this team organization is eminently
suited to handle large and complex
programs. This team structure is
extremely popular and is being used in
many software development companies.
 Team structure
• Suppose you are a project manager of a large
product development team to make a choice
between democratic and chief programmer
team organizations, which one would you
adopt for the team. Justify?