Project management - Project Types and Management Approaches

Introduction to Project Management Approaches and Methods Project management has evolved over the decades to address different types of projects and organizational challenges. Today, organizations choose from several management approaches—each suited to particular project contexts. Some focus on delivering physical infrastructure, others on technology solutions, and still others on capturing business value. Understanding these different approaches and methodologies is essential for selecting the right tool for your project and for recognizing how different frameworks complement one another. Types of Projects Construction Project Management Construction project management specializes in delivering physical infrastructure such as buildings, roads, bridges, and similar tangible assets. These projects are typically long-term, have clear physical deliverables, and require coordination of multiple specialized trades and contractors. The methods used in construction project management emphasize detailed sequencing, resource allocation, and on-site coordination. Information Technology Project Management Information technology (IT) project management manages the delivery of technical systems and services. IT projects progress through distinct phases: planning, design, development, testing, and deployment. These projects often involve less tangible deliverables than construction projects, though they may produce software, cloud infrastructure, databases, or integrated systems. Hard versus Soft Project Management A fundamental distinction exists between hard and soft project management: Hard project management focuses on delivering physical, tangible outputs. Construction projects exemplify this—you can see and touch the final deliverable. Hard project management emphasizes scope, schedule, cost, and the concrete outputs produced. Soft project management deals with non-physical outcomes such as organizational change, knowledge creation, improved processes, or strategic positioning. These outcomes are real and valuable to the organization, but they are not physical objects. Soft project management emphasizes outcomes, stakeholder satisfaction, and capability development. Most real-world projects contain elements of both hard and soft dimensions, though one typically dominates. Management Approaches and Frameworks Benefits Realization Management (BRM) Benefits Realization Management (BRM) represents a shift in how we measure project success. Rather than focusing solely on whether we delivered the planned outputs (the project deliverables themselves), BRM emphasizes whether the project actually achieved its intended benefits (the business value and strategic improvements the organization sought). For example, a construction company might complete a new warehouse facility on time and budget (successful outputs), but if the warehouse is poorly designed and never reaches expected capacity utilization, it has not realized its intended benefits. BRM operates through two key mechanisms: Requirements capture: Good requirements management translates intended business benefits into specific, measurable requirements that the project must satisfy. Rather than writing requirements about activities ("conduct five design reviews"), BRM-oriented requirements specify desired outcomes ("reduce operational costs by 20%"). Benefit monitoring: Throughout the project and afterward, the team monitors whether benefits are being realized. This may involve metrics and key performance indicators that track the actual business value being delivered. BRM also ensures strategic alignment—that project outcomes genuinely support the organization's broader business strategy. This prevents organizations from successfully completing projects that no longer matter strategically. Critical Path Method (CPM) The Critical Path Method (CPM) is a foundational scheduling technique that determines the optimal project schedule. CPM evaluates four key factors: Sequence: The order in which tasks must occur (task A must finish before task B can start) Work effort: How long each task takes Inter-dependencies: Which tasks depend on which other tasks Float time: The amount of schedule flexibility each task has The critical path is the sequence of dependent tasks that has the least flexibility—or no extra time (float). Any delay in a critical path task directly delays the entire project. Non-critical tasks may have float time, meaning they can slip slightly without affecting the overall schedule. The network diagram above illustrates this concept. Paths through the network can be traced from start to finish; the critical path is the longest path, which determines minimum project duration. Critical Chain Project Management (CCPM) While CPM focuses on task sequences and timing, Critical Chain Project Management (CCPM) takes a different approach by applying the Theory of Constraints to project management. The Theory of Constraints identifies that every system has one constraint—the factor that most limits system performance. CCPM's core logic: Identify the constraint (often a specific resource, skill, or critical chain of dependent work) Exploit the constraint (maximize its contribution to the project) Subordinate all other activities to protecting and supporting the constraint CCPM prioritizes tasks on the critical chain—not just the longest sequence, but the sequence that most impacts project completion when resources are constrained. This approach is particularly valuable in resource-constrained environments where multiple projects compete for limited specialists or equipment. Earned Value Management (EVM) Earned Value Management (EVM) extends project monitoring beyond simple schedule and budget tracking. EVM answers three critical questions about project performance: What was planned? (Planned Value) What was actually accomplished? (Earned Value) What did it actually cost? (Actual Cost) By comparing these three dimensions, EVM reveals whether a project is: Ahead or behind schedule Under or over budget Operating efficiently Earned Schedule is an extension of EVM that integrates schedule performance into the traditional EVM framework, giving project managers better insight into schedule status beyond simple percentage-complete metrics. EVM is particularly valuable for large, complex projects where subtle performance degradation might otherwise go unnoticed until too late to correct. Iterative and Incremental Management Iterative and incremental approaches deliver projects in cycles rather than all at once. Each cycle (or iteration) produces a usable increment of the final product, and the team learns and adapts based on experience and feedback. These approaches work especially well for: Large, complex projects that would benefit from staged delivery Multi-company projects where different organizations collaborate Ambiguous projects where requirements are unclear at the start Fast-changing environments where flexibility is essential Common iterative frameworks include: Agile: Emphasizes customer collaboration, responding to change, and delivering working solutions frequently Scrum: A specific Agile framework that organizes work into time-boxed iterations called sprints (typically one to four weeks) Dynamic Systems Development Method (DSDM): Emphasizes timeboxing and stakeholder involvement Extreme Project Management (XPM): Designed for projects in highly uncertain, turbulent environments <extrainfo> The choice among iterative approaches depends on organizational culture, project context, and stakeholder preferences. Some organizations blend multiple approaches. </extrainfo> Lean Project Management Lean Project Management applies principles from lean manufacturing—a methodology developed in automotive manufacturing—to project delivery. The core idea: deliver maximum value to the customer with minimum waste and reduced time. Lean thinking in projects means: Eliminating waste: Non-value-adding activities, rework, waiting time, and unnecessary handoffs Accelerating value delivery: Reducing cycle time from concept to completion Continuous improvement: Systematically identifying and removing obstacles to flow Lean works well when combined with other approaches; for example, many organizations use Lean principles within Agile/Scrum frameworks. Product-Based Planning Traditional activity-based planning defines project success through completed activities ("we finished all planned meetings and reviews"). Product-based planning inverts this logic: define success by the deliverable products required to meet project objectives. Product-based planning begins by asking: "What products (deliverables, outputs, and outcomes) must this project produce to achieve its objectives?" The team then: Identifies all required products Determines dependencies between products Plans activities only as necessary to produce those products This approach naturally eliminates unnecessary busywork and maintains focus on what actually matters. PRINCE2 (Projects in Controlled Environments) is a widely-used methodology that implements product-based planning. PRINCE2 structures projects around product delivery, clear accountability, and stage-based management. <extrainfo> PRINCE2 is particularly popular in government and regulated industries, where structured governance and clear documentation are essential. </extrainfo> Risk Management Proactive Risk Identification Project risk management is fundamentally proactive rather than reactive. Rather than waiting for problems to occur, effective risk management: Identifies potential problems before they materialize Evaluates their likely consequences and probability Develops mitigation strategies to reduce likelihood or impact Enables predictive decision-making based on understood risks This proactive orientation allows organizations to make informed choices about which risks to accept, which to mitigate, and how to allocate contingency resources. Risk management encompasses multiple categories: technical risks (will the solution work?), schedule risks (will we complete on time?), cost risks (will we stay within budget?), organizational risks, and external risks. Enterprise Risk Management System While individual projects manage their own risks, a comprehensive enterprise risk management system supports risk management across the entire organization. Such systems: Create a common language and framework for identifying and assessing risks Enable visibility into risks across multiple projects Identify interdependencies and cascading risks Support resource allocation decisions across the portfolio Build organizational learning about risk patterns Organizations using enterprise risk management can recognize risks that transcend individual projects and make portfolio-level decisions about acceptable risk exposure. Project Management Software Functions of Project Management Software Project management software automates and supports the core functions of project management: Planning: Defining scope, creating schedules, estimating durations and resources Organizing: Structuring work, assigning responsibilities, establishing workflows Resource management: Managing resource pools, allocating people and equipment, tracking utilization Estimation: Developing resource estimates based on historical data or parameters Plan execution: Implementing plans, tracking progress, capturing actuals While software is a valuable tool, it is not a substitute for sound project management thinking. Software amplifies the effectiveness of good project management practices but cannot compensate for poor fundamentals. Project managers must understand the underlying concepts and use software as an enabler rather than relying on it as a solution in itself.