On this page & study actions
Assessed progress
Sign in and complete the verified MCQs to track mastery.
Unit 1: Project Planning10 min read
Defining project scope is the foundational process of establishing what is, and what is not, part of a project. It sets clear boundaries, outlines deliverables, and identifies the work required to achieve project objectives, thereby preventing scope creep and ensuring project success.
A systematic approach to defining project scope helps ensure all stakeholders are aligned and the project remains focused.
Every project begins with a purpose.
Project managers and key stakeholders must agree upon all project requirements. Beyond the scope itself, this includes:
This is a detailed narrative of all the work that needs to be done to complete the project successfully. It clearly defines:
Project exclusions are specific statements defining what is explicitly NOT part of the project. Examples include:
Constraints are factors that limit the project team's options. The most common are often referred to as the triple constraint:
Other important constraints can include:
Identifying potential constraints early allows for proactive planning and mitigation strategies.
Assumptions are factors that, for planning purposes, are considered to be true, real, or certain without proof or demonstration. They often relate to potential constraints. For example:
These are the tangible or intangible outputs that your team needs to produce to meet the business objectives. Deliverables can include:
A Work Breakdown Structure (WBS) is a hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish project objectives and create required deliverables. It divides a large, complex project into smaller, more manageable, and independent tasks.
The WBS visually represents the project's scope and deliverables in a tree-like structure, with the project name at the root.
Steps to Create a WBS:
Here's an ASCII art example of a simple WBS for "Website Development":
Project: Website Development ├── 1. Project Management │ ├── 1.1 Planning │ ├── 1.2 Monitoring & Control │ └── 1.3 Closing ├── 2. Design Phase │ ├── 2.1 Wireframing │ ├── 2.2 UI/UX Design │ └── 2.3 Mockups Creation ├── 3. Development Phase │ ├── 3.1 Front-end Development │ │ ├── 3.1.1 HTML Structure │ │ ├── 3.1.2 CSS Styling │ │ └── 3.1.3 JavaScript Interactivity │ └── 3.2 Back-end Development │ ├── 3.2.1 Database Setup │ ├── 3.2.2 API Implementation │ └── 3.2.3 Server-side Logic ├── 4. Testing Phase │ ├── 4.1 Unit Testing │ ├── 4.2 Integration Testing │ └── 4.3 User Acceptance Testing (UAT) └── 5. Deployment Phase ├── 5.1 Server Configuration ├── 5.2 Code Deployment └── 5.3 Go-Live
After defining the WBS, tools are needed to visualize the project schedule and task dependencies.
A Gantt chart is a horizontal bar chart commonly used in project management to visually represent tasks scheduled over time.
Here's a conceptual ASCII art representation of a Gantt Chart:
Task A | [===== ]| | | | Task B | | [=======]| | | Task C | | | [=== ] | | Task D | | | | [=========]|
A network diagram is a schematic representation showing all project tasks, their dependencies, and the flow of work. They visualize the project schedule, focusing on the logical relationships between activities.
Benefits of Network Diagrams:
Types of Project Network Diagrams:
PDM Dependency Relationships:
Here's an ASCII art example of a simple PDM network diagram:
+-----+ +-----+ +-----+ | A |----->| B |----->| C | | (3) | FS | (5) | FS | (4) | +-----+ +-----+ +-----+ | ^ | FS | SS v | +-----+ +-----+ | D |----->| E | | (2) | FF | (6) | +-----+ +-----+ Numbers in parentheses indicate task durations.
The Critical Path Method (CPM) is a project management technique for scheduling project activities. It helps identify the longest sequence of dependent tasks (the critical path) that determines the minimum time required to complete the project.
CPM's Two Main Functions:
Steps to Calculate the Critical Path:
The Program Evaluation and Review Technique (PERT) is a project management tool used to schedule, organize, and coordinate tasks within a project, especially when activity durations are uncertain. Unlike CPM, which often uses single-point estimates, PERT employs a probabilistic approach to time estimation.
Steps to Create a PERT Chart:
Identify project tasks: List all necessary project activities.
Define task dependencies: Determine the logical relationships between tasks (e.g., which tasks must precede others). These dependencies are visualized by connecting tasks.
Connect project tasks: Represent tasks as arrows and events/milestones as nodes (circles) in a network diagram.
Estimate project time frame: For each task, estimate three time durations:
Using these, calculate the Expected Duration () for each task with the PERT formula: The expected duration is then used to calculate the project's overall completion time, often by applying CPM principles to the PERT network.
Key Terms in PERT:
In software development, defining scope means specifying which features or functionalities are part of the current release or iteration. This C++ example simulates a ScopeChecker that verifies if a requested feature is within the project's defined scope.
This simple C++ program illustrates how a program could conceptually enforce a predefined scope by checking if certain "features" or "tasks" are part of an allowed list. In a real-world scenario, this logic might be part of a larger system that validates requirements or user stories against the approved project scope document.
The comprehensive process of identifying and documenting the project's objectives, deliverables, tasks, and boundaries, ensuring a clear understanding of what is included and excluded.
A hierarchical decomposition of the total scope of work into smaller, more manageable tasks and work packages, serving as a foundational element for project planning.
A schedule network analysis technique that identifies the longest sequence of dependent activities (the critical path) in a project, determining the minimum project completion time.
A project management tool used to estimate project activity durations and completion times under conditions of uncertainty, utilizing optimistic, pessimistic, and most likely time estimates.
Constraints are limitations (e.g., time, budget, resources) that affect project performance, while exclusions are explicit statements of what is outside the project's boundaries.
Test your understanding with 5 questions
Which of the following is NOT typically considered one of the 'triple constraints' of project management?
The primary purpose of a Work Breakdown Structure (WBS) is to:
In the Precedence Diagramming Method (PDM), a 'Finish to Start' (FS) dependency means:
What is the primary difference between the Critical Path Method (CPM) and the Program Evaluation and Review Technique (PERT) regarding activity duration estimates?
A project manager is calculating the 'float' for tasks. Which statement accurately describes tasks on the critical path?
Manage task progress: Continuously track task completion, update the chart, and mitigate issues to ensure progress towards milestones.
6 Modules
6 Modules