Week 2 Notes
Slide 1: Title
Week 2 – Project Definition, Initiation, and Planning Processes
Slide 2: Learning Outcomes & Objectives
MLO1 Develop a critical awareness of all phases of a project.
MLO2 Evaluate the relationship between project management processes and methodologies.
Slide 3: Table of Contents
Slide 1: Title
Slide 2: Learning Outcomes & Objectives
Slide 3: Table of Contents
Slide 4: The Pre-Project Frontier: Strategic Alignment and the Business Case
Slide 5: Economic Feasibility and Project Justification: Selection Models
Slide 6: Formalising Initiation: The Project Charter and Managerial Authority
Slide 7: Transitioning to Planning: The Integrated Management Plan Paradigm
Slide 8: Requirements Elicitation and Analysis: Capturing Stakeholder Needs
Slide 9: Scope Definition and the Project Scope Statement: Defining the In-Scope
Slide 10: Decomposing Work: The Work Breakdown Structure (WBS)
Slide 11: Project Time Management: Scheduling and Activity Sequencing
Slide 12: Project Cost Management: Estimating and Budget Build-Up
Slide 13: Project Resource Management: Allocation and Optimization
Slide 14: Project Risk Management: Identifying and Mitigating Uncertainty
Slide 15: Quality Management and Performance Metrics: Ensuring Excellence
Slide 16: Deliverables, Milestones, and the Phase-Gate Approval Process
References
Slide 4: The Pre-Project Frontier: Strategic Alignment and the Business Case
Projects do not emerge in isolation; they are born from a specific organisational need or market
opportunity (Abdullah, 2025). The pre-project stage is a vital analytical phase where the
strategic intent of the organisation is translated into a potential project initiative (Project
Management Institute, 2021; Butler, 2022). At the heart of this stage is the needs assessment, a
process that involves evaluating the current state of the organisation, identifying gaps or
problems, and defining the desired future state (Williams, 2023). Scholarly perspectives suggest
that the way a problem is defined fundamentally determines the path to its solution; therefore,
project practitioners must avoid defining problems in terms of preconceived solutions (Heagney,
2022). This initial problem statement serves as the anchor for the entire project life cycle,
LJMU - 7501 - BEGP - Project Management Fundamentals
​
1/12
Week 2 Notes
ensuring that the team addresses a genuine organisational requirement rather than a superficial
symptom (Heagney, 2022; Williams, 2023).
Once the need is validated, the organisation develops a business case, which serves as the
primary document for project justification (Abdullah, 2025; Williams, 2023). The business case
is not merely a financial forecast; it is an economic feasibility study that outlines the tangible
and intangible benefits expected from the project (Abdullah, 2025; Project Management
Institute, 2021). It must be thorough, addressing the commercial problems of the project rather
than just technical complexities (Williams, 2023). Within the business case, practitioners should
include a needs analysis, a cost-benefit analysis, and a benefits realisation management
plan (Abdullah, 2025). This ensures that the required investment is justified from a business
standpoint and that there is a clear mechanism for tracking value delivery post-completion
(Abdullah, 2025; Zaman et al., 2022).
Strategic alignment is the "golden thread" that must run through the business case (Butler,
2022; Abdullah, 2025). Projects must advance the organisation's mission and vision, helping it
gain a competitive advantage or achieve long-term objectives (Zaman et al., 2022; Abdullah,
2025). In high-maturity organisations, the Enterprise Project Management Office (EPMO) plays
a critical role in ensuring that project proposals are evaluated against a set of prioritised criteria,
such as market potential, strategic fit, and risk level (Richardson and Jackson, 2024; Butler,
2022). Failing to establish this alignment leads to the "success trap," where organisations
complete the "wrong projects right," wasting limited resources on initiatives that do not
contribute to organisational well-being (Richardson and Jackson, 2024; Butler, 2022; Abdullah,
2025). Master-level students must recognize that a robust business case is a living document
that may be revisited during phase-gate approvals to ensure the project remains viable in a
changing external environment (Butler, 2022; Project Management Institute, 2021).
Slide 5: Economic Feasibility and Project Justification: Selection Models
The process of project selection is a critical governance function, as organisations often have
more ideas than they have budget or resource capacity to execute (Abdullah, 2025; Butler,
2022). Decisions at this stage rely on a combination of quantitative and qualitative analysis to
identify projects with the highest potential impact (Butler, 2022; Abdullah, 2025). Financial
models are frequently utilised to determine the economic feasibility of a proposal. One common
metric is the payback period, which measures the amount of time required to recover the initial
project investment (Abdullah, 2025). While easy to calculate, the payback period is often
criticised for ignoring the time value of money and cash flows beyond the recovery date
(Abdullah, 2025). Consequently, practitioners often prefer Net Present Value (NPV), which
calculates the long-term profitability of a project by discounting future cash inflows to their
today's value (Abdullah, 2025).
However, relying solely on financial indicators can be dangerous, especially in contemporary
project environments where factors like sustainability, safety, and regulatory compliance are
paramount (Abdullah, 2025; Richardson and Jackson, 2024). To introduce objectivity into what
could be a subjective process, organisations often employ weighted scoring models (Abdullah,
2025). These models allow decision-makers to structure the project selection process by
specifying and prioritising needs through decision-making criteria (Abdullah, 2025). For
example, a technology firm might weight strategic opportunity at 25%, competitive advantage
LJMU - 7501 - BEGP - Project Management Fundamentals
​
2/12
Week 2 Notes
at 15%, and risk aversion at 20% (Abdullah, 2025). This holistic approach ensures that the
organisation doesn't just chase ROI, but also builds its future preparedness and technological
infrastructure (Butler, 2022; Abdullah, 2025).
In the public sector, project justification takes on an even broader dimension, focusing on
public benefits, GDP growth, and the quality of life for citizens (Irfan et al., 2021). Public sector
projects are often subject to government mandates or social needs, such as installing clean
energy solutions or building bridges (Williams, 2023; Abdullah, 2025; Irfan et al., 2021). In these
contexts, the business case must demonstrate social feasibility and establish clear success
metrics that go beyond the "iron triangle" (Irfan et al., 2021; Abdullah, 2025). Regardless of the
sector, project selection committees must be wary of the "escalation of commitment," where
leaders continue to fund failing projects due to emotional attachment or sunk costs (Butler, 2022;
Richardson and Jackson, 2024). A disciplined selection process grounded in a robust business
case is the first line of defence against project failure and ensuring value creation (Butler, 2022;
Abdullah, 2025).
Slide 6: Formalising Initiation: The Project Charter and Managerial Authority
The initiating process group marks the formal birth of a project within the organisation (Project
Management Institute, 2021; Abdullah, 2025). The primary output of this stage is the project
charter, a formal document that authorises the project's existence and provides the project
manager with the formal authority to apply organisational resources to project activities
(Abdullah, 2025; Williams, 2023). Without a charter, a project is merely an idea without the
governance structure required for execution (Williams, 2023; Abdullah, 2025). The charter is
typically a brief but comprehensive document that outlines the project's purpose, measurable
objectives, and high-level requirements (Williams, 2023; Abdullah, 2025). It serves as the
"contract" between the project team and the project sponsor, ensuring that all parties share a
consistent vision and mission (Heagney, 2022; Williams, 2023).
A critical element of the project charter is the identification of the project sponsor, who is
usually an executive with the authority to assign resources and remove barriers to success
(Abdullah, 2025; Williams, 2023). The sponsor acts as the project's "external champion," serving
as the final escalation point for issues the team cannot resolve independently (Williams, 2023).
The charter also defines the project manager's role, clarifying their level of accountability and
power (Abdullah, 2025; Heagney, 2022). In many organisations, the project manager is assigned
during the initiation phase to ensure they are involved in defining the project's foundations,
which significantly increases the likelihood of success (Abdullah, 2025; Irfan et al., 2021). Effective
leadership begins here, as the project manager must start team building and aligning
stakeholder expectations from the very first kickoff meeting (Williams, 2023; Abdullah, 2025).
The content of a project charter should be specific enough to provide direction but flexible
enough to allow for progressive elaboration during the planning phase (Abdullah, 2025; Project
Management Institute, 2021). Key components include the summary milestone schedule,
preapproved financial resources, and an initial list of overall project risks (Abdullah, 2025;
Williams, 2023). Furthermore, the charter must specify project exit criteria—the conditions
under which the project will be terminated, whether successfully or prematurely (Abdullah, 2025).
This formal authorization is necessary for both internal projects and external projects where a
legally binding contract may also be required (Abdullah, 2025; Pheng, 2022). By establishing
LJMU - 7501 - BEGP - Project Management Fundamentals
​
3/12
Week 2 Notes
clear governance and decision-making mechanisms at the outset, the initiation process sets
the stage for the rigorous integrated planning required to navigate the complexities of the
project life cycle (Abdullah, 2025; Zaman et al., 2022).
Slide 7: Transitioning to Planning: The Integrated Management Plan Paradigm
Once the project charter is approved, the project transitions into the planning process group,
which is widely considered the most intense and challenging phase of the project management
life cycle (Abdullah, 2025; Pheng, 2022). The purpose of this stage is to establish the project's
scope, refine objectives, and define the course of action required to attain them (Abdullah,
2025; Pheng, 2022). Planning is not a one-time event but an iterative process of progressive
elaboration, where the team continuously refines initial "ballpark" estimates into a detailed
project management plan as more information becomes available (Richardson and Jackson,
2024; Abdullah, 2025). This integrated planning approach ensures that all knowledge
areas—including scope, schedule, cost, quality, resource, communication, risk, and
procurement—are synchronized and aligned with the organisational strategy (Pheng, 2022;
Abdullah, 2025).
The project management plan serves as the primary roadmap for the team, providing direction
through execution, monitoring and control, and closure (Abdullah, 2025; Williams, 2023). It
includes baselines for the triple constraint of scope, schedule, and cost, which act as the
metrics against which project performance will be measured (Abdullah, 2025; Heagney, 2022).
Scholarly evidence suggests that a well-developed plan significantly reduces the likelihood of
project failure by mitigating uncertainty and preventing scope creep (Irfan et al., 2021;
Abdullah, 2025). However, practitioners must avoid "analysis paralysis," recognizing that no plan
is perfect and that it must be susceptible to change through a formal change control process
(Heagney, 2022; Richardson and Jackson, 2024). The effort spent in upfront planning is an
investment that results in smoother implementation and fewer "surprises" during the later stages
of the life cycle (Richardson and Jackson, 2024; Abdullah, 2025).
In adaptive (agile) environments, the approach to planning is more fluid, with comprehensive
upfront planning replaced by iteration or cycle planning (Mohammadreza Samadzadeh et al.,
2025; Abdullah, 2025). In these contexts, the plan evolves through sprints or timeboxes,
allowing the team to pivot based on stakeholder feedback and changing market conditions
(Mohammadreza Samadzadeh et al., 2025; Abdullah, 2025). Regardless of the
methodology—predictive, iterative, or hybrid—the project manager must ensure that the plan
is realistic and that all stakeholders have signed off on it (Richardson and Jackson, 2024;
Abdullah, 2025; Heagney, 2022). Master-level students must appreciate that "failing to plan is
planning to fail," but a plan is only valuable if it is actually followed and updated to reflect the
project's current reality (Heagney, 2022; Abdullah, 2025).
Slide 8: Requirements Elicitation and Analysis: Capturing Stakeholder Needs
Before a project team can define the work to be done, they must first understand what the
product or service needs to accomplish, a process known as eliciting requirements (Abdullah,
2025; Williams, 2023). While some frameworks use the term "collecting," the BABOK Guide
emphasises elicitation, which involves "drawing forth" information through interviews, surveys,
LJMU - 7501 - BEGP - Project Management Fundamentals
​
4/12
Week 2 Notes
workshops, observations, and document analysis (Abdullah, 2025; Project Management
Institute, 2021). A requirement is defined as a usable representation of a need, and it must be
measurable, testable, and related to identified business opportunities (Abdullah, 2025).
Inaccurate requirements gathering is cited as a primary cause of project failure in 37% of
organisations, making this process critical for delivering strategic value (Abdullah, 2025; Project
Management Institute, 2021).
Requirements are typically structured in a hierarchy to ensure traceability from high-level
organisational goals to technical specifications (Abdullah, 2025). At the top are business
requirements, which describe the high-level needs of the organisation (Abdullah, 2025). These
lead to stakeholder requirements, which capture the needs of specific groups affected by the
project, and then to solution requirements, which define the capabilities the product must have
(Abdullah, 2025). Solution requirements are further divided into functional requirements (what
the system does) and non-functional requirements (how the system behaves, such as its
reliability, security, and usability) (Abdullah, 2025). Finally, transition requirements describe
the temporary capabilities needed to move from the current state to the desired future state,
such as staff training or data conversion (Abdullah, 2025).
To manage this complexity, project managers utilise a Requirements Traceability Matrix (RTM),
which links requirements to their corresponding WBS activities, design elements, and test
cases (Abdullah, 2025). This ensures that every requirement is accounted for and that no "gold
plating"—the addition of unauthorised features—takes place (Abdullah, 2025; Pheng, 2022).
Furthermore, the use of the SMART protocol (Specific, Measurable, Achievable, Relevant,
Time-based) ensures that requirements are clear and unambiguous (Abdullah, 2025; Heagney,
2022). In agile projects, requirements are often captured as user stories, which describe
functionality from the perspective of the end-user (e.g., "As a [user], I want [feature] so that
[benefit]") (Mohammadreza Samadzadeh et al., 2025; Abdullah, 2025; Williams, 2023). Successful
requirements management requires continuous engagement with stakeholders to ensure that
the solution matures in concert with their aspirations and the shifting external environment
(Mohammadreza Samadzadeh et al., 2025; Abdullah, 2025; Zaman et al., 2022).
Slide 9: Scope Definition and the Project Scope Statement: Defining the
In-Scope
Project scope management is the process that ensures the project includes only the work
necessary for its successful completion—"no more and no less" (Pheng, 2022; Abdullah, 2025).
Defining the scope is the critical step that prevents scope creep, the uncontrolled expansion of
project requirements that can lead to budget overruns and schedule delays (Abdullah, 2025;
Richardson and Jackson, 2024; Heagney, 2022). This process builds upon the high-level
information in the project charter to generate a detailed project scope statement (Abdullah,
2025; Williams, 2023). The scope statement is the "compass" for the project team, describing
the deliverables, assumptions, and constraints in quantifiable terms to assure measurability
and stakeholder alignment (Abdullah, 2025; Pheng, 2022).
A robust scope statement must explicitly define what is in scope and, just as importantly, what
is out of scope or project exclusions (Abdullah, 2025; Williams, 2023). For example, a project to
develop a mobile app might exclude tablet optimization or operating systems other than Android
and iOS (Abdullah, 2025). By clearly defining these boundaries, the project manager can better
LJMU - 7501 - BEGP - Project Management Fundamentals
​
5/12
Week 2 Notes
manage stakeholder expectations and defend the project against unauthorised change requests
(Abdullah, 2025; Richardson and Jackson, 2024). The scope statement also includes product
acceptance criteria, the specific conditions that must be met for the client to sign off on the
final deliverables (Abdullah, 2025; Williams, 2023). This provides the project team with a
definitive "finish line" and ensures that quality standards are complied with throughout the
execution phase (Abdullah, 2025; Pheng, 2022).
Managing the scope requires an integrated approach to change management, where every
proposed modification is evaluated for its impact on the triple constraint (Richardson and
Jackson, 2024; Abdullah, 2025). If a stakeholder requests a new feature, the project team must
assess whether the current budget, schedule, and resources are sufficient to absorb the change
(Richardson and Jackson, 2024; Abdullah, 2025). Scope changes are inevitable, but they must
be formally approved through a change control board and funded via a scope management
reserve to maintain the integrity of the baseline plan (Richardson and Jackson, 2024; Abdullah,
2025). At the master's level, we recognize that scope is not a static target but a "rubber box" that
can be adjusted through difficult trade-offs to maximise value delivery (Richardson and
Jackson, 2024). Ultimately, successful scope management ensures that the project team
remains focused on achieving the business objectives outlined in the business case (Project
Management Institute, 2021; Abdullah, 2025).
Slide 10: Decomposing Work: The Work Breakdown Structure (WBS)
The Work Breakdown Structure (WBS) is a hierarchical decomposition of the project's total
scope into manageable and logical work packages (Williams, 2023; Abdullah, 2025). It is
considered the "foundation" of project planning, as it subdivides the complex project into smaller
components that can be scheduled, estimated, and easily monitored and controlled (Abdullah,
2025; Heagney, 2022). In a predictive methodology, each descending level of the WBS
represents an increasingly detailed definition of the project work (Abdullah, 2025). The lowest
level manageable activities are called work packages, which provide the necessary detail for
assigning resources and establishing cost estimates (Abdullah, 2025; Williams, 2023). The WBS
is essentially the "mailbox" for the project work, where every task has a unique WBS code for
identification and traceability (Richardson and Jackson, 2024; Abdullah, 2025).
Constructing a WBS follows a top-down approach, starting with the project summary and
moving through phases or major deliverables (Abdullah, 2025; Pheng, 2022). For example, a
building project might be subdivided into substructure, superstructure, and architectural
works (Pheng, 2022). The "100% rule" is a fundamental principle of the WBS, stating that it must
include all work defined by the project scope and capture all deliverables to be created
(Abdullah, 2025). If a task is not in the WBS, it is not in the project (Abdullah, 2025). This
systematic organisation helps project managers identify missing tasks and avoid scope creep
(Abdullah, 2025). Furthermore, a WBS dictionary should accompany the structure, providing
detailed descriptions of the work for each box to ensure that project team members understand
their specific responsibilities (Richardson and Jackson, 2024; Abdullah, 2025).
The WBS also facilitates delegation and buy-in within the project team (Heagney, 2022;
Richardson and Jackson, 2024). By involving the people who will actually perform the work in the
decomposition process, the project manager ensures that the plan is realistic and that there is a
sense of collective ownership (Heagney, 2022; Williams, 2023). A well-structured WBS enables
LJMU - 7501 - BEGP - Project Management Fundamentals
​
6/12
Week 2 Notes
the team to transition from "what" is being built to "how" it will be built, providing the inputs for
sequencing activities and developing the project schedule (Abdullah, 2025; Heagney, 2022). In
agile projects, while a full WBS may be absent, the product backlog and user stories serve a
similar role in organizing and prioritising work into manageable increments (Mohammadreza
Samadzadeh et al., 2025; Abdullah, 2025; Williams, 2023). Ultimately, the WBS is the vital link
that integrates the project's scope with its time, cost, and resource management processes
(Abdullah, 2025; Project Management Institute, 2021).
Slide 11: Project Time Management: Scheduling and Activity Sequencing
Project time management is the process of planning, developing, and controlling the project
schedule to ensure timely completion (Abdullah, 2025; Pheng, 2022). The schedule is one of the
pillars of the triple constraint, and its effective management is integral to project success
(Abdullah, 2025; Irfan et al., 2021). The process begins with defining activities by further
breaking down the work packages from the WBS into individual units of work that can be
estimated (Abdullah, 2025; Pheng, 2022). Once activities are defined, the team must sequence
them based on their logical relationships and dependencies (Abdullah, 2025; Pheng, 2022).
These include mandatory (hard logic) dependencies required by technical or regulatory
standards, and discretionary (soft logic) dependencies based on preference or best practices
(Pheng, 2022; Abdullah, 2025).
Developing the project schedule requires estimating activity durations, which is often an
"educated guess" based on historical data, expert judgement, and analogous estimating
(Abdullah, 2025; Heagney, 2022). To improve accuracy and account for uncertainty, practitioners
often use three-point estimates, calculating a weighted average based on optimistic, most
likely, and pessimistic scenarios (Abdullah, 2025; Heagney, 2022). A critical innovation in
scheduling theory is the move toward 50/50 probability estimates combined with project
buffers, as proposed by the Critical Chain model (Richardson and Jackson, 2024). This
approach discourages task padding, which often leads to the student syndrome—the human
tendency to delay starting a task until the last possible moment (Richardson and Jackson, 2024).
By removing padding and using buffers, the project manager can better protect the completion
date while maintaining a culture of urgency and speed (Richardson and Jackson, 2024).
The Activity Network Diagram is the primary tool for calculating the critical path, the longest
sequence of tasks through the network that determines the earliest possible project finish (Pheng,
2022; Abdullah, 2025; Heagney, 2022). Tasks on the critical path have zero slack or float,
meaning any delay will directly impact the project's end date (Heagney, 2022; Abdullah, 2025). In
contrast, non-critical activities have some flexibility, which the project manager can leverage for
resource leveling (Heagney, 2022; Abdullah, 2025). The resulting schedule is typically visualised
as a Gantt chart, providing a clear roadmap for stakeholders (Abdullah, 2025; Richardson and
Jackson, 2024). However, practitioners must recognize that a Gantt chart without an underlying
network logic is merely a "wish list" rather than a valid management tool (Heagney, 2022;
Richardson and Jackson, 2024).
LJMU - 7501 - BEGP - Project Management Fundamentals
​
7/12
Week 2 Notes
Slide 12: Project Cost Management: Estimating and Budget Build-Up
Project cost management ensures that the project is completed within the approved budget, a
primary metric for judging project management success (Abdullah, 2025; Pheng, 2022). This
process is tightly linked to scope and time, as expansion in either typically leads to increased
costs (Abdullah, 2025; Heagney, 2022). Cost estimating involves calculating the expenses for all
resources—manpower, materials, machinery, and services—needed to complete the WBS
activities (Pheng, 2022; Abdullah, 2025). Early in the project life cycle, estimates may be Rough
Order of Magnitude (ROM) or "ballpark" figures, but they must become increasingly refined into
bottom-up estimates during the planning phase to ensure financial feasibility (Abdullah, 2025;
Richardson and Jackson, 2024).
The cost baseline is the authorised time-phased budget used to measure and monitor cost
performance (Project Management Institute, 2021; Abdullah, 2025). It is established through cost
aggregation, subtotaling the estimates of individual activities and work packages (Abdullah,
2025; Project Management Institute, 2021). A vital component of the budget is reserve analysis,
which sets aside funds to manage uncertainty (Abdullah, 2025; Richardson and Jackson, 2024).
Contingency reserves are allocated for "known-unknowns"—identified risks for which response
strategies have been developed (Abdullah, 2025; Project Management Institute, 2021). In
contrast, management reserves are set aside for "unknown-unknowns"—unforeseen situations
like natural disasters or sudden regulatory changes (Abdullah, 2025; Project Management
Institute, 2021; Richardson and Jackson, 2024).
Effective cost management also requires a robust procurement management plan to identify
whether resources should be "made" in-house or "bought" from external vendors (Abdullah,
2025; Pheng, 2022). Make-or-buy analysis considers factors like cost, expertise, and
confidentiality before selecting a contract type (Abdullah, 2025; Pheng, 2022). Common
contracts include Fixed Price, where the seller assumes the risk of cost overruns, and Cost
Reimbursable, where the buyer assumes more risk (Abdullah, 2025; Pheng, 2022). During
execution, the project manager must monitor cost variance (CV) by comparing actual costs
(AC) against the planned value (PV) and earned value (EV) (Abdullah, 2025; Heagney, 2022).
This Earned Value Management (EVM) approach provides the transparency necessary to
detect budget issues early and take corrective actions before the project's financial situation
becomes unrecoverable (Abdullah, 2025; Heagney, 2022; Irfan et al., 2021).
Slide 13: Project Resource Management: Allocation and Optimization
Resource management involves the efficient and effective deployment of an organisation's
resources—human, physical, and services—when they are needed (Abdullah, 2025; Pheng,
2022). In the project context, human resources include the core project team and subject
matter experts, while physical resources encompass equipment, materials, infrastructure, and
IT software (Abdullah, 2025). The process begins with resource planning, identifying the types
and quantities of resources required for each WBS activity (Abdullah, 2025; Williams, 2023). A
Resource Breakdown Structure (RBS) is a useful hierarchical tool for visualising these needs
and ensuring that no critical requirement is overlooked (Abdullah, 2025; Project Management
Institute, 2021).
LJMU - 7501 - BEGP - Project Management Fundamentals
​
8/12
Week 2 Notes
A significant challenge in contemporary project environments is resource availability, as
projects often compete for a single pool of scarce resources within a host organisation (Butler,
2022; Abdullah, 2025; Richardson and Jackson, 2024). Resource loading involves assigning
specific resources to activities based on the project schedule, while resource leveling is a
technique used to resolve overallocations or conflicts (Abdullah, 2025; Richardson and Jackson,
2024). For example, if a systems analyst is scheduled to work 64 hours in a single week, the
project manager must shift tasks or adjust start dates to stay within the standard 40-hour
capacity (Abdullah, 2025). This often results in a longer project duration but ensures a more
sustainable workload and higher team morale (Richardson and Jackson, 2024; Abdullah, 2025;
Heagney, 2022).
Managing the project team also requires soft skills and leadership behaviors to navigate
conflicts and promote team building (Abdullah, 2025; Heagney, 2022). The Tuckman ladder
describes the stages of team development—forming, storming, norming, performing, and
adjourning—and the project manager must adapt their leadership style accordingly (Abdullah,
2025; Mohammadreza Samadzadeh et al., 2025). To promote productive involvement, a team
charter should be developed to establish ground rules, values, and working agreements
(Abdullah, 2025; Mohammadreza Samadzadeh et al., 2025). Furthermore, the use of a RACI chart
(Responsible, Accountable, Consulted, Informed) provides clarity regarding roles and
responsibilities, minimising misunderstandings and ensuring that decision-making is
streamlined (Williams, 2023; Abdullah, 2025). Ultimately, successful resource management is
about matching the right skills to the right tasks at the right time, a critical driver of
productivity and project success (Richardson and Jackson, 2024; Abdullah, 2025; Irfan et al.,
2021).
Slide 14: Project Risk Management: Identifying and Mitigating Uncertainty
Risk management is the systematic process of identifying, analysing, and responding to
uncertainty within a project (Heagney, 2022; Abdullah, 2025). A risk is defined as an uncertain
event or condition that, if it occurs, has a positive or negative effect on one or more project
objectives (Abdullah, 2025; Project Management Institute, 2021). Negative risks are called
threats, while positive risks are opportunities (Abdullah, 2025; Project Management Institute,
2021). Master-level practitioners must recognize that no project is risk-free; hence, the goal is to
reduce the likelihood of "surprises" and proactively manage potential impacts on scope,
schedule, cost, and quality (Heagney, 2022; Abdullah, 2025; Irfan et al., 2021).
The risk identification process should be collaborative, involving the project team, sponsors,
and subject matter experts to leverage the organisation's "intellectual capital" (Heagney, 2022;
Williams, 2023). Tools like the fishbone (Ishikawa) diagram help identify root causes, while the
Risk Breakdown Structure (RBS) provides a framework for categorizing risks—technical,
financial, external, or management (Abdullah, 2025; Williams, 2023). Once identified, risks are
recorded in a risk register and evaluated through qualitative risk analysis (Abdullah, 2025;
Heagney, 2022). This involves assessing each risk's probability of occurrence and its potential
impact, using a probability-impact matrix to assign a severity score (Abdullah, 2025; Heagney,
2022; Yang and Yin, 2023). High-severity risks require immediate attention and the development
of formal risk response strategies (Abdullah, 2025).
LJMU - 7501 - BEGP - Project Management Fundamentals
​
9/12
Week 2 Notes
Risk response planning explores different actions for handling threats—such as avoidance
(changing the plan), mitigation (reducing probability/impact), transfer (using insurance or
vendors), or acceptance (Heagney, 2022; Abdullah, 2025). For opportunities, strategies include
exploitation (ensuring the risk happens), enhancement, or sharing (Abdullah, 2025; Project
Management Institute, 2021). It is also vital to identify risk owners responsible for monitoring
triggers (early warning signs) and implementing contingency plans (Abdullah, 2025; Richardson
and Jackson, 2024). Developing a robust risk culture within the team ensures that everyone is
vigilant and that uncertainty is managed as a "way of life" in VUCA environments (Zaman et al.,
2022; Richardson and Jackson, 2024). Ultimately, effective risk management increases the
predictability of project outcomes and protects the organisation's system for value delivery
(Zaman et al., 2022; Abdullah, 2025; Yang and Yin, 2023).
Slide 15: Quality Management and Performance Metrics: Ensuring Excellence
Project quality management involves the processes required to ensure that the project will
satisfy the needs for which it was undertaken (Project Management Institute, 2021; Abdullah,
2025). Quality is often defined through two lenses: conformance to requirements (meeting the
stated specifications) and fitness for purpose (satisfying the customer's actual needs) (Pheng,
2022; Abdullah, 2025). It is important to distinguish between quality and grade; a low-grade
product (with fewer features) can still be high-quality if it is free of defects and meets its specified
requirements (Pheng, 2022; Abdullah, 2025). High quality is achieved through prevention rather
than inspection, emphasizing a "right first time" culture to avoid the high costs of rework
(Pheng, 2022; Abdullah, 2025).
The quality management plan defines the quality standards, metrics, and checklists that will
be used to assess the deliverables (Abdullah, 2025; Williams, 2023). To ensure continuous
improvement, project teams often adopt the Deming cycle—Plan-Do-Check-Act (PDCA)—an
iterative approach that seeks to improve work processes based on data and feedback (Pheng,
2022; Abdullah, 2025; Heagney, 2022). In the monitoring and control phase, the team conducts
quality control to measure the actual performance of the project outcomes and identify
variances (Abdullah, 2025; Pheng, 2022). Tools like statistical sampling, control charts, and
trend analysis help determine if the process is "under control" and within acceptable variance
ranges (Pheng, 2022; Heagney, 2022).
Quality assurance is the companion process that focuses on the management processes
themselves, ensuring that the team is following the defined procedures and using the correct
tools (Abdullah, 2025; Pheng, 2022). Quality audits are conducted by internal or external parties
to identify process gaps and recommend corrective actions (Abdullah, 2025; Pheng, 2022).
Furthermore, the project manager must ensure that stakeholder satisfaction remains a primary
quality metric, as a project that meets all technical specs but fails to please the customer is
ultimately a failure (Abdullah, 2025; Project Management Institute, 2021; Irfan et al., 2021). By
building excellence into the project's "DNA" through Lean Six Sigma or other performance
domains, organisers can deliver robust, sustainable outcomes that provide lasting
organisational value (Mohammadreza Samadzadeh et al., 2025; Abdullah, 2025; Zaman et al.,
2022).
LJMU - 7501 - BEGP - Project Management Fundamentals
​
10/12
Week 2 Notes
Slide 16: Deliverables, Milestones, and the Phase-Gate Approval Process
The culmination of the definition, initiation, and planning processes is a set of defined project
deliverables—the unique and verifiable products, results, or services that the project was
undertaken to produce (Abdullah, 2025; Williams, 2023). Deliverables can be internal
(intermediate documents like a WBS or blueprint) or external (the final functioning system or
building) (Abdullah, 2025; Project Management Institute, 2021). To manage the project effectively,
these deliverables are linked to milestones, significant points or events in the project life cycle
that mark the completion of a major phase of work (Pheng, 2022; Williams, 2023). Milestones act
as the "heartbeat" of the project, providing stakeholders with tangible evidence of progress and
serving as critical governance checkpoints (Williams, 2023; Abdullah, 2025).
A core practice in strategic project management is the use of phase-gate approvals, also
known as "go/no-go" decision points (Butler, 2022; Pheng, 2022). At the end of each life cycle
phase, the project team must present its results to a steering committee or project sponsor
for evaluation (Butler, 2022; Williams, 2023; Abdullah, 2025). This phase-gate review assesses
whether the project is still on track regarding scope, schedule, and cost, and whether the
business case remains valid (Butler, 2022; Abdullah, 2025; Irfan et al., 2021). If a project no
longer aligns with corporate strategy or if the risks have become unacceptable, the organisation
must have the discipline to terminate the project to prevent further waste of resources (Butler,
2022; Richardson and Jackson, 2024; Abdullah, 2025).
Passing through a stage-gate requires formal sign-off and deliverable verification, ensuring
that the work meets the agreed-on acceptance criteria (Butler, 2022; Abdullah, 2025). This
process of scope verification provides the client with the assurance that the project is delivering
the envisioned value (Pheng, 2022; Abdullah, 2025). Furthermore, lessons learned should be
captured at each gate to foster organisational learning and improve performance in subsequent
phases (Williams, 2023; Abdullah, 2025; Heagney, 2022). As we conclude Week 2, students
should appreciate that the transition from planning to execution is not automatic; it is a
controlled process underpinned by rigorous documentation, governance, and a relentless
focus on strategic success (Butler, 2022; Abdullah, 2025; Zaman et al., 2022).
References
Abdullah, A. (2025). Project Management, Navigating the Complexity with a Systematic Approach,
2nd Edition. Cleveland: MSL Academic Endeavors.
Butler, M. J. (2022). Project portfolio management practices – a theoretical base and practitioner
guidelines. International Journal of Project Organisation and Management, 14(1), pp. 65-88.
Heagney, J. J. (2022). Fundamentals of Project Management, 6th Edition. Nashville: HarperCollins
Leadership.
Irfan, M., Khan, S. Z., Hassan, N., Hassan, M., Habib, M., Khan, S. and Khan, H. H. (2021). Role
of Project Planning and Project Manager Competencies on Public Sector Project Success.
Sustainability, 13(3), 1421.
Mohammadreza Samadzadeh, M., Arab, A. and Valami, M. B. (2025). Agile Project Management
for Information Technology. Ottawa: Library and Archives Canada.
LJMU - 7501 - BEGP - Project Management Fundamentals
​
11/12
Week 2 Notes
Pheng, L. S. (2022). Project Management for the Built Environment: Study Notes. Singapore:
Springer Nature.
Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge
(PMBOK® Guide) – Seventh Edition and The Standard for Project Management. Newtown
Square, PA: Project Management Institute.
Richardson, G. L. and Jackson, B. M. (2024). Optimizing Project Work, Management, and
Delivery. Boca Raton: CRC Press.
Wiliams, R. T. (2023). Project Management Toolkit: Essential Resources for Beginners. [E-book].
Yang, J. and Yin, S. (2023). Risk Management for Housing and Construction Projects. Journal of
Engineering, Project, and Production Management, 14(1), 0011.
Zaman, U., Khan, M. N., Raza, S. H. and Farías, P. (2022). Fall Seven Times, Stand Up Eight:
Linking Project Management Innovation, Project Governance, and High-Performance Work
Practices to Project Success. Frontiers in Psychology, 13, 902816.
LJMU - 7501 - BEGP - Project Management Fundamentals
​
12/12