Skip to content
PMPCAPM

Kill Points

Kill points are predetermined decision points in a project life cycle where stakeholders have the explicit option to terminate the project based on performance, viability, or strategic relevance.

Share:

Explanation

Kill points are closely related to phase gates but carry a specific emphasis on the termination option. While every phase gate technically includes the possibility of stopping the project, a kill point makes this option explicit and prominent. The purpose is to prevent the sunk-cost fallacy, where organizations continue investing in failing projects simply because they have already spent significant resources.

At a kill point, the review authority evaluates whether the project still makes business sense. Has the market changed? Have costs escalated beyond acceptable limits? Has a competitor launched a similar product? Are the technical challenges insurmountable? If the answer to any of these questions undermines the project's viability, the project should be terminated, and remaining resources should be redirected to higher-value work.

Establishing kill points at the beginning of a project is a best practice in project governance. It normalizes the decision to stop a project, removing the stigma that often prevents organizations from making rational termination decisions.

Key Points

  • Explicit decision points where project termination is a primary option
  • Designed to prevent the sunk-cost fallacy
  • Evaluate continued business viability and strategic relevance
  • Should be defined during project planning as part of governance

Exam Tip

Kill points and phase gates are related but not identical. If the exam question emphasizes the decision to terminate a project, the answer is a kill point. If it emphasizes a general review and go/no-go decision, it is a phase gate.

Frequently Asked Questions

Related Topics

High-yield topics our learners drill most before exam day.

Project Governance

Project governance is the framework of authority, accountability, policies, and decision-making processes that guide a project from initiation through closure, ensuring alignment with organizational strategy and stakeholder expectations.

Burndown Chart

A Burndown Chart is a graphical representation of work remaining versus time in a Sprint or release, showing whether the team is on track to complete the planned work.

Resource Leveling

Resource leveling is a resource optimization technique in which adjustments are made to the project schedule to keep resource usage at or below a defined limit, often resulting in a longer project duration.

Risk Register

The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.

Stakeholder Mapping

Stakeholder mapping is the visual representation of stakeholder relationships, influence, interest, or other attributes using grids, matrices, or diagrams to support analysis and engagement planning.

Relative Estimation

Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.

Cost Performance Index (CPI)

Cost Performance Index (CPI) is an EVM efficiency metric that measures cost performance as the ratio of earned value to actual cost: CPI = EV / AC.

Schedule Performance Index (SPI)

Schedule Performance Index (SPI) is an EVM efficiency metric that measures schedule performance as the ratio of earned value to planned value: SPI = EV / PV.

Earned Value Management (EVM)

Earned Value Management (EVM) is a methodology that integrates scope, schedule, and cost data to assess project performance and progress objectively.

Part of

Organizational Structures & Governance

Study full domain →

Test your knowledge

Practice scenario-based questions on this topic with detailed explanations.