Project management - History and Standards

The History and Development of Project Management Introduction Project management as a formal discipline emerged in the mid-20th century, driven by the need to manage increasingly complex industrial and governmental projects. The field developed through the work of pioneering practitioners and scholars who created systematic approaches to planning, scheduling, and controlling project work. Understanding this history provides context for the frameworks and standards used in modern project management. The Foundational Figure: Henry Gantt The story of modern project management begins with Henry L. Gantt, an industrial engineer and management consultant working in the early 1900s. Gantt is often called the "father of planning and control techniques" because he developed one of the most important visualization tools in project management: the Gantt chart. A Gantt chart is a horizontal bar chart that displays project tasks along a timeline. Each task is represented as a bar, with the length of the bar showing the duration of that task, and the position of the bar on the horizontal axis showing when the task occurs. Gantt charts allowed project managers to see at a glance which activities were happening in parallel, how long each activity should take, and the overall project timeline. The Gantt chart was revolutionary because it made project schedules visible and easy to understand. Before this, project planning was often done informally or in dense tables that were difficult to interpret. Gantt's innovation established the principle that project management requires clear visualization of work over time. Early Scheduling Models: CPM and PERT By the 1950s, growing complexity in large-scale projects—particularly in defense, aerospace, and industrial manufacturing—drove the need for more sophisticated scheduling methods. Two major techniques emerged during this period, each suited to different types of projects. The Critical Path Method (CPM) The Critical Path Method (CPM) was developed in the late 1950s by DuPont and Remington Rand for their manufacturing and construction projects. CPM is designed for projects where activity durations are known and predictable (what we call deterministic times). The key insight of CPM is identifying the critical path: the sequence of activities that determines the shortest possible project duration. Activities on the critical path have no slack time—any delay in these activities delays the entire project. Activities not on the critical path have some flexibility in when they can be scheduled. CPM allows managers to focus their attention where it matters most: keeping the critical path on schedule. This focus enables efficient resource allocation and risk management. The Program Evaluation and Review Technique (PERT) Around the same time, the U.S. Navy and Lockheed developed the Program Evaluation and Review Technique (PERT) for managing the Polaris submarine missile program. PERT was designed for projects where activity durations are uncertain (what we call stochastic times). Unlike CPM, which assumes a single known duration for each activity, PERT uses three time estimates for each activity: Optimistic time (best-case scenario) Most likely time (what you expect to happen) Pessimistic time (worst-case scenario) These three estimates are combined using a weighted average formula to calculate an expected duration that accounts for uncertainty. PERT is particularly useful for research projects, new product development, and other work where outcomes are less predictable. The difference between CPM and PERT reflects an important principle in project management: different types of projects require different planning approaches depending on how well we can predict activity durations. Modern Professional Standards and Frameworks The Project Management Institute and PMBOK Guide As project management matured as a discipline, the need for standardized practices became clear. The Project Management Institute (PMI) was founded in 1969 to establish professional standards and best practices. In 1996, PMI published the first edition of the Project Management Body of Knowledge Guide (PMBOK Guide). The PMBOK Guide serves as an authoritative reference document that defines the standard terminology, processes, and practices recognized across the project management profession. It organizes project management knowledge into different process groups and knowledge areas, providing a framework that practitioners can use regardless of their industry or project type. The PMBOK Guide identifies five major process groups that occur throughout a project: Initiating: Starting the project and defining its objectives Planning: Developing the project management plan and detailed schedules Executing: Performing the actual project work Monitoring & Controlling: Tracking progress and managing changes Closing: Finalizing the project and capturing lessons learned International and Alternative Project Management Standards <extrainfo> While the PMBOK Guide is widely used, particularly in the United States, other countries and organizations have developed alternative frameworks: PRINCE2 PRINCE2 (Projects IN Controlled Environments) is a process-driven project management method developed by AXELOS and widely used in the United Kingdom and Europe. PRINCE2 emphasizes clear governance structures, defined roles and responsibilities, and structured decision-making throughout the project lifecycle. It is particularly popular in government and public sector projects. PM2 PM2 is the project management methodology developed by the European Commission for managing its projects. It provides a flexible framework adapted to the specific needs of European institutions and international organizations. The V-Model The V-Model is a systems development methodology that emphasizes the relationship between development phases and testing phases. Each development phase on the left side of the "V" has a corresponding verification or validation phase on the right side, ensuring that requirements are tested as they are implemented. This approach is particularly valued in regulated industries like aerospace, automotive, and healthcare where product safety and quality assurance are critical. </extrainfo>