Skip to content
PMPCAPM

Customer/End User

The customer or end user is the person or organization that will use the project's product, service, or result and whose satisfaction is a primary measure of project success.

Share:

Explanation

Customers and end users are among the most important external stakeholders because the project ultimately exists to deliver value to them. Their requirements define what the project must produce, and their satisfaction determines whether the project is considered successful, regardless of whether it was completed on time and within budget.

It is important to distinguish between the customer (who pays for or commissions the deliverable) and the end user (who actually uses it). They may be the same person or entity, but often they are not. For example, a company executive may commission a new software system (customer) while the employees use it daily (end users). Both perspectives must be captured in requirements.

In agile approaches, customer involvement is continuous. The product owner often represents the customer and prioritizes the backlog based on customer value. Regular demonstrations and feedback loops ensure that the evolving product meets customer expectations. In predictive approaches, customer requirements are gathered upfront and validated through formal acceptance processes.

Key Points

  • Defines project requirements and measures of success
  • Customer (who commissions) and end user (who uses) may differ
  • Satisfaction is a primary success metric regardless of schedule or budget performance
  • Agile emphasizes continuous customer involvement; predictive uses formal acceptance

Exam Tip

If an exam question asks what determines project success, customer satisfaction is always a key factor. A project delivered on time and budget but rejected by the customer is not successful.

Frequently Asked Questions

Related Topics

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

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.

Power/Influence Grid

The power/influence grid is a stakeholder classification model that groups stakeholders based on their level of authority (power) and their active involvement or ability to affect the project (influence).

Stakeholder Analysis

Stakeholder analysis is a technique for systematically gathering and analyzing quantitative and qualitative information to determine whose interests should be taken into account throughout the project.

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.

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.

Part of

Stakeholder Management

Study full domain →

Test your knowledge

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