This handbook introduces the core concepts of project management, from defining a project and its life cycles to understanding organizational structures and governance. It is designed for project managers, team leads, and students seeking a structured overview of the discipline.
This document is a project management handbook that introduces foundational concepts for practitioners and students. It defines a project as a temporary, unique endeavor and explains the traditional four-phase and comprehensive five-phase life cycles, from initiation to closing.
The handbook compares organizational structures such as functional hierarchies, matrix structures, and the Project Management Office (PMO). It also covers corporate governance, organizational culture, and the roles of project managers, program managers, and change agents, including techniques like influencing without authority and Conger's four steps of persuasion.
A detailed comparison between Waterfall and Agile frameworks is presented, analyzing philosophical approach, scope management, scheduling, cost control, quality, communication, and stakeholder dynamics. The section highlights how Waterfall suits stable projects while Agile adapts to VUCA environments.
The planning section explains estimation techniques like three-point estimating with PERT and triangular distributions, relative sizing with story points, and the use of Work Breakdown Structures (WBS). It also covers task dependencies, Critical Path Method (CPM), float, and buffers for schedule management.
Risk management is addressed through probability and impact matrices, root cause analysis tools like fishbone diagrams, and the ROAM technique. Quality assurance versus quality control is distinguished, and earned value management formulas for cost and schedule variance are provided.
The handbook concludes with agile practices, including the Agile Manifesto values, core roles like Product Owner and Development Team, and ceremonies such as Daily Scrum and Sprint Review. It also explains artifacts like the Product Backlog and the difference between a product increment and a minimum viable product.