INTRODUCTION TO
PROJECT MANAGEMENT
Comprehensive Lecture Notes for Beginners
────────────────────────────────────────────────────────────
Table of Contents
Table of Contents 2
1. What Is a Project? 4
1.1 Definition of a Project 4
1.2 Key Characteristics of Projects 4
1.3 Project vs. Operations 5
1.4 Real-World Examples of Projects 5
2. Why Are Projects Needed? 6
2.1 Business Drivers for Projects 6
2.2 The Value Projects Deliver to Organizations 6
2.3 Projects and Organizational Strategy 6
3. Elements of a Good Project 6
3.1 Clear Objectives and Scope 7
3.2 Committed Sponsorship and Governance 7
3.3 Competent Project Manager 7
3.4 Engaged Stakeholders 7
3.5 Realistic Planning 7
3.6 Effective Risk Management 7
3.7 Open Communication 8
3.8 Summary — Elements of a Good Project 8
4. Phases in Project Management — The PMI Framework 8
4.1 Overview of the PMI Process Groups 8
4.2 Initiating Process Group ★ (Detailed Coverage) 9
4.2.1 What Happens During Initiation? 9
4.2.2 Inputs to the Initiating Process Group 10
4.2.3 Tools and Techniques Used in Initiation 10
4.2.4 Outputs of the Initiating Process Group 10
The Project Charter 10
The Assumption Log 11
The Stakeholder Register 11
4.2.5 Stakeholder Identification Process 12
4.2.6 Feasibility and Selection Methods 12
4.3 Planning Process Group 12
4.4 Executing Process Group 12
4.5 Monitoring and Controlling Process Group 13
4.6 Closing Process Group 13
5. Project Management Methodologies 13
5.1 Waterfall Methodology (Traditional / Predictive) 14
5.1.1 Overview 14
5.1.2 The Waterfall Phases 14
5.1.3 When to Use Waterfall 14
5.1.4 Advantages and Disadvantages of Waterfall 15
5.2 Agile Methodology (Iterative / Adaptive) 15
5.2.1 Overview and the Agile Manifesto 15
5.2.2 How Agile Works — The Sprint Cycle 15
5.2.3 Key Agile Roles (Scrum) 15
5.2.4 When to Use Agile 16
5.2.5 Advantages and Disadvantages of Agile 16
5.3 Waterfall vs. Agile — Detailed Comparison 16
5.4 Hybrid Approaches 16
6. Summary and Key Takeaways 17
1. What Is a Project?
1.1 Definition of a Project
A project is a temporary endeavor undertaken to create a unique product, service, or result. This definition,
drawn from the PMI PMBOK® Guide, captures two fundamental attributes that distinguish a project from day-to-
day operational work: it is temporary (has a definite beginning and end) and it produces something unique.
📌 PMI Definition
"A project is a temporary endeavor undertaken to create a unique product, service, or result."
— PMBOK® Guide, 7th Edition, Project Management Institute
1.2 Key Characteristics of Projects
Every project shares several defining characteristics that separate it from routine organizational activities:
● Temporary: Projects have a defined start and end date. Once the objective is achieved, the project concludes
— unlike operations, which are ongoing.
● Unique Output: Every project produces a one-of-a-kind deliverable — a building, a software application, a
marketing campaign, or a research report.
● Progressive Elaboration: Project details are developed step by step as more information becomes available
throughout its lifecycle.
● Uncertainty & Risk: Because projects venture into new territory, they inherently carry uncertainty and
require proactive risk management.
● Cross-Functional Teams: Projects typically bring together specialists from multiple departments or
organizations to achieve a common goal.
● Resource Constraints: Projects must be delivered within defined limits of time, cost, scope, and quality —
often referred to as the Triple Constraint.
Figure 1.1 – The Triple Constraint: Scope, Time, and Cost, balanced around Quality
1.3 Project vs. Operations
Understanding the difference between projects and operations is essential for every aspiring project manager:
Dimension Project Operations
Duration Temporary (fixed start & end) Ongoing, continuous
Output Unique product/service/result Standardized, repetitive
Team Assembled for the project Permanent functional teams
Objective Achieve a specific goal then close Sustain and improve performance
1.4 Real-World Examples of Projects
Projects exist in every industry and at every scale. Here are representative examples across sectors:
● Construction: Building a hospital, bridge, or residential apartment complex.
● Information Technology: Developing a mobile banking application or migrating a company's data to a cloud
platform.
● Healthcare: Implementing an Electronic Health Records (EHR) system across a hospital network.
● Manufacturing: Designing and launching a new electric vehicle model.
● Education: Developing a new online degree programme, including curriculum design, content creation, and
platform deployment.
● Event Management: Planning and executing a national conference or corporate product launch event.
2. Why Are Projects Needed?
2.1 Business Drivers for Projects
Organizations initiate projects in response to a variety of internal and external forces. These drivers provide the
justification — the "why" — behind every project investment:
● Market Demand: A telecommunications company launches a project to deploy 5G infrastructure in response
to growing consumer demand for faster connectivity.
● Strategic Opportunity: A retailer initiates a project to enter a new emerging market before competitors
establish dominance.
● Regulatory/Legal Requirement: A financial institution executes a compliance project to meet new data
protection regulations (e.g., GDPR, DORA).
● Technological Advancement: An airline implements an AI-powered predictive maintenance system to
replace legacy processes.
● Customer Request: A software vendor develops a custom integration feature specifically requested by a key
enterprise client.
● Organizational Need: A company restructures its HR processes and launches a change-management project
to improve employee retention.
● Social Need / Environmental Concern: A government sponsors a clean-energy project to reduce carbon
emissions and meet international climate commitments.
2.2 The Value Projects Deliver to Organizations
When executed well, projects are the primary mechanism through which organizations create value and achieve
strategic objectives. The value can be tangible or intangible:
Tangible Value Intangible Value
Increased revenue or market share Enhanced brand reputation
Cost savings through process improvements Improved employee morale and capability
New physical or digital assets Better customer experience and loyalty
Compliance and legal protection Knowledge and intellectual capital
2.3 Projects and Organizational Strategy
Effective organizations align their project portfolio with their strategic plan. This alignment ensures that every
project dollar spent moves the organization closer to its long-term vision. The connection flows from strategy to
programs to individual projects:
1. Strategy defines goals (e.g., "Become the market leader in AI-driven logistics").
2. Programs group related projects that collectively deliver a strategic benefit.
3. Projects execute the specific work that produces change.
4. Operations sustain and exploit the capabilities created by projects.
3. Elements of a Good Project
A project does not succeed simply because it is completed. Success is measured against agreed criteria. Research
by PMI and the Standish Group consistently identifies the following elements as critical differentiators between
successful and failing projects:
3.1 Clear Objectives and Scope
Every successful project begins with unambiguous, measurable objectives. The SMART framework is widely used
to validate them:
● S – Specific: The objective defines exactly what will be accomplished.
● M – Measurable: Success criteria are quantifiable.
● A – Achievable: The objective is realistic given available resources.
● R – Relevant: It aligns with organizational strategy and stakeholder needs.
● T – Time-Bound: There is a clear deadline or milestone date.
3.2 Committed Sponsorship and Governance
A project sponsor — typically a senior executive — provides strategic direction, resources, and organizational
authority. Without active sponsorship, projects struggle to resolve escalated issues, secure funding, and maintain
organizational priority.
3.3 Competent Project Manager
The project manager is the individual responsible for leading the team, managing stakeholder expectations, and
delivering outcomes. According to PMI, effective project managers demonstrate competence in three
dimensions:
● Technical PM skills (scheduling, budgeting, risk management)
● Leadership and interpersonal skills (communication, motivation, conflict resolution)
● Strategic and business management acumen (understanding the organizational context)
3.4 Engaged Stakeholders
Stakeholders are individuals or groups who affect or are affected by the project. Early and sustained stakeholder
engagement prevents scope creep, reduces resistance to change, and improves decision-making quality.
Stakeholder management is now a standalone Knowledge Area in the PMBOK® Guide.
3.5 Realistic Planning
A good plan is one that the team can actually execute. Over-optimistic schedules and budgets are among the
leading causes of project failure. Realistic plans are built with:
● Bottom-up estimation from the people doing the work
● Historical data from similar past projects
● Explicit contingency reserves for identified risks
● Regular review and baseline re-alignment as the project progresses
3.6 Effective Risk Management
Proactive risk management identifies potential threats and opportunities before they occur and plans responses
accordingly. The key steps include:
1. Identify risks through brainstorming, expert interviews, and risk checklists.
2. Analyze risks qualitatively (probability × impact) and quantitatively where warranted.
3. Plan risk responses: avoid, transfer, mitigate, or accept.
4. Monitor and control risks throughout the project lifecycle.
3.7 Open Communication
Studies show project managers spend approximately 90% of their time communicating. A communication plan
defines who needs what information, in what format, and how frequently. Good communication ensures
everyone is aligned and issues surface early.
3.8 Summary — Elements of a Good Project
Element Purpose Risk if Missing
Clear Objectives Defines success criteria Scope creep, rework
Strong Sponsorship Provides authority & resources Funding gaps, unresolved issues
Competent PM Leads planning & execution Poor coordination, missed
deadlines
Engaged Stakeholders Aligns expectations Resistance, late requirements
Realistic Plan Sets achievable baselines Budget & schedule overruns
Risk Management Anticipates threats Unplanned disruptions
Communication Keeps everyone informed Misalignment, conflict
4. Phases in Project Management — The PMI Framework
4.1 Overview of the PMI Process Groups
The Project Management Institute (PMI) organizes project management activities into five Process Groups. These
are NOT sequential project phases; rather, they are clusters of logically related processes that can overlap and
interact throughout the project lifecycle.
Figure 4.1 – The Five PMI Process Groups and their Feedback Loop
Figure 4.2 – Effort Distribution Across the Five Process Groups
Process Group Primary Focus Key Deliverable(s)
Initiating Authorize and define the project Project Charter, Stakeholder
Register
Planning Develop the roadmap for delivery Project Management Plan
Executing Perform the work per the plan Deliverables, Work Performance
Data
Monitoring & Controlling Track, review, and regulate Change Requests, Performance
progress Reports
Closing Formally complete the project or Final Report, Lessons Learned
phase
4.2 Initiating Process Group ★ (Detailed Coverage)
The Initiating Process Group is the foundation upon which the entire project rests. It is during initiation that the
project is formally authorized, its high-level objectives are established, and key stakeholders are identified. A
weak initiation phase is the number-one predictor of project failure — because problems not caught here
compound at every subsequent stage.
⭐ Why Initiation Matters
Research by PMI shows that organizations with mature initiation processes waste 28 times LESS money than those with
poor initiation practices.
Every dollar spent on thorough initiation saves an estimated $10–$100 in rework costs downstream.
4.2.1 What Happens During Initiation?
Initiation answers four critical questions:
● WHAT is the project trying to achieve?
● WHY is this project being undertaken (business justification)?
● WHO are the key stakeholders and decision-makers?
● Is this project FEASIBLE and aligned with organizational strategy?
4.2.2 Inputs to the Initiating Process Group
Business Case: A formal document that justifies the project investment. It outlines the problem/opportunity,
proposed solution, costs, benefits, and risks. The Business Case answers the fundamental question: "Is this
project worth doing?"
Benefits Management Plan: Describes how and when the benefits of the project will be realized, who is
responsible for realizing them, and how they will be measured.
Agreements (Contracts): If the project is delivered by an external vendor or contractor, the contract serves as a
key input, defining obligations, deliverables, and terms.
Enterprise Environmental Factors (EEFs): Internal and external conditions that influence how the project is
managed: organizational culture, market conditions, industry regulations, and available technology platforms.
Organizational Process Assets (OPAs): Templates, historical records, policies, and lessons learned from previous
projects that can be leveraged to accelerate the initiation process.
4.2.3 Tools and Techniques Used in Initiation
Expert Judgment: Input from individuals or groups with specialized knowledge — PMO staff, senior managers,
subject matter experts, or external consultants. Used extensively to assess feasibility, estimate costs, and identify
risks.
Data Gathering: Structured approaches to collecting information:
• Brainstorming sessions to generate ideas and identify stakeholders.
• Interviews with key stakeholders to capture requirements and expectations.
• Focus groups to understand end-user needs.
Interpersonal and Team Skills: Facilitation: guiding group discussions to achieve consensus on project objectives.
Conflict management: handling disagreements among stakeholders early.
Active listening: ensuring all perspectives are captured.
Meetings: The Project Kick-Off meeting is typically held at the end of initiation. It formally announces the project,
introduces the team, clarifies roles, and aligns everyone on objectives and initial plans.
4.2.4 Outputs of the Initiating Process Group
The primary outputs of initiation are documents that authorize the project and capture critical baseline
information:
The Project Charter
The Project Charter is the single most important document produced during initiation. It formally authorizes the
project and grants the project manager the authority to apply organizational resources. A well-crafted charter
includes:
● Project title and description
● Business need / purpose (the "why")
● High-level project objectives and success criteria
● High-level requirements
● High-level risks
● Project sponsor name and authorization
● Project manager assignment and authority level
● High-level budget and schedule summary
● Approval requirements (what constitutes success)
● Exit criteria (what would cause the project to be cancelled)
📋 Project Charter — Practical Example
Project: Deploy Cloud-Based ERP System
Business Need: Current legacy system cannot support projected 40% growth in transactions.
Objective: Implement SAP S/4HANA across all 5 business units by Q4 2026.
Budget: $2.4 million (±15% contingency reserve)
Sponsor: Chief Financial Officer
PM Authority: Can approve changes up to $50,000 without escalation.
The Assumption Log
Records all assumptions made during initiation (e.g., "the vendor will provide a dedicated support team") and
constraints (e.g., "the project must be completed before the fiscal year-end"). Assumptions that prove incorrect
become risks that must be managed.
The Stakeholder Register
A structured document that identifies all project stakeholders and captures key information about each:
● Name, title, and contact information
● Interest in the project (what they care about)
● Influence level (high/medium/low)
● Engagement level (unaware / resistant / neutral / supportive / leading)
● Communication preferences
Figure 4.3 – Initiating Process Group: Inputs, Tools & Techniques, and Outputs
4.2.5 Stakeholder Identification Process
Identifying stakeholders is one of the most critical — and often underestimated — tasks in initiation. Missing a
key stakeholder can result in significant scope changes or project cancellation later. The process involves:
1. Review the project charter, business case, and relevant contracts to identify those who have a stake.
2. Interview the sponsor and functional managers.
3. Analyze organizational charts and governance structures.
4. Consider external stakeholders: regulators, customers, suppliers, and the public.
5. Use the stakeholder register to document and prioritize them.
4.2.6 Feasibility and Selection Methods
Before formally authorizing a project, organizations evaluate feasibility across multiple dimensions and use
financial methods to select which projects to pursue:
Method / Dimension Description
Net Present Value (NPV) If NPV > 0, the project generates value. Higher NPV =
better investment.
Return on Investment (ROI) Ratio of net benefit to project cost. Higher ROI is
preferred.
Payback Period Time required to recover the initial investment.
Shorter = less risky.
Technical Feasibility Can the technology required be realistically
implemented?
4.3 Planning Process Group
The Planning Process Group encompasses the largest number of processes in PMBOK® — 24 in total. Planning
translates the high-level vision established during initiation into a detailed, actionable Project Management Plan.
This plan becomes the baseline against which project performance is measured.
Key planning activities and documents include:
● Scope Planning: Define detailed requirements and create the Work Breakdown Structure (WBS) — a
hierarchical decomposition of all project work.
● Schedule Planning: Sequence activities, estimate durations, identify the critical path, and build a schedule
baseline (often visualized as a Gantt chart).
● Cost Planning: Estimate costs for each work package and establish a cost baseline (project budget).
● Quality Planning: Define quality standards and the approach to meeting them.
● Resource Planning: Determine what human, material, and equipment resources are needed and when.
● Communications Planning: Define the communication strategy: who, what, when, and how.
● Risk Planning: Identify, analyze, and plan responses for risks.
● Procurement Planning: Determine what will be bought externally and develop procurement documents.
● Stakeholder Engagement Planning: Design strategies to keep stakeholders appropriately engaged
throughout the project.
4.4 Executing Process Group
During execution, the project team carries out the work defined in the Project Management Plan. This is where
the bulk of the project budget is consumed and where deliverables are actually created. The project manager
focuses on:
● Directing and managing project work
● Managing quality — performing quality assurance activities
● Acquiring, developing, and managing the project team
● Managing communications and stakeholder engagement
● Conducting procurements — working with vendors and suppliers
● Implementing approved change requests
4.5 Monitoring and Controlling Process Group
Monitoring and Controlling (M&C) runs concurrently with all other process groups. It involves tracking, reviewing,
and regulating project progress and performance, and managing changes. Key activities include:
● Monitoring project work against the baseline (scope, time, cost)
● Performing Integrated Change Control — evaluating and approving/rejecting changes
● Validating scope — formal acceptance of completed deliverables by the sponsor
● Controlling schedule, costs, quality, resources, and communications
● Monitoring risks and implementing risk responses as needed
● Reporting project performance to stakeholders (e.g., Status Reports, Dashboards)
A critical concept within M&C is Earned Value Management (EVM), which provides objective measurements of
project performance using metrics such as Schedule Performance Index (SPI) and Cost Performance Index (CPI).
An SPI or CPI below 1.0 signals that the project is behind schedule or over budget, respectively.
4.6 Closing Process Group
The Closing Process Group finalizes all activities to formally complete the project or phase. It is often
underemphasized but is critically important for organizational learning and accountability.
● Obtain Final Acceptance: Secure formal sign-off from the sponsor and key stakeholders that all deliverables
have been completed as agreed.
● Transition Deliverables: Hand over completed products, systems, or services to the operations team or
client.
● Release Resources: Release project team members back to their functional departments or to other projects.
● Document Lessons Learned: Capture what went well and what could be improved for future projects. This is
one of the most valuable — and most neglected — closing activities.
● Archive Project Documents: Store all project records for future reference in the organizational process
assets repository.
● Close Contracts: Verify that all vendor/supplier obligations have been fulfilled and formally close
procurement contracts.
5. Project Management Methodologies
A project management methodology is a structured set of processes, rules, tools, and techniques that guide how
a project is planned, executed, and controlled. Different project environments call for different methodologies.
The two most widely adopted approaches are Waterfall and Agile — each with distinct philosophies, strengths,
and limitations.
Figure 5.1 – Waterfall (sequential) vs. Agile (iterative) Approaches
5.1 Waterfall Methodology (Traditional / Predictive)
5.1.1 Overview
The Waterfall methodology, introduced by Winston Royce in the 1970s, follows a strictly sequential, linear
process. Each phase must be fully completed before the next one begins — like water flowing down a waterfall. It
is also referred to as the "Predictive" or "Plan-Driven" approach because the full scope, schedule, and budget are
defined upfront.
5.1.2 The Waterfall Phases
● 1. Requirements: All project requirements are gathered, documented, and signed off before any design or
development work begins. The output is a Requirements Specification document.
● 2. System Design: The technical architecture, database structure, and system interfaces are designed based
on the approved requirements. Output: Design Specification.
● 3. Implementation (Development): Developers build the product according to the design specifications. This
is typically the longest and most resource-intensive phase.
● 4. Testing (Verification): The completed product is rigorously tested against the requirements to identify and
fix defects. Testing only begins after development is complete.
● 5. Deployment: The tested product is released to the production environment or delivered to the client.
● 6. Maintenance: Post-delivery support, bug fixes, and minor enhancements are handled. This phase
continues for the product lifecycle.
5.1.3 When to Use Waterfall
Waterfall is most effective when:
● Requirements are well-understood, stable, and unlikely to change.
● The technology and approach are well-established and low-risk.
● Regulatory or contractual requirements demand extensive documentation.
● The project is short in duration (reducing the risk of requirement changes).
● Examples: construction projects, manufacturing, government infrastructure.
5.1.4 Advantages and Disadvantages of Waterfall
✅ Advantages ❌ Disadvantages
Simple, easy to understand and manage Inflexible to scope changes once started
Clear documentation at each phase Testing occurs late — bugs are expensive to fix
Easy progress tracking against milestones Customer sees product only at the end
Works well for fixed-price contracts High risk for complex, innovative projects
5.2 Agile Methodology (Iterative / Adaptive)
5.2.1 Overview and the Agile Manifesto
Agile emerged in the software industry in the early 2000s as a response to the rigid constraints of Waterfall. In
2001, a group of 17 software practitioners published the Agile Manifesto, articulating a new set of values for
software development that has since expanded to many other domains.
📜 The Four Values of the Agile Manifesto
1. Individuals and interactions OVER processes and tools
2. Working software OVER comprehensive documentation
3. Customer collaboration OVER contract negotiation
4. Responding to change OVER following a plan
"While there is value in the items on the right, we value the items on the left more." — Agile Manifesto (2001)
5.2.2 How Agile Works — The Sprint Cycle
Agile breaks the project into short, fixed-length iterations called "Sprints" (in Scrum, the most popular Agile
framework). Each sprint typically lasts 1–4 weeks and follows a consistent cycle:
● 1. Sprint Planning: The team selects items from the product backlog and commits to delivering them within
the sprint.
● 2. Daily Stand-up: A 15-minute daily meeting where team members share what they did yesterday, what
they'll do today, and any blockers.
● 3. Development & Testing: The team builds, tests, and integrates features continuously throughout the
sprint.
● 4. Sprint Review: The team demonstrates the completed working product increment to stakeholders and
receives feedback.
● 5. Sprint Retrospective: The team reflects on their process and identifies improvements for the next sprint.
5.2.3 Key Agile Roles (Scrum)
● Product Owner: Represents the customer/business. Maintains and prioritizes the product backlog. Defines
"what" to build.
● Scrum Master: Facilitates the Scrum process, removes impediments, and coaches the team. Not a manager
— a servant-leader.
● Development Team: Self-organizing, cross-functional group of professionals (developers, testers, designers)
who build the product increment.
5.2.4 When to Use Agile
Agile is most effective when:
● Requirements are unclear, evolving, or likely to change frequently.
● The customer/end-user needs to be actively involved throughout development.
● Speed to market and early delivery of value are critical.
● The team is co-located or capable of close collaboration.
● The project involves innovative, complex, or technology-driven work.
● Examples: software development, digital transformation, product design.
5.2.5 Advantages and Disadvantages of Agile
✅ Advantages ❌ Disadvantages
Highly adaptable to changing requirements Scope and cost harder to predict upfront
Continuous customer feedback reduces rework Requires high customer involvement
Early delivery of working product increments Less emphasis on documentation
Team empowerment improves quality and morale Difficult to scale to very large projects
5.3 Waterfall vs. Agile — Detailed Comparison
The table below provides a comprehensive side-by-side comparison to help you choose the right approach for a
given project context:
Dimension Waterfall Agile
Approach Sequential, linear Iterative, incremental
Planning All upfront (Big Design Up Front) Rolling wave (sprint by sprint)
Requirements Fixed and fully documented at Evolving, captured in backlog
start
Flexibility Low — changes are costly High — change is embraced
Customer Role Primarily at start and end Continuous, collaborative
Delivery Single delivery at project end Working increments every sprint
Testing After development is complete Integrated into each sprint
Documentation Comprehensive and formal Lightweight, just enough
Team Structure Functional hierarchies Self-organizing, cross-functional
Risk Profile Higher — detected late Lower — detected early each
sprint
Best Suited For Stable, well-defined projects Complex, innovative, fast-changing
5.4 Hybrid Approaches
In practice, many organizations blend elements of both Waterfall and Agile into a Hybrid approach. For example,
a construction company might use Waterfall for the design and regulatory approval phases (which require stable,
documented requirements) but adopt Agile sprints for the interior fit-out and technology integration phases
(where flexibility adds value).
The choice of methodology should always be driven by the project's context — its complexity, the stability of
requirements, the level of innovation involved, and the organizational culture — not by personal preference or
trend-following.
💡 Key Takeaway for Beginners
Neither Waterfall nor Agile is universally superior. A project manager's job is to select and tailor the methodology that
best fits the project's needs and the organization's environment.
As PMI's PMBOK® 7th Edition states: "Project managers should select and tailor their approach based on the context of
the project and the needs of the stakeholders."
6. Summary and Key Takeaways
This lecture note has introduced the foundational concepts of project management. Let us consolidate the key
learning points:
● A project: is a temporary, unique endeavor — distinct from ongoing operations.
● Projects are initiated: in response to strategic opportunities, market demands, regulatory requirements, or
organizational needs.
● Six elements: make a project successful: clear objectives, strong sponsorship, competent PM, engaged
stakeholders, realistic planning, and effective risk management.
● The PMI Framework: organizes project work into five Process Groups: Initiating, Planning, Executing,
Monitoring & Controlling, and Closing.
● Initiation: is the most critical phase — it establishes the project charter, identifies stakeholders, and sets the
strategic foundation.
● Waterfall: suits stable, well-defined projects requiring sequential execution and comprehensive
documentation.
● Agile: suits complex, evolving projects requiring rapid delivery, flexibility, and continuous customer
collaboration.
● Hybrid approaches: combine both methodologies to match the specific context of the project.