why so many projects fail and how to fix it projects-fail-and-ho… · the assumption is that one...

1
The assumption is that one can predict the exact plan of the entire project from start to finish, and the more detailed the plan is, the more one can get individ- uals accountable for their local tasks, and in execution, all you need to do is control and report. Gantt's methodology was a breakthrough at its time as it allowed, for the first time, to plan activities and dependencies in projects. However, while in other management disciplines (such as manufacturing) methodologies kept improving and being updated to the mod- ern times and requirements, exact Gantt schedules are still a common way to manage projects today, and those exact schedules are the main reason for the mul- titasking effect. Unfortunately, "exact" sched- ules cannot be followed because uncertainties are unavoidable during execution. For example, tasks take longer than expected, vendors and subcontractors miss their deadlines, technical glitch- es occur, requirements change and expand, engineering designs might have to be redone, local or environmental condi- tions may cause delays, and issues can come up during inte- gration and testing of systems. As uncertainties unfold, delays start accumulating and the original schedules that had been so meticulously laid out become obsolete. Faced with both delays and a lack of schedules, individuals and teams involved in execu- tion have to decide on their own what to work on first. These priorities are set locally by team leads or even by the resources themselves, often based on who is screaming the loudest at the time, or which job is easier to finish. As these local priorities over- take the original plans, soon everyone is marching to a differ- ent drumbeat—and multitask- ing and chaotic execution is unavoidable. Work keeps getting interrupt- ed because everyone is waiting for someone else. Sometimes the required inputs—like technical data, drawings and customer approvals—are not available; at other times the inputs are all lined up but resources—like engineers, technicians, welders, pipe fitters, cranes are missing. Reducing multitasking to the minimum—realising uncer- tainties: In 1998, almost 100 years after Henry Gantt created his first chart, finally, a new method of managing project execution was invented by Dr. Eli Goldratt, known as 'Critical Chain'. Its breakthrough lies in keeping tasks and resources synchronised within and across projects, even in the face of uncertainties, without having to rely on exact schedules at all. Instead of communicating obsolete schedules, it calculates the impact of delays in execution and adjusts task priorities accordingly. Managers at all levels get a list of ready-to-work and upcoming tasks in the order of relative priority. These priori- ties are synchronised across the organisation so that multitask- ing and interruptions are held to a minimum, and projects get done fast and efficiently Since the theory was invented, it has been turned into a work- able methodology and has been adopted by a wide range of organisations around the world, allowing them to increase the execution rate of projects by 20- 50 per cent (see table). It is clear, that in today's uncer- tain world of project execution, where growth opportunity are in abundance, but skilled resources are scarce, companies can no longer rely on traditional project management. India should not import 100-year old methodologies, because it will just replicate the poor project success rates that have been achieved in other countries for so many years. Executives must adopt cutting edge project execution manage- ment techniques to maximise their growth opportunities. (Realization Technologies, Inc. is a premium provider of project execution services in US, Brazil and India. Kapil Gupta can be reached at 090-49988918 or pro- [email protected]) Projectmonitor, Mumbai, September 26-October 2, 2011 19 18 W hen a major project, such as a plant expan- sion, constructing a new refinery or build- ing a new bridge is late, the con- sequences can be much more serious than just cost overruns and contractual penalties. For the operator or owner of the infrastructure, every week that a project runs late is a week of lost revenues and profits. For the contractor, the longer a project takes, the longer resources remain tied up and unavailable to do new projects. Missing deadlines also undermine the contractor's credibility with cus- tomers and lessens the possibili- ty of winning future work. For India, delays in infrastruc- ture projects translates into delays in lifting millions out of poverty and a severe damage to India's economy. A 2009 McKin- sey report suggests that if rate of project execution in India does not dramatically improve, India will bear a direct loss of $200B of its GDP by 2017. Despite the significant bene- fits of accelerating projects and delivering them on time, proj- ects continue to be overdue, over budget, over and over again. Harvard Business Review reports that construc- tion projects fail at an alarming rate—more than 50 per cent by some estimates. No one doubts that schedule and cost overruns are not only devastating but also common in projects. The real question is, "What, if anything, can we do about it?" Blaming factors outside our control is pointless: There are many causes for late and failed projects. One common category of culprits is industry-level issues e.g., slow pre-tendering approval process, shortfall in awarding projects, below par design and engineering skills and land acquisition delays. Another usual refrain is that there are too many unknowns and every project is late because of project-specific surprises. True, but we don't have to be helpless or wait for the industry or the government to resolve these problems. There are major ineffi- ciencies in all projects that can be plugged by changing how we execute projects, allowing us to do projects 20-50 per cent faster. Interruptions and Multitask- ing—the twin killers of speed and productivity in projects: Ask anyone who is involved in any type of project, and they would tell you that they can never finish a task without get- ting interrupted. These interruptions happen because: The required inputs and sup- porting resources are not available when needed because task priorities across the organisations are not syn- chronised; Managers and experts cannot provide decisions and approvals in a timely manner because they have become a bottleneck; and Higher priority tasks require people to drop whatever they are doing. When tasks are interrupted, people are forced to switch to either higher priority tasks or to tasks on which they can do some work. Switching between tasks without completing them causes people to lose focus and make them inefficient and causes tasks to take longer. The effect is intensified when it comes to equipment and machines e.g.: cranes. Compare the performance of a crane that is focused on one work-front at a time, to one that needs to be used on five different work- fronts at the same time and the damaging impact of multitask- ing is immediately understood. Multitasking and interrup- tions affect not just those who experience them. Downstream resources end up waiting longer, and under the pressure to get going they start their tasks out of sequence. These tasks cannot make real progress as they depend on the original delayed tasks, and so they get stuck; and additional tasks are opened "in the meanwhile". Very soon everyone is working on many tasks and makes only a little progress on each. Quality too is a major collateral damage of multitasking. When resources are constantly inter- rupted, they lose concentration and workmanship suffers. Qual- ity is also impacted when resources can no longer wait for the required inputs and deci- sions and proceed with their tasks, only to find later that they have made erroneous assump- tions and their work needs to be redone. Multitasking and interrup- tions easily account for up 20-50 per cent wasted capacity in proj- ects. If this capacity can be saved, projects can be done faster and with better quality. Traditional project manage- ment induces multitasking: The common way to manage projects was invented in the 1910s by Henry Gantt. It relies on detailed task schedules with "exact" start and end dates. ANTHONY AZAVEDO For India, delays in infrastructure projects translates into delays in lifting millions out of poverty and a severe damage to India's economy, writes Kapil Gupta, Vice President, Strategic Services, Realization Technologies, Inc. EXAMPLE OF RESULTS IN EPC PROJECTS Projects Description Before After Design and manufacturing of oil and gas platforms Design Engineering: 15 mos. Production Engineering: 9 mos. Fabrication & Assembly: 8 mos. Design Engineering: 9 mos. Production Engineering: 5 mos. Fabrication & Assembly: 8 mos. 22% height labor productivity. Expansion of a mine along with a railway and port facility to increase iron ore delivery capacity 22,800 man-hours of engineering design work had to be completed in 8 months. Historical delay of 2 weeks and man-hours overruns of 20% Project was finished 3 weeks early. Productivity increased by 25% with only 19,500 man-hours needed. Overhaul and upgrade of a melter and process plant for a nicked mine Projects were consistently late and over budget Melter was delivered on time; Plant overhaul was delivered 1 day early with 10% added to the scope. Cost was 96% of planned budged. Why so many projects fail and how to fix it DOING PROJECTS RIGHT 18-19] Construction Special_Final.qxp 9/23/2011 7:05 PM Page 18

Upload: vonga

Post on 06-Mar-2018

216 views

Category:

Documents


0 download

TRANSCRIPT

The assumption is that one canpredict the exact plan of theentire project from start to finish,and the more detailed the planis, the more one can get individ-uals accountable for their localtasks, and in execution, all youneed to do is control and report.

Gantt's methodology was abreakthrough at its time as itallowed, for the first time, to planactivities and dependencies inprojects. However, while inother management disciplines(such as manufacturing)methodologies kept improvingand being updated to the mod-ern times and requirements,exact Gantt schedules are still acommon way to manage projectstoday, and those exact schedulesare the main reason for the mul-titasking effect.

Unfortunately, "exact" sched-ules cannot be followed becauseuncertainties are unavoidableduring execution. For example,tasks take longer than expected,vendors and subcontractors misstheir deadlines, technical glitch-es occur, requirements changeand expand, engineeringdesigns might have to be redone,local or environmental condi-tions may cause delays, andissues can come up during inte-gration and testing of systems.

As uncertainties unfold,delays start accumulating andthe original schedules that had

been so meticulously laid outbecome obsolete.

Faced with both delays and alack of schedules, individualsand teams involved in execu-tion have to decide on theirown what to work on first.These priorities are set locallyby team leads or even by theresources themselves, oftenbased on who is screaming theloudest at the time, or which jobis easier to finish.

As these local priorities over-take the original plans, sooneveryone is marching to a differ-ent drumbeat—and multitask-ing and chaotic execution isunavoidable.

Work keeps getting interrupt-ed because everyone is waitingfor someone else. Sometimes therequired inputs—like technicaldata, drawings and customerapprovals—are not available; atother times the inputs are alllined up but resources—likeengineers, technicians, welders,pipe fitters, cranes are missing.

Reducing multitasking to the

minimum—realising uncer-

tainties: In 1998, almost 100years after Henry Gantt createdhis first chart, finally, a newmethod of managing projectexecution was invented by Dr.Eli Goldratt, known as 'CriticalChain'. Its breakthrough lies inkeeping tasks and resourcessynchronised within and across

projects, even in the face ofuncertainties, without having torely on exact schedules at all.

Instead of communicatingobsolete schedules, it calculatesthe impact of delays in executionand adjusts task prioritiesaccordingly. Managers at alllevels get a list of ready-to-workand upcoming tasks in the orderof relative priority. These priori-ties are synchronised across theorganisation so that multitask-ing and interruptions are held toa minimum, and projects getdone fast and efficiently

Since the theory was invented,it has been turned into a work-able methodology and has beenadopted by a wide range oforganisations around the world,allowing them to increase theexecution rate of projects by 20-50 per cent (see table).

It is clear, that in today's uncer-tain world of project execution,where growth opportunity are inabundance, but skilledresources are scarce, companiescan no longer rely on traditionalproject management. Indiashould not import 100-year old

methodologies, because it willjust replicate the poor projectsuccess rates that have beenachieved in other countries forso many years.

Executives must adopt cuttingedge project execution manage-ment techniques to maximisetheir growth opportunities.

(Realization Technologies, Inc.

is a premium provider of project

execution services in US, Brazil

and India. Kapil Gupta can be

reached at 090-49988918 or pro-

[email protected])

Projectmonitor, Mumbai, September 26-October 2, 2011 1918

When a major project,such as a plant expan-sion, constructing anew refinery or build-

ing a new bridge is late, the con-sequences can be much moreserious than just cost overrunsand contractual penalties.

For the operator or owner of theinfrastructure, every week that aproject runs late is a week of lostrevenues and profits. For thecontractor, the longer a projecttakes, the longer resourcesremain tied up and unavailableto do new projects. Missingdeadlines also undermine thecontractor's credibility with cus-tomers and lessens the possibili-ty of winning future work.

For India, delays in infrastruc-ture projects translates intodelays in lifting millions out ofpoverty and a severe damage toIndia's economy. A 2009 McKin-sey report suggests that if rate ofproject execution in India doesnot dramatically improve, Indiawill bear a direct loss of $200B ofits GDP by 2017.

Despite the significant bene-fits of accelerating projects anddelivering them on time, proj-ects continue to be overdue,over budget, over and overagain. Harvard BusinessReview reports that construc-tion projects fail at an alarming

rate—more than 50 per cent bysome estimates.

No one doubts that scheduleand cost overruns are not onlydevastating but also common inprojects. The real question is,"What, if anything, can we doabout it?"

Blaming factors outside our

control is pointless: There aremany causes for late and failedprojects. One common categoryof culprits is industry-levelissues e.g., slow pre-tenderingapproval process, shortfall inawarding projects, below pardesign and engineering skillsand land acquisition delays.Another usual refrain is thatthere are too many unknownsand every project is late becauseof project-specific surprises.

True, but we don't have to behelpless or wait for the industry orthe government to resolve theseproblems. There are major ineffi-ciencies in all projects that can beplugged by changing how weexecute projects, allowing us todo projects 20-50 per cent faster.

Interruptions and Multitask-

ing—the twin killers of speed

and productivity in projects:

Ask anyone who is involved in

any type of project, and theywould tell you that they cannever finish a task without get-ting interrupted.

These interruptions happen

because:

� The required inputs and sup-porting resources are notavailable when neededbecause task priorities acrossthe organisations are not syn-chronised;

� Managers and experts cannotprovide decisions andapprovals in a timely mannerbecause they have become abottleneck; and

� Higher priority tasks requirepeople to drop whatever theyare doing.When tasks are interrupted,

people are forced to switch toeither higher priority tasks or totasks on which they can do somework. Switching between taskswithout completing them causespeople to lose focus and makethem inefficient and causestasks to take longer.

The effect is intensified when

it comes to equipment and

machines e.g.: cranes. Comparethe performance of a crane thatis focused on one work-front at atime, to one that needs to beused on five different work-fronts at the same time and thedamaging impact of multitask-ing is immediately understood.

Multitasking and interrup-

tions affect not just those whoexperience them. Downstreamresources end up waiting longer,and under the pressure to getgoing they start their tasks out ofsequence. These tasks cannotmake real progress as theydepend on the original delayedtasks, and so they get stuck; andadditional tasks are opened "inthe meanwhile".

Very soon everyone is workingon many tasks and makes only alittle progress on each.

Quality too is a major collateraldamage of multitasking. Whenresources are constantly inter-rupted, they lose concentrationand workmanship suffers. Qual-ity is also impacted whenresources can no longer wait forthe required inputs and deci-sions and proceed with theirtasks, only to find later that theyhave made erroneous assump-tions and their work needs to beredone.

Multitasking and interrup-tions easily account for up 20-50per cent wasted capacity in proj-ects. If this capacity can besaved, projects can be donefaster and with better quality.

Traditional project manage-

ment induces multitasking: Thecommon way to manage projectswas invented in the 1910s byHenry Gantt. It relies ondetailed task schedules with"exact" start and end dates.

ANTHONY AZAVEDO

For India, delays in

infrastructure projects

translates into delays in

lifting millions out of

poverty and a severe

damage to India's economy,

writes KKaappiill GGuuppttaa,,

Vice President, Strategic

Services, Realization

Technologies, Inc.

EXAMPLE OF RESULTS IN EPC PROJECTS

Projects Description Before After

Design and manufacturing of oil and gas

platforms

Design Engineering: 15 mos. Production

Engineering: 9 mos.

Fabrication & Assembly: 8 mos.

Design Engineering: 9 mos.

Production Engineering: 5 mos.

Fabrication & Assembly: 8 mos. 22% height

labor productivity.

Expansion of a mine along with a railway and

port facility to increase iron ore delivery

capacity

22,800 man-hours of engineering design

work had to be completed in 8 months.

Historical delay of 2 weeks and man-hours

overruns of 20%

Project was finished 3 weeks early.

Productivity increased by 25% with only

19,500 man-hours needed.

Overhaul and upgrade of a melter and

process plant for a nicked mine

Projects were consistently late and over

budget

Melter was delivered on time; Plant overhaul

was delivered 1 day early with 10% added to

the scope.

Cost was 96% of planned budged.

Why so many projectsfail and how to fix it

DOING PROJECTS RIGHT

18-19] Construction Special_Final.qxp 9/23/2011 7:05 PM Page 18