Project Planning, Design & Implementation β Project Planning and Scheduling, NEC licence examination syllabus (Nepal Engineering Council).
Project Classifications
What makes something a project rather than ordinary work β and why the distinction changes how it must be managed.
π Where this lives: The distinction matters enormously in practice because the two kinds of work fail differently. A factory production line that goes wrong has been through the same cycle a thousand times, so the fault is findable and fixable by comparison with what worked yesterday. A project going wrong has no such baseline β it is being done for the first time, so there is nothing to compare it to. That is why projects need explicit planning, monitoring and control machinery that routine operations can manage without. Search "project versus operations management characteristics".
What a project is
A PROJECT IS A TEMPORARY ENDEAVOUR UNDERTAKEN TO CREATE A UNIQUE
PRODUCT, SERVICE OR RESULT. (PMI definition)
THE DEFINING CHARACTERISTICS β the standard list, and each has a
managerial consequence:
1. TEMPORARY β a definite beginning and a definite end. The
end arrives when the objectives are met, when it becomes
clear they cannot be met, or when the need disappears.
CONSEQUENCE: the team is assembled and disbanded, so
staffing, knowledge retention and handover are permanent
problems.
2. UNIQUE β the output has not been produced before in exactly
this form. Two houses on the same drawing still differ in
site, ground, weather and crew.
CONSEQUENCE: ESTIMATES ARE FORECASTS, NOT MEASUREMENTS, and
therefore uncertain.
3. PROGRESSIVE ELABORATION β the definition sharpens as work
proceeds. Early estimates are necessarily coarse.
4. RESOURCE-CONSTRAINED β limited money, people, equipment and
time.
5. SINGLE POINT OF RESPONSIBILITY β a project manager
accountable for the whole.
6. CROSS-FUNCTIONAL β draws people from several departments or
organisations, who do not normally report to the project
manager.
7. INVOLVES RISK AND UNCERTAINTY, in proportion to its
novelty.
PROJECT VERSUS OPERATIONS β the comparison examiners ask for:
PROJECT OPERATIONS
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
duration TEMPORARY, defined ONGOING, continuous
end
output UNIQUE REPETITIVE, identical
objective achieve the goal SUSTAIN the business
and CLOSE
team assembled, then permanent
DISBANDED
process evolving, planned standardised, refined
once over repetitions
risk HIGH β novelty lower β experience
example building a running a power
power plant plant
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
THE PATTERN: A PROJECT DELIVERS THE ASSET; OPERATIONS RUN IT.
Building a hospital is a project; treating patients in it is
an operation. The moment of handover is where one becomes the
other, and it is a notoriously badly managed transition.
THE TRIPLE CONSTRAINT (PROJECT MANAGEMENT TRIANGLE):
SCOPE
β± β²
β± QUALITYβ²
TIME ββββββ COST
THE THREE ARE INTERLOCKED: changing one forces a change in at
least one other, with quality sitting in the middle as what
suffers when the other three are squeezed.
"FASTER, CHEAPER, BETTER β PICK TWO" is the crude version,
and it is essentially correct. A client demanding a
compressed schedule at unchanged cost is, whether they know
it or not, asking for reduced scope or reduced quality.
MODERN TREATMENTS EXTEND IT to six: scope, time, cost,
quality, risk and resources.
The classifications
PROJECTS ARE CLASSIFIED SEVERAL WAYS, AND A QUESTION MAY ASK FOR
ANY OF THEM. THE USEFUL ORGANISING IDEA IS THAT EACH
CLASSIFICATION EXISTS BECAUSE IT PREDICTS SOMETHING ABOUT HOW THE
PROJECT MUST BE MANAGED.
ββ 1. BY SECTOR / OWNERSHIP ββββββββββββββββββββββββββββββββ
PUBLIC SECTOR β funded by government; roads, schools,
irrigation. Objectives include SOCIAL BENEFIT, so appraisal
uses economic (benefit-cost) analysis rather than purely
financial return, and procurement follows the Public
Procurement Act.
PRIVATE SECTOR β funded by firms; appraised on financial
return (NPV, IRR).
PUBLIC-PRIVATE PARTNERSHIP (PPP) β shared. Common in Nepal
for hydropower and transport, typically as BOOT (Build-
Own-Operate-Transfer): the private party finances and
operates for a concession period, then transfers the asset
to the state.
ββ 2. BY SIZE AND COMPLEXITY βββββββββββββββββββββββββββββββ
MINOR / SMALL, MEDIUM, MAJOR / MEGA PROJECTS.
MEGAPROJECTS (conventionally above USD 1 billion) are
treated as a category of their own because THEY FAIL
DIFFERENTLY: long durations, many stakeholders, political
exposure and a well-documented tendency to cost overrun.
ββ 3. BY NATURE OF WORK ββββββββββββββββββββββββββββββββββββ
CONSTRUCTION β buildings, roads, bridges, dams
MANUFACTURING β producing a physical product
RESEARCH AND DEVELOPMENT β the outcome itself uncertain,
so the schedule is least predictable
SOFTWARE / IT
MANAGEMENT / ORGANISATIONAL CHANGE
MAINTENANCE AND REHABILITATION
ββ 4. BY DEGREE OF NOVELTY β the most managerially useful βββ
DERIVATIVE β a small change to something existing. Low risk,
estimates reliable.
PLATFORM β a new generation of an existing family.
BREAKTHROUGH β genuinely new technology. HIGH RISK, and
conventional scheduling is least reliable precisely here.
R&D β outcome not guaranteed at all.
THE PRINCIPLE: PLANNING TECHNIQUES THAT WORK WELL FOR
DERIVATIVE PROJECTS WORK WORST FOR BREAKTHROUGH ONES, so
the choice of method should follow the novelty.
ββ 5. BY DELIVERY / CONTRACT ARRANGEMENT βββββββββββββββββββ
TRADITIONAL (DESIGN-BID-BUILD) β design completed, then
tendered, then built. Clear roles; slow; the designer and
builder are separate, so buildability problems surface
late.
DESIGN-BUILD (TURNKEY) β one contractor designs and builds.
Faster, single point of responsibility, less client
control over design detail.
EPC (Engineering, Procurement, Construction) β the standard
for industrial plant and power projects.
BOT / BOOT β as above, used for infrastructure concessions.
MANAGEMENT CONTRACTING and CONSTRUCTION MANAGEMENT.
ββ 6. BY URGENCY AND PRIORITY ββββββββββββββββββββββββββββββ
MANDATORY β legally or safety required; NO "DO NOTHING"
OPTION EXISTS, so the analysis compares costs only.
OPERATIONAL NECESSITY β required to keep the business
running.
STRATEGIC β expanding capacity or entering a market.
DISCRETIONARY β desirable but deferrable.
ββ 7. IN THE NEPALI CONTEXT ββββββββββββββββββββββββββββββββ
The National Planning Commission and the Ministry of Finance
classify public projects for budgeting and monitoring:
NATIONAL PRIDE PROJECTS β a designated set of strategically
important schemes (major hydropower, international
airports, large highways and irrigation) receiving
priority funding and high-level monitoring.
GAME CHANGER / TRANSFORMATIVE PROJECTS.
P1 / P2 / P3 PRIORITY CLASSES in the budget system,
determining which projects receive funds first when
revenue falls short β a real and frequently binding
constraint.
Projects are also classified by IMPLEMENTATION LEVEL β
federal, provincial or local β under the constitutional
division of responsibilities.
WHY CLASSIFY AT ALL β the concluding point:
CLASSIFICATION IS NOT AN ADMINISTRATIVE RITUAL. It
determines which appraisal method applies (financial or
economic), which procurement rules bind, how much
contingency is appropriate, what management structure suits,
and how much uncertainty the estimates carry.
A BREAKTHROUGH R&D PROJECT MANAGED WITH THE TOOLS OF A
DERIVATIVE CONSTRUCTION PROJECT WILL REPORT CONFIDENT
SCHEDULES THAT ARE MEANINGLESS. Matching the method to the
class is the practical purpose of the whole taxonomy.
Classification determines which appraisal method applies, which procurement rules bind, how much contingency is appropriate, and how far the estimates can be trusted. The consequence worth remembering: the planning techniques that work best on derivative projects work worst on breakthrough ones β so a novel project managed with routine tools will produce confident schedules that mean nothing.
π Go further: Megaprojects are treated as their own category because they fail with remarkable consistency. Bent Flyvbjerg's studies of several hundred large infrastructure projects worldwide found cost overruns to be the norm rather than the exception, with rail projects averaging roughly 45% over budget and the pattern showing no improvement across seven decades of supposedly better management technique. His explanation combines optimism bias β genuine underestimation of difficulty β with strategic misrepresentation, where promoters understate costs deliberately because an honest estimate would not be approved. The proposed remedy, reference class forecasting, is deliberately anti-analytical: ignore your own detailed estimate and use the actual outcomes of similar past projects. Search "Flyvbjerg megaproject cost overrun reference class forecasting".
π‘ Exam angle: give the definition of a project and its characteristics β temporary, unique, progressive elaboration β then produce the project versus operations comparison table, which is very commonly asked. Draw the triple constraint triangle with quality at the centre and explain the interlock. For classifications, be ready to give several schemes: by sector (public/private/PPP with BOOT), by size, by nature of work, by novelty (derivative to breakthrough) and by delivery method (design-bid-build, design-build, EPC). For Nepali context, mention National Pride Projects and the P1/P2/P3 priority classes. Close by explaining why classification matters managerially.
Syllabus points
Types/classifications of projects
Create a free account to tick topics off, take notes as you read, watch the video lessons and get a day-by-day study plan built around your exam date.