Draft:Project Business Management
Project Business Management (PBM)
From Wikipedia, the free encyclopedia
Project Business Management (PBM) is a management discipline focused on projects that also function as commercial transactions between legally independent organisations. It extends traditional project management by addressing the contractual, financial, governance and inter-organisational challenges that arise when customers, contractors and subcontractors jointly deliver a project across corporate boundaries.
Where to get help
How to improve a draft
You can also browse Wikipedia:Featured articles and Wikipedia:Good articles to find examples of Wikipedia's best writing on topics similar to your proposed article. Improving your odds of a speedy review To improve your odds of a faster review, tag your draft with relevant WikiProject tags using the button below. This will let reviewers know a new draft has been submitted in their area of interest. For instance, if you wrote about a female astronomer, you would want to add the Biography, Astronomy, and Women scientists tags. Editor resources
|
Submission declined on 16 November 2025 by Theroadislong (talk). This draft's references do not show that the subject meets Wikipedia's criteria for inclusion. The draft requires multiple published secondary sources that:
Declined by Theroadislong 4 months ago.
|
This draft's references do not show that the subject meets Wikipedia's criteria for inclusion for organizations and companies. The draft requires multiple published secondary sources that:
Declined by Patre23 5 months ago.
|
PBM is considered an emerging field, drawing increasing attention from researchers and practitioners as industries rely more heavily on inter-organisational project delivery. Its academic foundations stem from research on project-based firms, temporary multi-organisational arrangements, commercial governance, contracting and risk sharing in project settings.
History and evolution
Some ancient mega-projects demonstrate proto–project-business features. Archaeological evidence from the Old Kingdom site of Heit el-Ghurab near the Giza Plateau shows organised labour crews housed in a “workers’ town”, provisioned by the state, and engaged in building large pyramid structures.[1] Further studies indicate the workforce was supplied a diet high in cereals, meat and fruit, implying central logistical coordination rather than purely localised village labour.[2] While this example does not reflect contract-based, cross-corporate project business in the modern sense, it illustrates early forms of externally organised labour mobilisation for large-scale projects.
Later historical examples also demonstrate contract-based project delivery across organisational boundaries. In the Roman Republic and Empire, major public works such as roads, aqueducts, temples and harbours were routinely delivered through competitive contracts administered by the censors. Private contractors (redemptores) bid for these projects, provided performance guarantees and frequently subcontracted portions of the work, forming temporary private consortia for large construction tasks.[3] The Roman contracting system (locatio conductio) included payment schedules, penalties for non-performance and detailed specifications, illustrating a well-documented premodern form of project delivery involving external organisations rather than internal state labour.[4]
These historical cases illustrate that externally organised project delivery has deep roots. However, the formalised, cross-corporate structures associated with modern Project Business Management emerged only in the late twentieth century.
The modern origins of PBM can be traced to the late twentieth century, when organisations in sectors such as construction, engineering, defence and infrastructure increasingly outsourced major project components to external contractors. This shift produced complex commercial relationships between clients, contractors and supply chain partners, prompting researchers to examine how inter-organisational projects differ from internal project management.
During the 1990s and 2000s, studies on project-based firms, temporary multi-organisational forms and complex product systems highlighted the importance of commercial and contractual factors in project delivery. Work by Artto, Wikström, Davies, Hobday, Winch and others advanced understanding of how projects function as business transactions rather than solely technical endeavours. In parallel, the spread of alliance contracting demonstrated collaborative multi-party governance models.
Definition and scope
Project Business Management addresses projects that function simultaneously as commercial undertakings. Key characteristics include:
- execution by two or more legally separate organisations
- contracts defining scope, responsibilities, risk allocation and financial flows
- revenue generation for contractors and financial exposure for customers
- complex governance structures involving multiple corporate entities
- inter-organisational coordination and relationship management
- commercial and financial decision-making alongside technical delivery
Because Project Business involves contractual transactions between legally independent entities, it contributes to gross domestic product (GDP) as recorded in national accounts. By contrast, purely internal projects conducted within a single organisation do not generate external economic transactions and therefore do not directly contribute to GDP.
PBM complements, rather than replaces, traditional project management by adding focus on contract management, financial governance, cross-corporate collaboration, commercial risk and business-model alignment.
Comparison with related disciplines
PBM overlaps with but is distinct from several other disciplines:
- Project management: focuses on internal scope, schedule and cost; PBM emphasises inter-organisational relationship and commercial management.
- Contract management: deals with contract lifecycle and compliance; PBM integrates contract issues into overall project delivery.
- Procurement: focuses on acquiring goods and services; PBM concerns the entire project transaction.
- Supply chain management: addresses flows of materials and information; PBM examines the project as a temporary business network.
- Programme management: coordinates multiple related projects; PBM focuses on cross-corporate business aspects of individual projects.
Types of project business
Project Business appears in several forms, including:
- Customer projects: contractors deliver projects for paying clients.
- Multi-tier subcontracting: prime contractors rely on subcontractors for major portions of delivery.
- Joint ventures and consortia: multiple organisations share ownership, risk and delivery responsibilities.
- Project alliances: collaborative models with collective risk–reward sharing and unanimous decision-making.
- Framework contracts: long-term agreements enabling repeated project engagements.
- Long-term service projects: recurring projects delivered under ongoing commercial arrangements.
Academic foundations
Early academic work emphasised the inter-organisational nature of commercial projects. Artto and Wikström defined “project business” as project activity extending beyond internal initiatives and becoming a commercial relationship between legally separate organisations.[5]
Further contributions explored service components,[6] business models,[7] and complex product systems.[8]
Morris highlighted the importance of front-end definition and contractual governance,[9] while Winch examined information-processing constraints in multi-firm projects.[10]
Research on temporary multi-organisational forms illuminated social and organisational mechanisms in cross-corporate project settings.[11]
Project typology work further distinguished internal from cross-corporate projects, emphasising differences in governance and commercial logic.[12]
Building on this stream of research, Lehmann published a book-length synthesis of Project Business Management that defines PBM as the management of cross-corporate projects performed under contract between legally independent organisations.[13]
Heptinstall and Bolton analysed collaborative alliance contracting in a practitioner-oriented guide outlining governance structures and risk–reward principles.[14]
Hornby emphasised the growing commercial skill requirements in project delivery.[15]
Governance models
Governance mechanisms in PBM vary substantially and may include:
- bilateral contract governance between client and contractor
- multi-tier governance overseeing subcontractor chains
- alliance governance with collective risk–reward pools
- joint venture or consortium governance with shared ownership
- client-led steering committees, common in public-sector projects
Academic research on project alliances illustrates how collaborative governance models can influence project outcomes, even though alliancing represents only one of many approaches within the broader field of Project Business Management. A study of 61 public-sector infrastructure alliances in Australia and New Zealand reported that leadership–operations communication and relationship-based trust were decisive factors for cost, schedule and value-for-money performance.[16] The same study noted that alliance governance emphasised collective performance indicators rather than individual contract positions, reflecting an alignment of incentives around shared project objectives. Although these findings are context-limited — applying specifically to public-sector infrastructure in Australasia, where alliancing had seen extensive adoption — they provide an example of how cross-corporate governance structures can affect inter-organisational project performance.
Contemporary practitioners have also critiqued traditional contract forms. Heptinstall, an associate professor of project management at the University of Birmingham, has argued publicly that fixed-price contracting often creates an illusion of cost certainty and that multi-party alliance models may yield more reliable outcomes on complex projects.[17]
Risk in Project Business
Risk in PBM includes categories less prominent in internal project management:
- contractual and legal risk
- financial and liquidity risk
- counterparty risk
- commercial and market risk
- supply chain instability
- claims and disputes
- opportunistic behaviour
- information asymmetry and moral hazard
Target cost contracts, incentive schemes and alliance models may mitigate but do not eliminate such risks.
Methods and practices
Common PBM practices include:
- contract structuring and negotiation
- bid/no-bid decisions
- development of project business cases
- cash-flow and liquidity management
- commercial performance measurement
- interface management across organisations
- change and claim management
- collaborative contracting and incentive structures
Traditional techniques such as earned value management often require adaptation to reflect contractual realities.
Economic significance
Project Business constitutes a substantial share of economic activity in many countries, particularly where infrastructure, energy and industrial projects form major investment categories. Because PBM involves contractual payments between organisations, it contributes directly to GDP. Construction alone accounts for an estimated 13% of global GDP in industry analyses, with additional contributions from engineering, defence, technology and large-scale services.
Education and research landscape
PBM-related topics appear across university programmes in project management, operations management, construction management, supply chain management and industrial engineering. Research appears in journals including the International Journal of Project Management, Project Management Journal, Technovation and others.
Dedicated PBM education remains limited. Professional training is primarily offered through practitioner bodies and industry organisations.
Professionalisation and certification
Criticism and limitations
As an emerging discipline, PBM faces several challenges:
- limited academic visibility compared to established fields
- lack of consistent terminology
- significant reliance on practitioner sources
- overlap with procurement, contract management and supply chain management
- difficulty studying cross-corporate relationships empirically
- uneven adoption across industries
Case examples
PBM principles can be observed in:
- major infrastructure alliances in Australia
- transportation megaprojects such as Crossrail
- defence acquisition programmes with multi-tier contractor networks
- complex engineering projects in the energy sector
- large-scale outsourcing and service programmes
See also
- Project governance
- Contract management
- Project-based organisation
- Programme management
- Supply chain management
- Alliance contracting

LLM-generated pages with the below issues may be deleted without notice.
These tools are prone to specific issues that violate our policies:
Instead, only summarize in your own words a range of independent, reliable, published sources that discuss the subject.
See the advice page on large language models for more information.