Lesson 1: Introduction to Project Management

1. What Is a Project?

A project is a temporary, unique endeavour undertaken to create a specific product, service, or result.

Key characteristics of a project:

• Temporary – It has a clear start and end date.
• Unique output – It delivers something that did not exist in exactly the same way before (a system, a building, a new process, a campaign, etc.).
• Progressive elaboration – You don’t know everything at the beginning; details become clearer as the project moves forward.
• Resources and constraints – Projects use limited time, people, and money, and must work within constraints (scope, budget, quality, etc.).

Examples of projects:

• Implementing a new IT system for a company
• Organising a conference or event
• Building a shopping mall
• Launching a new product
• Developing a mobile app

1.1 Projects vs Operations

It’s important to distinguish between projects and operations:

Most organisations run projects to change or improve things, while operations keep the business running day-to-day.

2. Why Project Management Exists

Project management is the application of knowledge, skills, tools and techniques to project activities to meet project requirements.

Good project management helps to:

• Deliver the agreed scope (what needs to be done)
• Meet deadlines and milestones
• Control costs and avoid overspending
• Maintain quality and compliance
• Manage risks and issues
• Coordinate people, communication and expectations

Without structured project management, organisations experience:

• Missed deadlines
• Budget overruns
• Confused responsibilities
• Unhappy clients and stakeholders

3. The Triple Constraint (Iron Triangle)

Every project works within a balance of three primary constraints:

1. Scope – What must be delivered? (features, requirements, deliverables)
2. Time – By when must it be delivered? (schedule, milestones, deadlines)
3. Cost – How much can be spent? (budget, labour, materials, tools)

At the centre sits Quality.
Any change in one constraint affects the others:

• If scope increases, time and cost usually increase.
• If time is reduced, either scope must be reduced or cost/resources increased.
• If budget is cut, you may need to reduce scope or extend timelines.

A key job of the project manager is to manage this balance and communicate trade-offs clearly.

4. The Project Life Cycle

Although different methodologies (Agile, Waterfall, Hybrid) exist, the project life cycle generally includes five stages:

1. Initiation

   • Defining the need or opportunity

   • Creating a high-level business case

   • Appointing a project manager and sponsor

   • Approving the project to move forward

2. Planning

   • Defining scope in detail

   • Creating the work breakdown structure (WBS)

   • Building schedules and timelines

   • Estimating costs and budgets

   • Planning resources, communication, risk, quality, procurement, etc.

3. Execution

   • Performing the project work

   • Coordinating people and resources

   • Communicating with stakeholders

   • Managing suppliers and contractors

4. Monitoring and Control

   • Tracking progress against the plan

   • Measuring performance (time, cost, scope, quality)

   • Managing change requests

   • Handling risks and issues

5. Closure

   • Completing all project work and deliverables

   • Obtaining client or stakeholder acceptance

   • Releasing resources

   • Capturing lessons learned

   • Closing contracts and documentation

These stages are not always perfectly linear; sometimes they overlap or repeat, but they provide a clear structure for controlling the project.

5. Key Roles in a Project

Projects involve several important roles:

• Project Sponsor

  • Senior person who champions the project

  • Provides funding, strategic direction and decision-making authority

• Project Manager

  • Plans, executes, monitors and closes the project

  • Manages the team, budget, schedule, risks and communication

  • Acts as the main point of contact between stakeholders

• Project Team Members

  • Carry out technical tasks and produce deliverables

• Stakeholders

  • Anyone affected by the project or its outcome

  • Can be internal (staff, management) or external (clients, suppliers, regulators)

• Customers / End Users

  • People who will use the project’s final product or service

A successful project depends on clear roles and responsibilities and good collaboration between these parties.

6. Organisational Structures and Their Impact

The way an organisation is structured affects how projects are run and how much authority the project manager has.

1. Functional Organisation

   • Company is divided by departments (HR, Finance, IT, etc.)

   • Project work is done inside departments

   • Functional managers have more authority than the project manager

   • Project manager role may be part-time or coordination only

2. Matrix Organisation

   • Combination of functional and projectized

   • Staff report to both a functional manager and a project manager

   • Can be weak, balanced or strong, depending on who has more authority

3. Projectized Organisation

   • Most resources are organised around projects

   • Project managers have high authority over budget, people and decisions

   • Teams may be dedicated to projects full time

Understanding the organisation structure helps the project manager know:

• How to request resources
• Who makes which decisions
• How to escalate issues

7. The Project Environment: Internal and External Factors

Projects do not happen in isolation. They are influenced by:

Internal Factors:

• Company culture and values
• Internal policies and procedures
• Available skills and capacity
• Existing technology and systems
• Management support

External Factors:

• Legislation and regulations
• Industry standards
• Market conditions and competition
• Political and economic factors
• Environmental and social expectations

The project manager must monitor these factors, because they often create:

• Risks (things that might go wrong)
• Opportunities (things that can benefit the project)

8. Core Competencies of a Project Manager

A project manager needs both technical and soft skills:

Technical / Process Skills

• Planning and scheduling
• Cost estimation and budgeting
• Risk identification and analysis
• Reporting and documentation
• Understanding of project management methodologies (e.g. PMBOK, Agile)

Soft / People Skills

• Communication (verbal, written, presentation)
• Leadership and motivation
• Conflict management and negotiation
• Problem-solving and critical thinking
• Decision-making under pressure
• Stakeholder management and emotional intelligence

Strong project managers are able to balance people, processes, and results.

9. Key Terms Glossary (For Learners)

You can include this as a quick reference at the bottom of the lesson:

• Project – Temporary endeavour to create a unique result.
• Project Management – Application of knowledge, skills, tools and techniques to meet project requirements.
• Stakeholder – Any person or group affected by the project or its outcome.
• Scope – The work that must be done to deliver the project.
• Deliverable – A specific, measurable output of the project.
• Milestone – A significant point or event in the project schedule.
• Risk – An uncertain event that can have a positive or negative effect on the project.

🎯 Lesson Outcomes 

By the end of this lesson, learners should be able to:

1. Define a project and explain how it differs from ongoing operations.
2. Describe why structured project management is necessary in organisations.
3. Explain the Triple Constraint (scope, time, cost) and its relationship to quality.
4. List and describe the main stages of the project life cycle.
5. Identify key project roles and their responsibilities.
6. Explain how organisational structures and the project environment influence projects.
7. Recognise the core competencies required of an effective project manager.