📘 Chapter 4 – Defining the Project
🔹 Introduction
Defining a project is the first and most critical step in successful project
management.
A poorly defined project leads to confusion, scope creep, and failure.
The goal of this stage is to establish a clear agreement on what will be done, by
whom, for whom, and within what limits.
This chapter focuses on project definition documents, objectives, scope, and
stakeholder alignment.
🔹 Why Project Definition Matters
It sets the foundation for planning, scheduling, and execution.
Ensures everyone understands the purpose and boundaries of the project.
Prevents miscommunication between sponsors, managers, and team members.
Allows accurate estimation of time, cost, and resources.
Defines success criteria (how the project’s outcome will be judged).
🔹 Main Elements of Project Definition
1. Project Objectives – What the project is supposed to achieve.
2. Project Scope – What is included and excluded from the project.
3. Project Deliverables – The measurable outcomes or products produced.
4. Milestones – Key events or checkpoints.
5. Technical Requirements – Performance or design constraints.
6. Limits and Exclusions – Clarifies what is not part of the work.
7. Reviews and Approvals – Defines who signs off and when.
✅ Together, these form the Project Definition Document (PDD) or Project Charter.
🔹 Defining the Project Objectives
Objectives should be clear, specific, and measurable.
Must align with organizational strategy and stakeholder needs.
Objectives usually cover:
o Performance (quality) – What must be achieved.
o Time – When it must be done.
o Cost – Budget or resource limits.
Example:
“Develop and launch a new company website by July 2025 within a $60,000 budget.”
🔹 The SMART Criteria for Objectives
Letter Meaning Explanation
S Specific Clearly defines the goal.
M Measurable Quantifiable and trackable.
A Achievable Realistic given available resources.
R Relevant Supports the organization’s strategy.
T Time-bound Has a fixed deadline.
✅ SMART objectives keep the project focused and measurable.
🔹 Defining Project Scope
Scope describes the boundaries of work — what will and won’t be delivered.
Helps prevent scope creep — uncontrolled changes or additions to project tasks.
The Scope Statement includes:
o Purpose and justification.
o Major deliverables.
o Constraints (time, budget, technology).
o Assumptions.
o Exclusions (what’s out of scope).
Example:
“This project includes designing the company website layout but excludes hosting setup and
post-launch maintenance.”
🔹 Scope Creep
Occurs when additional features or tasks are added without approval or adjusting
time/cost.
Common causes:
o Poor initial definition.
o Stakeholders requesting “small” changes.
o Lack of change control system.
Prevented by:
o Clear documentation and communication.
o Formal approval process for all changes.
o Strong project leadership.
🔹 Project Deliverables and Milestones
Deliverables: tangible or intangible results of project activities (e.g., report,
prototype, app).
Milestones: key dates marking completion of major phases or tasks.
Help track progress and signal when management review is needed.
🔹 Stakeholder Identification and Analysis
Stakeholders are individuals or groups affected by the project or who can influence
it.
Key types:
o Internal: managers, employees, departments.
o External: customers, suppliers, government, community.
The Project Manager must:
1. Identify all stakeholders.
2. Analyze their needs and influence.
3. Develop a plan to manage their expectations.
✅ Early stakeholder engagement reduces resistance and increases commitment.
🔹 Creating the Project Charter
The Project Charter formally authorizes the project.
Acts as a contract between sponsor and project manager.
Includes:
o Project purpose and objectives.
o High-level scope and deliverables.
o Key stakeholders and responsibilities.
o Budget and schedule summary.
o Approval signatures.
Benefits:
Provides official authority to start the project.
Establishes alignment between sponsor and team.
Prevents misunderstandings about scope and priorities.
🔹 Project Priority Matrix
Used to clarify which of the triple constraints (time, cost, scope) is most important.
Constraint Options Meaning
Time Constrain / Enhance / Accept Is schedule fixed or flexible?
Cost Constrain / Enhance / Accept Is budget strict or adjustable?
Scope Constrain / Enhance / Accept Are features negotiable or must all be delivered?
Example:
Constrain: “Must finish by July.”
Enhance: “Can spend more to improve quality.”
Accept: “If needed, we can delay delivery slightly.”
✅ This matrix helps the project manager make trade-offs when changes occur.
🔹 The Statement of Work (SOW)
Detailed description of work to be done and results expected.
Often used in contracts or external projects.
Includes:
o Project objectives and scope.
o Deliverables and acceptance criteria.
o Schedule and milestones.
o Roles and responsibilities.
🔹 Work Breakdown Structure (WBS)
Breaks down the total project work into smaller, manageable pieces.
Hierarchical — top level shows overall project, lower levels show detailed tasks.
Helps with:
o Assigning responsibilities.
o Estimating time and cost.
o Tracking progress.
Levels Example:
1. Project: Build New Website
1.1 Design
1.2 Development
1.3 Testing
1.4 Launch
✅ “Decompose” large tasks into smaller, measurable work packages.
🔹 Risk and Assumptions
During definition, identify key risks (potential problems) and assumptions
(conditions believed true).
Documenting them early helps the team prepare mitigation plans.
Example: “Assume supplier delivers on time; risk = delay in shipment.”
🔹 Defining Success Criteria
Success = meeting objectives within scope, time, and budget + satisfying
stakeholders.
Modern project success also includes:
o Business value delivered.
o Long-term impact.
o Team learning and process improvement.
🧾 Key Terms and Definitions
Term Meaning
The process of clearly describing a project’s purpose, scope,
Project Definition
and outcomes.
Formal document authorizing the project and giving the PM
Project Charter
authority.
Defines the boundaries of what’s included/excluded in the
Scope Statement
project.
Specific, Measurable, Achievable, Relevant, Time-bound
SMART Objectives
goals.
Scope Creep Uncontrolled changes to project scope.
Deliverables Tangible or intangible project outputs.
Milestone Key point marking progress in the project timeline.
Stakeholders Individuals or groups with an interest in the project.
Priority Matrix Tool for setting constraint priorities (time, cost, scope).
Detailed description of work, deliverables, and acceptance
Statement of Work (SOW)
criteria.
Work Breakdown Structure
Hierarchical breakdown of project tasks.
(WBS)
📊 Summary Tables
🔸 SMART Objectives
S M A R T
Specific Measurable Achievable Relevant Time-bound
🔸 Triple Constraint Priority Matrix Example
Constraint Status Manager Focus
Time Constrain Must meet deadline
Cost Accept May increase slightly
Scope Enhance Add features if possible
🔸 Project Definition Documents
Document Purpose
Project Charter Authorizes project and defines high-level info.
Scope Statement Clarifies project boundaries.
SOW Detailed work description (often contractual).
WBS Breaks down work for planning and control.
✅ Chapter Summary
Defining the project is the foundation for success — it sets objectives, scope, and
stakeholder expectations.
The Project Charter and Scope Statement formalize the project start.
Using tools like SMART goals, WBS, and Priority Matrix ensures focus and
control.
A well-defined project avoids scope creep, builds alignment, and increases success
rates.