when i think of a hammock, the first thing that comes to mind is a hammock hanging in the nice cool breeze between two tall palm trees in the caribbean.
in an article written by patrick weaver “the origins of hammocks and ladders”, published in the pm world journal, we get a glimpse of the origins of hammocks and why they were created in the first place.
a hammock is an activity that hangs between two activities in a schedule. hammocks do not have a manually set duration, instead the duration is calculated based on the duration of the two points from which is hangs. hammocks were created to develop high level summary reports of the overall project – like a summary. based on patrick’s research, a group of researchers in the uk (including our friend raf dua) created the concept of skeletonisation in the 1960’s.
this process, of which we have no detail, allowed schedulers to reduce the volume of data being inputted into the mainframe leading to substantial savings on computing costs considering how expensive it was to run a mainframe computer in the 60s and 70s. hammocks were used as a part of this process.
in connection to level of efforts in primavera p6, a hammock can also be used to convey overhead 世界杯时间比赛时间 and costs like project management efforts and quality inspections for a certain area of the schedule without affecting the whole project.
source: origins of hammocks and ladders featured paper
as we develop more into a digital age, the powers of computers are virtually limitless and documenting a large volume of data isn’t a problem anymore. regardless hammocks are still relevant and will remain valuable in the scheduling and planning world.
read the full article at the pm world journal website.
for more of level of efforts check out these articles:
- use a level of effort to add work stoppage info to a project and still track to your primavera baseline
- setting up loes and resource loading them
