, PRO4801
ASSIGNMENT 3 2026
DUE AUGUST 2026
Question 3.1
Distinguishing Steps in the Project Planning Process and Their Purpose
1. Introduction
The ABC project's pronounced difficulties—ranging from scheduling delays and cost overruns to
ambiguous product specifications—underscore a critical failure in foundational planning. According
to Kerzner and Kerzner (2017), poor planning is one of the most consistent predictors of project
failure, irrespective of industry or project size. In the case of ABC, the absence of a structured
planning framework was compounded by an inexperienced project manager and the lack of a
functioning Project Management Office (PMO), which could have provided methodological
guidance. As a consultant with training from PRO4801 and extensive practical experience, I address
the core planning deficiencies by distinguishing the sequential steps in the project planning process
and explaining the purpose of the questions answered at each stage. This structured approach is
intended to restore confidence in the project's governance and execution capacity.
2. The Foundational Role of Project Planning
Project planning is not merely an administrative exercise but the strategic backbone of project
success. As noted by the Project Management Institute (PMI) (2021), the planning process group
consumes a significant proportion of project effort and establishes the baselines against which all
subsequent performance is measured. Without a robust plan, a project cannot demonstrate that it
is under control (Schwalbe, 2018). For ABC, the absence of such control likely explains the
cascading failures in budget and schedule. A well-constructed project plan provides a roadmap,
facilitates communication among stakeholders, enables resource optimisation, and serves as an
early-warning system for risks (Pinto, 2019). To achieve these benefits, the planning process must
answer six essential questions: What? Why? How? Who? Where? When? and How much?
(Meredith, Mantel and Shafer, 2017). Each question corresponds to a distinct planning step, which I
now distinguish and elaborate upon.
3. Step 1: Defining Project Objectives and Scope (Answering What? and Why?)
3.1 Nature and Purpose of This Step
The inaugural step in project planning concerns defining the project's purpose and deliverables.
This involves articulating clear, measurable objectives that align with organisational strategy and
specifying the boundaries of the work to be performed—commonly referred to as scope definition
(PMI, 2021). For ABC, this would entail producing a project charter and a preliminary scope
statement that delineates what the project will and will not deliver. The questions What? and Why?
serve to anchor all subsequent planning activities. Without answering these, the project risks
delivering outputs that do not meet customer expectations, a problem explicitly noted in ABC's
case.
, 3.2 Typical Questions and Their Purpose
Typical questions in this step include:
What is the product or service to be delivered?
What problem does this project solve?
What are the measurable success criteria?
Why is this project necessary for the organisation?
The purpose of these questions is to ensure that the project is aligned with business strategy and
that all stakeholders share a common understanding of the end goal (Kerzner and Kerzner, 2017).
According to Larson and Gray (2021), a well-defined scope statement reduces the likelihood of
scope creep, which is a frequent cause of budget overruns. For ABC, answering these questions
would have provided a clear reference point for evaluating change requests and maintaining focus
on value-for-money outcomes, a key concern raised by the customer.
4. Step 2: Developing the Work Breakdown Structure and Activity Definition (Answering How?)
4.1 Nature and Purpose of This Step
Once the scope is defined, the next step is to decompose the project work into manageable
components. This is achieved through the Work Breakdown Structure (WBS), which subdivides
deliverables into smaller work packages and, ultimately, into individual activities (Schwalbe, 2018).
The central question at this stage is How?—how will the project deliver the defined outputs? For
ABC, this would involve breaking down the product specification development into discrete tasks
such as requirements gathering, design iterations, and quality reviews.
4.2 Typical Questions and Their Purpose
Typical questions include:
What activities must be performed to produce each deliverable?
What are the dependencies among these activities?
What level of detail is required for effective control?
The purpose of this step is to create a comprehensive inventory of all work required, thereby
preventing omissions that could cause delays later (Meredith, Mantel and Shafer, 2017). The WBS
also serves as a foundation for estimating cost, time, and resources. Project Management Institute
(2021) emphasises that the WBS must be developed with input from the team to ensure buy-in and
accuracy. In ABC's context, poor planning likely meant that activities were not adequately
decomposed, leading to unrealistic schedules and resource misallocation.
5. Step 3: Sequencing Activities and Developing the Schedule (Answering When?)
5.1 Nature and Purpose of This Step
With activities defined, the planner must determine their logical sequence and establish a timeline.
This involves identifying dependencies, estimating durations, and developing a project schedule,
often using tools such as Gantt charts or network diagrams (Pinto, 2019). The question When? is
central here. For ABC, an experienced project manager would have used techniques like the Critical
Path Method (CPM) to identify activities that directly impact the project completion date.
ASSIGNMENT 3 2026
DUE AUGUST 2026
Question 3.1
Distinguishing Steps in the Project Planning Process and Their Purpose
1. Introduction
The ABC project's pronounced difficulties—ranging from scheduling delays and cost overruns to
ambiguous product specifications—underscore a critical failure in foundational planning. According
to Kerzner and Kerzner (2017), poor planning is one of the most consistent predictors of project
failure, irrespective of industry or project size. In the case of ABC, the absence of a structured
planning framework was compounded by an inexperienced project manager and the lack of a
functioning Project Management Office (PMO), which could have provided methodological
guidance. As a consultant with training from PRO4801 and extensive practical experience, I address
the core planning deficiencies by distinguishing the sequential steps in the project planning process
and explaining the purpose of the questions answered at each stage. This structured approach is
intended to restore confidence in the project's governance and execution capacity.
2. The Foundational Role of Project Planning
Project planning is not merely an administrative exercise but the strategic backbone of project
success. As noted by the Project Management Institute (PMI) (2021), the planning process group
consumes a significant proportion of project effort and establishes the baselines against which all
subsequent performance is measured. Without a robust plan, a project cannot demonstrate that it
is under control (Schwalbe, 2018). For ABC, the absence of such control likely explains the
cascading failures in budget and schedule. A well-constructed project plan provides a roadmap,
facilitates communication among stakeholders, enables resource optimisation, and serves as an
early-warning system for risks (Pinto, 2019). To achieve these benefits, the planning process must
answer six essential questions: What? Why? How? Who? Where? When? and How much?
(Meredith, Mantel and Shafer, 2017). Each question corresponds to a distinct planning step, which I
now distinguish and elaborate upon.
3. Step 1: Defining Project Objectives and Scope (Answering What? and Why?)
3.1 Nature and Purpose of This Step
The inaugural step in project planning concerns defining the project's purpose and deliverables.
This involves articulating clear, measurable objectives that align with organisational strategy and
specifying the boundaries of the work to be performed—commonly referred to as scope definition
(PMI, 2021). For ABC, this would entail producing a project charter and a preliminary scope
statement that delineates what the project will and will not deliver. The questions What? and Why?
serve to anchor all subsequent planning activities. Without answering these, the project risks
delivering outputs that do not meet customer expectations, a problem explicitly noted in ABC's
case.
, 3.2 Typical Questions and Their Purpose
Typical questions in this step include:
What is the product or service to be delivered?
What problem does this project solve?
What are the measurable success criteria?
Why is this project necessary for the organisation?
The purpose of these questions is to ensure that the project is aligned with business strategy and
that all stakeholders share a common understanding of the end goal (Kerzner and Kerzner, 2017).
According to Larson and Gray (2021), a well-defined scope statement reduces the likelihood of
scope creep, which is a frequent cause of budget overruns. For ABC, answering these questions
would have provided a clear reference point for evaluating change requests and maintaining focus
on value-for-money outcomes, a key concern raised by the customer.
4. Step 2: Developing the Work Breakdown Structure and Activity Definition (Answering How?)
4.1 Nature and Purpose of This Step
Once the scope is defined, the next step is to decompose the project work into manageable
components. This is achieved through the Work Breakdown Structure (WBS), which subdivides
deliverables into smaller work packages and, ultimately, into individual activities (Schwalbe, 2018).
The central question at this stage is How?—how will the project deliver the defined outputs? For
ABC, this would involve breaking down the product specification development into discrete tasks
such as requirements gathering, design iterations, and quality reviews.
4.2 Typical Questions and Their Purpose
Typical questions include:
What activities must be performed to produce each deliverable?
What are the dependencies among these activities?
What level of detail is required for effective control?
The purpose of this step is to create a comprehensive inventory of all work required, thereby
preventing omissions that could cause delays later (Meredith, Mantel and Shafer, 2017). The WBS
also serves as a foundation for estimating cost, time, and resources. Project Management Institute
(2021) emphasises that the WBS must be developed with input from the team to ensure buy-in and
accuracy. In ABC's context, poor planning likely meant that activities were not adequately
decomposed, leading to unrealistic schedules and resource misallocation.
5. Step 3: Sequencing Activities and Developing the Schedule (Answering When?)
5.1 Nature and Purpose of This Step
With activities defined, the planner must determine their logical sequence and establish a timeline.
This involves identifying dependencies, estimating durations, and developing a project schedule,
often using tools such as Gantt charts or network diagrams (Pinto, 2019). The question When? is
central here. For ABC, an experienced project manager would have used techniques like the Critical
Path Method (CPM) to identify activities that directly impact the project completion date.
