The internal and external context in which a project operates, including organisational strategy, culture, resources and wider political, economic, social, technological, legal and environmental influences.

A tool for scanning the external environment of a project across six dimensions: Political, Economic, Social, Technological, Legal and Environmental.

A document and ongoing justification that explains why a project is desirable, viable and achievable, summarising options, costs, benefits, risks and strategic fit.

The role that owns the business case, ensures the project remains aligned with strategy and worth doing, and makes key investment decisions about starting, continuing or stopping the project.

What is Business case?

The justification for a project, describing why it should be undertaken, summarising options, costs, benefits, risks and alignment with strategy, and used to support investment decisions.

What is Project manager?

The role responsible for planning, executing and controlling the project to deliver agreed outputs within defined constraints, and for providing information to support business case decisions.

What is Project sponsor?

A senior role accountable for the project’s alignment to strategy and for owning the business case, including decisions to start, continue, change or stop the project.

Projects in Context: Operating Environment, Business Case and Success — APM PFQ Essentials with Citivirtual: Fast-Track to Project Fundamentals

Step 1 – Setting the Scene: Projects in Context

Why Context Matters

Projects do not live in a vacuum. They are chosen, shaped and judged by their environment: external forces, internal strategy, and the business case that says why they are worth doing.

Links to PFQ

This module supports PFQ by helping you: apply PESTLE to a project, understand the purpose and contents of a business case, and explain project success criteria vs success factors.

What You Will Do

Across the next steps you will break down project environment, build a simple business case view, and practice defining success in realistic project scenarios.

Step 2 – Project Environment: Internal vs External

What Is Project Environment?

Project environment is everything around a project that can affect it. PFQ highlights that this includes both internal and external influences on the project.

Internal Environment

Internal factors include strategy, structure, culture, policies and available resources. They come from within the organisation delivering the project.

External Environment

External factors include laws, regulations, competitors, customers, technology trends and social expectations. They sit outside the organisation but still affect projects.

A Quick Example

For a university IT project, internal drivers include the university’s student‑experience strategy; external drivers include UK GDPR, cyber threats and student expectations of mobile apps.

Step 3 – PESTLE: A Simple Tool to Scan the Environment

What Is PESTLE?

PESTLE is a simple tool to scan the external environment. It stands for Political, Economic, Social, Technological, Legal and Environmental influences on a project.

The Six Dimensions

P: Political, E: Economic, S: Social, T: Technological, L: Legal, E: Environmental. Use these headings as a checklist when thinking about external project context.

Why Use PESTLE?

PESTLE helps you spot external opportunities and threats early, feeding into the business case and risk management. It is especially useful at concept and feasibility stages.

PESTLE and Internal Factors

PESTLE focuses on external factors. Internal items like culture, structure and resources matter, but they are usually analysed with other tools, not PESTLE.

Step 4 – Apply PESTLE to a Simple Scenario

Use this quick exercise to practice PESTLE thinking.

Scenario:

Your local city council in 2026 wants to launch an e‑scooter rental scheme as a project. The aim is to reduce car use and support greener travel.

For each PESTLE category, jot down one factor that might affect the project. Use the prompts to guide you.

Political

Prompt: What might local or national politicians care about here?
Your example: `...`

Economic

Prompt: What is happening with funding, costs or the local economy?
Your example: `...`

Social

Prompt: How might residents feel about scooters? Who benefits or loses?
Your example: `...`

Technological

Prompt: What technology is needed to run and track scooters?
Your example: `...`

Legal

Prompt: What laws or regulations govern e‑scooters and road use?
Your example: `...`

Environmental

Prompt: How might this affect emissions, noise, or street clutter?
Your example: `...`

Self‑check (sample answers):

Political: Upcoming local elections make councillors keen to show green credentials.
Economic: High inflation increases purchase and maintenance costs.
Social: Some residents worry about safety on pavements.
Technological: Need a reliable app and GPS tracking to prevent theft.
Legal: National road‑traffic rules on where scooters can be ridden.
Environmental: Risk of discarded scooters creating street waste.

Compare your ideas with these. The goal is not to “match” them, but to think systematically across all six PESTLE areas.

Step 5 – The Business Case: Why This Project, Now?

Purpose of the Business Case

The business case explains why a project should be done and whether it remains viable. It supports decisions about starting, continuing or stopping the project.

Three Core Questions

A good business case shows whether the project is desirable (benefits), viable (affordable) and achievable (deliverable with current capability and constraints).

Typical Contents

It usually covers: background and strategic fit, options analysis, recommended option, costs, benefits and disbenefits, risks and assumptions, and timescales.

Not One‑and‑Done

The business case should be reviewed and updated as the environment changes, for example when costs, technology or regulations shift during the project.

Step 6 – Example Business Case: University Learning App

The Scenario

Imagine a university project to develop a mobile learning app combining timetables, lecture recordings and assessments into one place.

Strategic Fit and Options

The project aligns with a digital‑learning strategy and responds to student feedback. Options include doing nothing, buying an off‑the‑shelf app, or developing one in‑house.

Costs, Benefits, Risks

The business case outlines development and support costs, expected benefits like higher satisfaction and reduced admin, plus risks such as integration challenges.

Link Back to Environment

Student expectations, technology trends and university strategy all shape this business case, showing how context influences project selection and justification.

Step 7 – Who Owns the Business Case? Sponsor vs Project Manager

Two Key Roles

PFQ separates the project sponsor and project manager, especially around the business case. They collaborate, but have different accountabilities.

Sponsor and the Business Case

The sponsor owns the business case, ensures strategic alignment, and decides whether the project should start, continue, change or stop.

Project Manager’s Role

The project manager plans and controls delivery, provides reliable information, and supports updates to the business case with realistic estimates and data.

Key PFQ Point

For PFQ, remember: ultimate ownership of the business case sits with the sponsor, not the project manager, even though both contribute to it.

Step 8 – Project Success: Criteria vs Success Factors

What Are Success Criteria?

Success criteria are measurable definitions of success. They answer: How will we know if this project is successful? They are the specific targets to be achieved.

Examples of Criteria

Examples include: finishing by a certain date, staying within budget, achieving defined performance levels, or hitting a target satisfaction score.

What Are Success Factors?

Success factors are the conditions or actions that increase the chance of success. They answer: What will help us to achieve those success criteria?

Examples of Factors

Examples include strong sponsor support, clear requirements, a skilled team, and effective stakeholder communication. They enable, but are not themselves the targets.

Step 9 – Quick Check: Criteria or Factor?

Test your understanding of project success criteria vs success factors.

Which of the following is a **project success criterion**, not a success factor?

The project team attends regular stakeholder workshops.
The project must reduce average customer waiting time by 20% within 3 months of go‑live.
The sponsor is highly engaged and removes organisational obstacles.
The organisation provides an experienced business analyst to support requirements gathering.

Show Answer

Answer: B) The project must reduce average customer waiting time by 20% within 3 months of go‑live.

Option 2 is a success **criterion** because it is a measurable target (reduce waiting time by 20% within 3 months). The others describe conditions or actions that help success happen, so they are success **factors**.

Step 10 – Flashcards: Key Terms Review

Use these cards to review key PFQ terms from this module.

Project environment: The internal and external context in which a project operates, including organisational strategy, culture, resources and wider political, economic, social, technological, legal and environmental influences.
PESTLE analysis: A tool for scanning the external environment of a project across six dimensions: Political, Economic, Social, Technological, Legal and Environmental.
Business case: A document and ongoing justification that explains why a project is desirable, viable and achievable, summarising options, costs, benefits, risks and strategic fit.
Project sponsor: The role that owns the business case, ensures the project remains aligned with strategy and worth doing, and makes key investment decisions about starting, continuing or stopping the project.
Project success criteria: The measurable definitions of project success that answer 'How will we know if the project is successful?' such as time, cost, quality and benefit targets.
Project success factors: The conditions, capabilities or actions that increase the likelihood of meeting the success criteria, such as strong leadership, clear requirements and effective communication.

Key Terms

Business case: The justification for a project, describing why it should be undertaken, summarising options, costs, benefits, risks and alignment with strategy, and used to support investment decisions.
PESTLE analysis: A structured framework for examining Political, Economic, Social, Technological, Legal and Environmental factors that may impact a project.
Project manager: The role responsible for planning, executing and controlling the project to deliver agreed outputs within defined constraints, and for providing information to support business case decisions.
Project sponsor: A senior role accountable for the project’s alignment to strategy and for owning the business case, including decisions to start, continue, change or stop the project.
Project environment: The combination of internal organisational context and external influences that affect how a project is chosen, planned and delivered.
Project success factors: Key conditions or practices that increase the probability of achieving the success criteria, such as competent teams, engaged stakeholders and effective governance.
Project success criteria: Agreed, measurable statements that define what successful project delivery looks like, often covering time, cost, quality, scope and benefits.