CAVENDISH UNIVERSITY ZAMBIA | DEPARTMENT OF BUSINESS INFORMATION TECHNOLOGY
PROJECT MANAGEMENT
Comprehensive Study Guide
Initiation Stage | Project Charter | Scope | Estimation | Team & Leadership
Chimwemwe Bilima
Cavendish University Zambia
Business Administration Programme | 2025/2026
TABLE OF CONTENTS Project Management Study Guide
Table of Contents
1. The Project Business Case
2. Project Management Process at the Initiation Stage
3. The Project Initiation Phase
4. The Project Management Cycle
5. The Project Charter
6. The Project Scope Statement
7. Estimation: Bottom-Up and Top-Down
8. Project Management Design and Strategy
9. The Project Manager
10. Project Team Members
11. Desired Attitudes of a Project Manager
Page 2
TABLE OF CONTENTS Project Management Study Guide
1. The Project Business Case
Definition
A project business case is a formal document that justifies the initiation of a project. It provides decision-makers with
the rationale, expected benefits, costs, risks, and alternatives needed to authorise or reject a project. It is the
foundation of the initiation phase - without a sound business case, no project should proceed.
Why the Business Case Matters
Links project to strategy Demonstrates that the project aligns with organisational goals, not just
departmental interests.
Secures funding and Sponsors and executives use it to decide whether to invest time, money, and
resources people.
Sets accountability Defines who is responsible for delivering the stated benefits.
Provides a baseline Serves as a benchmark throughout the project lifecycle against which success is
measured.
Key Components of a Business Case
• Executive Summary: Brief overview of the project purpose, cost, and recommendation.
• Problem / Opportunity Statement: Clear articulation of the problem being solved or opportunity being captured.
• Strategic Alignment: How the project supports organisational strategy, mission, or objectives.
• Options Analysis: At least three options: do nothing, minimum viable solution, full solution. Includes cost-benefit
for each.
• Recommended Option: Preferred solution with justification.
• Financial Appraisal: NPV, IRR, Payback Period, ARR - key tools for financial viability. See note below.
• Risk Assessment: High-level identification of major risks and mitigation strategies.
• Assumptions and Constraints: Key assumptions on which the case is built and constraints (budget, time,
technology).
• Stakeholder Impact: Who is affected, and how.
• Conclusion and Recommendation: Clear decision request from the sponsor.
Key Financial Metrics Recap: NPV (net present value) discounts future cash flows - positive NPV = value-adding.
IRR is the discount rate at which NPV = 0; higher than cost of capital means accept. Payback period = time to
recover initial investment. ARR = average annual profit / average investment.
Common Pitfalls
• Overly optimistic benefit projections (optimism bias)
• Underestimating costs or complexity
• Ignoring the 'do nothing' option
• Failing to re-evaluate the business case when project scope changes significantly
• Writing the business case to justify a pre-decided outcome rather than to evaluate options honestly
Page 3
SECTION 1: THE PROJECT BUSINESS CASE Project Management Study Guide
2. Project Management Process at the Initiation Stage
Overview
The initiation stage is the formal starting point of a project. It is where an idea or need is transformed into an
authorised, defined project. Without proper initiation, projects risk misalignment, scope creep, and failure before they
begin. The primary outputs are the Business Case, Project Charter, and initial Stakeholder Register.
Key Processes at Initiation (PMI/PMBOK Framework)
Develop Project Charter
Formally authorises the project. Documents high-level objectives, budget, schedule, and designates the project
manager.
Identify Stakeholders
Identifies all individuals or groups affected by the project. Captured in a Stakeholder Register.
Conduct Feasibility Study
Evaluates technical, financial, operational, and legal feasibility.
Appoint Project Manager
Ensures a named, accountable leader is in place before planning begins.
Establish Project Governance
Defines reporting lines, decision-making authority, and escalation procedures.
Initiation Stage: Inputs and Outputs
INPUTS OUTPUTS
Strategic plan / organisational objectives Project Charter
Business case / feasibility study Stakeholder Register
Expert judgement High-level scope statement
Organisational process assets (templates, past projects) Identified risks (high-level)
Environmental enterprise factors (market, regulation) Project Manager assigned
Page 4
SECTION 2: PM PROCESS AT INITIATION Project Management Study Guide
3. The Project Initiation Phase
The Project Initiation Phase is the first phase of the project lifecycle. It encompasses all activities needed to define
the project, secure authorisation, and prepare for planning. Think of it as the 'entry gate' - a project that passes through
it has a documented rationale, a sponsor, and a project manager.
Steps Within the Initiation Phase
Step 1: Identify the Need or Opportunity
Recognise a problem, gap, or strategic opportunity that justifies a project response.
Step 2: Develop the Business Case
Document the justification (see Section 1). This may require a preliminary feasibility study.
Step 3: Feasibility Analysis
Technical feasibility (can we build it?), financial feasibility (is it worth it?), operational feasibility (can we run it?),
legal/regulatory feasibility.
Step 4: Appoint the Project Manager
The sponsor selects a PM who will lead the project through its lifecycle.
Step 5: Develop the Project Charter
The PM drafts the charter (see Section 5). Once signed by the sponsor, the project is officially authorised.
Step 6: Identify Stakeholders
The PM and sponsor identify all individuals and groups with an interest in the project outcome.
Step 7: Conduct Kick-off Meeting
Brings the initial team, sponsor, and key stakeholders together. Aligns understanding and builds momentum.
Exam Tip: The initiation phase ends with an approved Project Charter. Before the charter is signed, the project
does not officially exist. The charter gives the PM authority to use organisational resources.
Page 5
SECTION 3: THE PROJECT INITIATION PHASE Project Management Study Guide
4. The Project Management Cycle
The Project Management Cycle (also called the project lifecycle) describes the phases a project moves through from
conception to closure. Most frameworks identify five phases, though some combine or rename them.
Define the project, build the business case, obtain authorisation (Project Charter). Key
1. Initiation question: Should we do this project?
Develop the project management plan: scope, schedule (Gantt, network diagram),
2. Planning budget (WBS, cost baseline), risk register, communication plan, procurement plan. Key
question: How will we do this project?
Carry out the work defined in the project plan. Direct and manage the project team.
3. Execution Manage stakeholder engagement. Procure resources. Key question: Are we doing the
work as planned?
Run concurrently with execution. Track, review, and regulate progress. Manage
4. Monitoring changes (change control). Earned Value Management (EVM). Key question: Are we on
and track, and how do we correct deviations?
Controlling
Formal acceptance of deliverables, lessons learned documentation, release resources,
5. Closure archive project records, celebrate success. Key question: Did we deliver what was
promised, and what did we learn?
Key distinction: Monitoring and Controlling is not a sequential phase - it runs in parallel with execution. Some
frameworks collapse it into execution, but PMBOK treats it as a distinct process group.
Iterative vs. Sequential Lifecycle
Traditional (Waterfall) projects move sequentially: each phase is completed before the next begins. Agile projects
iterate - short sprints cycle through planning, execution, and review repeatedly. Hybrid approaches combine both.
Exam answers should acknowledge this distinction when discussing lifecycle.
Page 6
SECTION 4: THE PROJECT MANAGEMENT CYCLE Project Management Study Guide
5. The Project Charter
Definition and Purpose
The Project Charter is the document that formally authorises the existence of a project and grants the Project
Manager the authority to apply organisational resources. It is issued by the project sponsor and is the single most
important output of the initiation phase. Without a signed charter, the project manager has no formal power.
Contents of a Project Charter
• Project Title and Description: Clear name and brief summary of the project.
• Project Purpose / Justification: Why the project is being undertaken - links to the business case.
• Measurable Objectives: SMART objectives: Specific, Measurable, Achievable, Relevant, Time-bound.
• High-Level Requirements: What the project must deliver at a high level.
• High-Level Scope: What is inside and outside the project boundary.
• High-Level Risks: Major risks identified at initiation.
• Summary Milestone Schedule: Key dates and phases at a high level.
• Pre-approved Budget: Initial financial envelope approved by the sponsor.
• Project Sponsor: Name and authority of the person commissioning the project.
• Project Manager: Name and level of authority granted to the PM.
• Key Stakeholders: High-level stakeholder identification.
• Approval Requirements: What constitutes success and who approves deliverables.
• Sponsor Signature: Formal sign-off that authorises the project.
Charter vs. Business Case: The business case justifies the project (is it worth doing?). The charter authorises it
(we are doing it - here is the PM and the budget). They are complementary, not interchangeable.
Who Creates and Signs the Charter?
Typically the Project Manager drafts the charter (often working with the sponsor and key stakeholders), and the
Project Sponsor signs it. In large organisations, a Project Management Office (PMO) may provide the template. The
signed charter is then communicated to all relevant stakeholders.
Page 7
SECTION 5: THE PROJECT CHARTER Project Management Study Guide
6. The Project Scope Statement
Definition
The Project Scope Statement is developed during the planning phase (following the charter) and defines in detail
what is included in and excluded from the project. It is the authoritative reference for managing scope change - if it
is not in the scope statement, it is not in the project.
Key Elements
Product Scope Detailed description of the product, service, or result the project will produce.
Description
Project Deliverables Specific, tangible outputs - both final and intermediate (sub-deliverables).
Acceptance Criteria Conditions that must be met for deliverables to be accepted by the sponsor/client.
Project Exclusions Explicitly states what is not part of the project to prevent scope creep.
Constraints Internal or external factors that limit the project team's options (budget, time,
technology, law).
Assumptions Factors believed to be true for planning purposes. If they prove false, they become
risks.
Scope Creep
Scope creep is the uncontrolled expansion of project scope without corresponding adjustments to time, cost, or
resources. It is one of the leading causes of project failure. Prevention requires a clear scope statement, a formal
change control process, and disciplined stakeholder management. Every change request must be evaluated,
approved, and documented.
Scope Statement vs. Work Breakdown Structure (WBS)
The scope statement describes what will be delivered. The WBS (Work Breakdown Structure) decomposes the scope
into manageable work packages - the smallest units of work that can be assigned, scheduled, and costed. Together
they form the scope baseline.
Page 8
SECTION 6: PROJECT SCOPE STATEMENT Project Management Study Guide
7. Bottom-Up and Top-Down Estimation
Estimation is the process of predicting the cost, time, and resources required to complete a project. Accurate
estimates are critical for realistic planning, budgeting, and stakeholder expectations. Two fundamental approaches are
Top-Down and Bottom-Up estimation.
Approach Comparison
Dimension Top-Down Estimation Bottom-Up Estimation
Definition Estimate the whole project first, then Estimate each individual work package,
allocate to sub-components. then aggregate to project total.
Basis Expert judgement, historical analogies, Detailed task analysis, often using the
parametric models. WBS.
Accuracy Lower - broad assumptions. Typically -25% Higher - based on detailed task data.
to +75% range. Typically -5% to +10%.
Speed Fast - suitable for early-stage feasibility. Slow - requires detailed scope definition.
Best used when Early feasibility, business case, high-level Detailed planning phase, when scope is
budget approval. fully defined.
Risk of error High - may miss specific cost drivers. Low - but depends on quality of task
breakdown.
Top-Down Estimation Techniques
• Analogous Estimating: Uses cost/duration from a similar past project as a basis. Fast but relies on the similarity of
the analogy.
• Parametric Estimating: Uses a statistical relationship between variables (e.g., cost per square metre, cost per line
of code). More accurate than analogous when good data exists.
• Expert Judgement: Relies on the experience of subject matter experts. Often used alongside other techniques.
• Three-Point Estimating: Uses Optimistic (O), Most Likely (M), and Pessimistic (P) estimates. PERT formula: E =
(O + 4M + P) / 6. Accounts for uncertainty.
Bottom-Up Estimation Process
1. Decompose the project into a full WBS with identifiable work packages.
2. Estimate cost and duration for each work package individually.
3. Identify dependencies and sequence work packages.
4. Sum all estimates upward through the WBS to arrive at total project cost/duration.
5. Add contingency reserves for identified risks and management reserves for unknown risks.
Exam Tip: In practice, projects often use top-down estimates for the business case and bottom-up estimates for
the project plan. The difference in figures between the two can reveal scope gaps or planning errors.
Page 9
SECTION 7: ESTIMATION METHODS Project Management Study Guide
8. Project Management Design and Strategy
Project Management Design refers to the deliberate selection of a project approach, methodology, governance
structure, and tools that best fit the nature and context of the project. There is no single right approach - the design
must match the project type, complexity, organisational culture, and stakeholder needs.
Choosing a Project Management Methodology
Waterfall (Traditional)
Sequential phases. Suitable for projects with well-defined, stable scope - construction, manufacturing, infrastructure.
Strong documentation, clear milestones, formal change control.
Agile (Scrum, Kanban)
Iterative, flexible. Suitable for uncertain or evolving scope - software, product development. Short sprints, continuous
feedback, customer collaboration over contract negotiation.
PRINCE2
Process-based framework common in UK/Commonwealth organisations. Seven themes: Business Case, Organisation,
Quality, Plans, Risk, Change, Progress. Strong emphasis on governance and defined roles.
Hybrid
Combines waterfall and agile elements. Common in large organisations transitioning to agile or managing mixed
portfolios.
Project Strategy Elements
Governance Who makes decisions, who has veto power, how escalations are handled.
Includes a Steering Committee, Project Board, or Project Sponsor.
Stakeholder Engagement How and when different stakeholders will be engaged, informed, or consulted.
Strategy
Risk Strategy Risk appetite, risk tolerance, and whether to avoid, mitigate, transfer, or accept
risks.
Communication Strategy What information is shared, with whom, how often, and through what channel.
Procurement Strategy Make-or-buy decisions, contractor selection, contract types.
Change Management How changes to scope, schedule, and budget are requested, evaluated, and
approved.
Page 10
SECTION 8: DESIGN AND STRATEGY Project Management Study Guide
9. The Project Manager
Role Definition
The Project Manager (PM) is the individual assigned by the performing organisation to lead the project team and is
responsible for achieving the project objectives. The PM is not merely an administrator - they are the integrator,
leader, communicator, and problem-solver who holds the project together from charter to closure.
Core Responsibilities
• Define and manage project scope, schedule, and budget (the triple constraint).
• Build, lead, and motivate the project team.
• Identify, assess, and manage risks and issues.
• Manage stakeholder relationships and communications.
• Monitor and control project performance (scope, time, cost, quality).
• Manage change through the formal change control process.
• Report progress to the sponsor and steering committee.
• Ensure deliverables meet quality standards and acceptance criteria.
• Facilitate lessons learned and formal project closure.
The PM's Triple Constraint (Iron Triangle)
Every project is constrained by Scope, Time, and Cost. Quality sits at the centre. Changing one constraint affects the
others: increasing scope requires more time or cost; cutting cost may reduce scope or extend time. The PM's role is to
optimise these trade-offs with the sponsor's input.
Constraint Question It Answers Tool/Technique
Scope What will we deliver? WBS, Scope Statement
Time By when? Gantt Chart, Network Diagram, CPM
Cost For how much? Cost baseline, Earned Value
Quality To what standard? QA plan, Acceptance criteria
PM Competency Framework (PMI Talent Triangle)
• Technical PM Skills: Planning, scheduling, risk management, budgeting, change control - the hard skills of project
management.
• Leadership: Motivating teams, resolving conflict, building trust, decision-making under uncertainty.
• Strategic and Business Management: Understanding the organisational context, aligning project outcomes to
strategy, financial literacy.
Page 11
SECTION 9: THE PROJECT MANAGER Project Management Study Guide
10. Project Team Members
Team Composition
The project team consists of individuals who collectively carry out the work of the project. Teams may be functional
(from one department), cross-functional (from multiple departments), virtual (geographically dispersed), or contracted
(third parties). Effective teams combine the right skills, roles, and personalities.
Key Roles Within a Project Team
Project Sponsor
Senior executive who champions the project, provides funding, and makes key decisions. Not part of the day-to-day
team but holds ultimate accountability for project success.
Project Manager
Leads and coordinates the team, manages all constraints, communicates with stakeholders.
Subject Matter Experts (SMEs)
Provide specialist technical or domain knowledge essential for specific deliverables.
Team Leaders / Work Package Owners
Accountable for specific sections of the WBS. Bridge between PM and technical team members.
Project Administrator / Coordinator
Handles documentation, scheduling, meeting coordination, and reporting support.
Quality Assurance Officer
Ensures project processes and outputs meet quality standards.
Risk Manager
In larger projects, a dedicated role for identifying, monitoring, and responding to risks.
Stakeholder / Change Manager
Manages relationships with affected parties and internal change communication.
Team Development: Tuckman's Model
Teams rarely perform optimally from day one. Bruce Tuckman's model describes five stages:
• Forming: Team members meet; polite, uncertain, dependent on the PM for direction.
• Storming: Conflict emerges as roles, workstyles, and power dynamics are negotiated.
• Norming: Norms develop; team cohesion grows; communication improves.
• Performing: High productivity; team is self-directing and focused on goals.
• Adjourning: Project ends; team disbands. Emotional for close-knit teams. Lessons learned captured.
Page 12
SECTION 10: PROJECT TEAM MEMBERS Project Management Study Guide
RACI Matrix: A useful tool for clarifying team roles. For each task, assign: Responsible (does the work),
Accountable (owns the outcome), Consulted (provides input), Informed (kept in the loop). Only one A per task.
Page 13
SECTION 10: PROJECT TEAM MEMBERS Project Management Study Guide
11. Desired Attitudes of a Project Manager
Technical skills get a project manager hired. Attitudes determine how far they go. The right mindset shapes how a
PM responds to ambiguity, conflict, failure, and people - which are the real substance of project work. The following
attitudes are widely recognised in project management literature as essential.
1. Proactivity A proactive PM anticipates problems before they become crises. Rather than waiting
for risks to materialise, they scan the environment, ask 'what could go wrong?', and
put contingencies in place. Reactive PMs manage crises. Proactive PMs prevent
them.
2. Accountability The PM owns the project outcome - not just the parts they personally control, but the
whole. This means not blaming the team or circumstances when things go wrong, but
asking: 'What could I have done differently?'
3. Integrity Honest reporting - even bad news - is a mark of a trustworthy PM. Stakeholders who
receive consistent, accurate information can make better decisions. PMs who hide
problems destroy trust and make crises worse.
4. Adaptability / Projects are dynamic. Scope changes, stakeholders shift, resources disappear. An
Flexibility adaptable PM holds the objective constant while remaining flexible about the path.
Rigidity in an uncertain environment is a liability.
5. Collaborative No PM delivers a project alone. The best PMs invest in team relationships, facilitate
Mindset rather than dictate, share credit, and build an environment where people feel safe to
raise concerns.
6. Emotional EQ - the ability to recognise, understand, and manage emotions (one's own and
Intelligence (EQ) others') - is arguably more important than IQ in project leadership. It underpins
conflict resolution, motivation, negotiation, and stakeholder management.
7. Decisiveness Projects demand decisions - often under uncertainty and time pressure. A PM who
cannot decide creates bottlenecks and loses team confidence. Good decisions made
promptly outperform perfect decisions made too late.
8. Resilience Projects face setbacks. A resilient PM processes failure without being paralysed by it,
learns from it, and keeps the team motivated forward. Resilience is not the absence
of stress - it is the capacity to recover from it.
9. Stakeholder Empathy Understanding stakeholder perspectives - including those who resist the project -
allows the PM to communicate more effectively, anticipate opposition, and build
genuine buy-in rather than forced compliance.
10. Commitment to Great PMs treat every project as a learning opportunity. They conduct honest
Continuous lessons-learned reviews, apply insights to future projects, and encourage a team
Improvement culture of reflection and growth.
Page 14
SECTION 11: DESIRED ATTITUDES OF A PM Project Management Study Guide
Attitudes vs. Skills: Skills can be trained. Attitudes are cultivated through character and self-awareness. The PMI
Code of Ethics and Professional Conduct codifies four core values for practitioners: Responsibility, Respect,
Fairness, and Honesty. These align directly with the attitudes above.
Page 15
SECTION 11: DESIRED ATTITUDES OF A PM Project Management Study Guide
Quick Reference Summary
Topic One-line Essence
Business Case Justifies why the project should exist.
Initiation Process Transforms idea into authorised project; ends with signed charter.
Initiation Phase Steps: identify need, business case, feasibility, appoint PM, charter, stakeholders,
kick-off.
PM Lifecycle Initiation > Planning > Execution > Monitor/Control > Closure.
Project Charter Authorises project + grants PM authority. Must be signed by sponsor.
Scope Statement Defines what is in/out. Prevents scope creep. Basis for change control.
Top-Down Estimation Fast, early-stage; uses analogies/parametric models. Less accurate.
Bottom-Up Estimation Detailed, accurate; sums work packages from WBS upward.
PM Design/Strategy Choose methodology (Waterfall/Agile/Hybrid) + governance + risk/comm strategy.
Project Manager Integrator and leader: owns scope/time/cost/quality and team performance.
Project Team Sponsor, PM, SMEs, TLs, admin - clarify roles with RACI matrix.
PM Attitudes Proactivity, accountability, integrity, EQ, adaptability, decisiveness, resilience.
Good luck, Chichi. You know this material - trust the preparation.
Page 16