ACTIVITY
ACTIVITY
WBS is a name given to a technique in project management in which the project is broken down
into manageable chunks. WBS represents a task oriented family tree of activities and organizes,
defines, and graphically displays the total work to be accomplished in order to achieve the final
objectives of the project. This serves as the common framework for other exercises such as
planning, scheduling, cost estimating, budgeting, monitoring, reporting, directing and controlling
the entire project.
The process WBS involves splitting project works into manageable constituents till the desired
level. These levels may be sub project level, task level, work packages, activities, and operations
and depend upon the nature and complexity of the project. Definition and classification of
project work breakdown levels are given in the following table.
Description Main criteria
Sub project level An independent, deliverable end product requiring processing of
multitasks having large volume of work
Task level An identifiable and deliverable major work containing one or more
packages
Work package level A sizeable, identifiable, measure, cost able and controllable work
package of activities
Activity level Identifiable lower level job, operation, or process, which consumes
time and possible resources
Operations level A lowest level day to day operation, or process, which is part of an
activity
Construction projects are best managed by work packages and best planned and monitored by
activities. Each activity consumes time and requires resources. After identifying various work
packages and activities, next job of the planner is to list all such activities and arrange them in a
chronological order as per sequence of operations and technological requirements. Dependency
of one activity on another is to be fixed and recorded accordingly. Such a list of activities, once
prepared, is also helpful in delegating responsibilities and calculating the manpower and other
resource requirements for each of the activities. The planner is then required to assess the activity
durations i.e. time each of the activities is likely to consume. Hence WBS is a tool that identifies
the functional elements of a project and their inter-relationship.
Example: the concreting work for roof slab of a residential building can be split up into various
elements as follows
Concreting for the roof slab
Once the activities have been identified in process WBS, it is necessary to find out what
resources will be needed to perform them. That is where this process Estimate Activity
Resources comes in. It is not only the amount of resources, but the schedule of when they are
available that are both needed to find out how long a particular activity will take.
Resource Estimation Techniques
1. Expert Judgment: Expertise should be sought during this process by those who have
specialized knowledge in estimating team and physical resources, or who have done such
estimation for similar, previous projects.
4. Parametric Estimating: This technique also uses information regarding resources from a
previous similar project. The difference is that there is a statistical relationship between
historical data and other variables which can be used to apply to the estimation of resources
in the current project. Here’s an example: if you are trying to complete an estimation of the
resources needed to build a house in a subdivision, you can do it by looking at the data on the
resources needed to build previous houses in the subdivision. This would be an example of
analogous estimating. However, if you took all of the data regarding those previously-built
houses and calculated how many resources would be required per 100 square feet, then you
would have a statistical relationship or a parameter you could then use to calculate the
resources required for the current project.
5. Project Management Information System (PMIS): This is the software tool (like
Microsoft Project) used to help manage the resources on a project.
Duration estimation methods: Generally any of the three methods are employed for assessing,
the duration of construction activities. These are termed as one-time estimate, three-time PERT
estimate and non-linear distribution estimate.
1. One-time estimate: The estimation of duration is based on one or more of the following
Planning data
Past experience on execution of a similar project.
Average time assessed by a group of executives.
Example: In excavation of 3000cft of common earth, if output of a man is taken as 100cft per
day and six men can be effectively employed on the job, the duration of the activity would be
5 days.
In most of the construction work, it is generally possible to assess the duration of an activity
with reasonable certainty by using experience or the departmental planning data. The one
time estimate for activity durations is used in these projects. Further the one time estimate is
task oriented and the activity duration can be correlated to the cost and the resources
employed. The method of the one-time estimate is simple and can easily be followed by all
concerned with the planning or execution of construction work.
2. Three time PERT estimate: When the exact duration of an activity, like research and
development, is not certain, the three-time estimate is used to compute its expected
duration. The following relation is used to calculate the expected duration of such an
activity.
To+4Tm+Tp
Te=
6
Where, T e =expected completion time
To = optimistic time, assuming that everything goes extremely well with no delays
Tp = pessimistic time, assuming that everything goes wrong
Tm = most likely time, assuming normal conditions.
Example: Let us take the activity of sanctioning of a government project. It has to pass
through many channels and depends upon many factors. Let us assume that the sanction is
most likely to take 8 weeks, and if all goes well, the earliest it can happen in 6 weeks, but in
case , it will certainly come through in 16 weeks. The expected duration of the activity can be
calculated as follows:
6+(4x8)+16
Te= = 9 weeks
6
The three-time estimate can effectively be used in certain areas of construction projects
where time is the main criterion and the resources employed are of secondary consideration.
Some of these are as follows.
The planning of projects especially, at the feasibility stage.
The skeleton networks enclosed with the tender documents
The contracted works, where time is the main consideration for the management.
The complex structures, where the exact duration estimate is difficult to assess.
3. Three-Point Estimating: This technique is employed to reduce the biases and uncertainties
in estimating assumptions. Three estimates are determined instead of finding one estimate,
and then their average is taken to reduce the uncertainties, risks, and biases. PERT (Program
Evaluation and Review Technique) is the most commonly used method in three-point
estimation technique.
Most Likely Cost (Cm): Considers a typical case and everything goes as usual.
Pessimistic Cost (Cp): Considers the worst case and assumes that almost everything goes
wrong.
Optimistic Cost (Co): Considers the best case and concludes that everything goes better
than presumed.
PERT estimate formula is:
Estimates derived from this technique are better than the two techniques presented earlier
because it minimizes the biased view from the data and provides a more accurate estimate.
4. Bottom-up Estimating: The bottom-up estimating technique is also called the “definitive
technique.” This technique is the most accurate, time-consuming, and costly technique for
estimating the cost of a project. Here, the cost of every single activity is determined with the
highest level of detail at the bottom level and then rolls up to calculate the total project cost.
Here, the total project work is broken down into the smallest work components. Each
component cost is estimated, and finally, it is aggregated to determine the project’s cost
estimate.
ACTIVITY SEQUENCING
Sequence Activities is the process of identifying and documenting relationships among the
project activities. The key benefit of this process is that it defines the logical sequence of work to
obtain the greatest efficiency given all project constraints.
2. Project Documents
a) Activities list–all activities needed for the project, based on the decomposition process done
on the work packages. These are to be sequenced in the upcoming process.
b) Activity attributes–information about the activities
any clearly defined predecessor or successor relationships among activities
any specified leads or lags between activities
any specified logical relationships between activities (does the successor activity need to
start before or after the predecessor activity ends, for example)
c) Milestone list–milestones can be specified as early as the project charter, but can also be
made specific as a result of the last process
4. Organizational Process Assets (OPA): The definition of OPA is any or all process related
assets, from any or all of the organizations involved in the project that are or can be used to
influence the project’s success. These process assets include formal and informal plans,
policies, procedures, and guidelines.
a) Templates to be used for creating a network of the project activities during the upcoming
process
b) Policies, procedures and/or guidelines for developing logical relationships between activities
c) Lessons learned repository–if there have been similar previous projects done by the
organization, this can help with the process of sequencing the activities in the current project
a) Finish to Start (FS): In this type of dependency, the second activity cannot be started until
the first activity completes. This type of dependency is the most commonly used dependency
in the diagramming techniques.
For example, to paint a wall you first need to build a wall. In this case, the first activity is
building the wall and second activity will be painting. You cannot start painting the wall
unless the wall is ready.
b) Finish to Finish (FF): Here, the second activity cannot be finished until the first activity
finishes. In other words, both activities should finish simultaneously.
For example, let us say that you are coding a program for a client, and the client is providing
you with the characteristics of the program. In this case, you cannot finish coding for your
program until the client gives you his complete requirements. Here, both activities should
finish simultaneously.
c) Start to Start (SS): Here, the second activity cannot be started until the first activity starts.
Both activities should start simultaneously.
Suppose you have to apply a primary coating on a wall. To apply the coating, you also need to
clean the wall. Therefore, one team will start cleaning the wall and second team will paint it.
Both activities can be started at the same time.
d) Start to Finish (SF): In this type of dependency, the second activity cannot be finished until
the first activity starts.
For example, let us say you have to move into a new home, and your old home has to be
demolished. In this case, you cannot move to your new home until it is ready. Hence, the
second activity (construction of new home) must be finished before the first activity starts
(you start moving into a new home); i.e. if you are moving into your new home, you cannot
start vacating your old home until the new house is completely ready.
2. Dependency determination
Dependencies are well-defined as connections among the activities that decide the sequence
in which project activities should be executed. Dependency is a technique used in identifying
the appropriate type of dependency used to create the relationship between two activities. The
activities are termed as predecessor (which refers to the first activity) and successor (the
activity that precedes the first).There are numerous types of dependencies: mandatory and
discretionary, internal and external, or some combination of these dependencies.
a) Mandatory dependencies
Mandatory Project Dependencies are legally or contractually required. They are, sometimes,
inherent in the nature of the work like physical limitation. Mandatory dependencies are also
commonly described as Hard logic.
Consider 2 activities A and B. If B has a Mandatory Dependency on A then it means action
on B cannot be performed until Action on A has been completed.
For example, work on the first floor (Activity B) cannot begin until the foundation of the
building (Activity A) is complete.
b) Discretionary dependencies
Discretionary Project Dependencies are defined by the Project Team. There could be more
than one way to define a sequence between 2 activities. The Project Team may prefer one
sequence over the other. The team would choose their preferred sequence because of best
practices or lessons learned from prior experiences. These are also called Preferred Logic,
Preferential Logic or Soft Logic.
Consider 2 activities A and B. A and B can be independently performed or one can be
performed after the other. The Project Team can choose to make B dependent on A.
For example, the team may choose to build the door and window frames before the full
structure of the wall is in place.
c) External dependencies
External Project Dependencies are defined between non-project Activities and project
activities. The non-project activities are done by people who are external to the Project Team
e.g. representatives from Client’s organization, Vendors’ organization or any other external
groups. The project activities, on the other hand, are done by the Project Team. The Project
Team usually does not have control over non-project activities.
Consider 2 activities A and B. If B has an External Dependency on A then it would signify
that B is a project activity while A is a non-project activity.
For example if construction work has to be started, the building plans has to approve by the
client’s side.
d) Internal dependencies
Internal Project Dependencies are defined between two project activities. The Project Team,
usually, has complete control over project activities.
Consider 2 activities A and B. If B has an Internal Dependency on A then it would signify
that both A and B are project activities.
For example, installing drywall must be completed before painting the wall can begin. This
is an example of an internal dependency because both tasks are part of the project. In this
case, it is also mandatory because it is based on a physical limitation. It is not possible to
paint the wall before it is dry-walled.