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:

Know it well enough for the exam? Questions on Customer/End User are scenario-based, not definitional.

Practice it free

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.

Power Interest Grid (Power/Influence Grid)

The power interest grid is a 2x2 stakeholder mapping tool that plots each stakeholder by power (ability to affect the project) and interest (concern about its outcome) to decide how to engage them: manage closely, keep satisfied, keep informed, or monitor.

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 plots the work remaining (usually in story points) against time in a sprint or release, alongside an ideal line to zero, so the team can see each day whether it is on track to finish.

Burn-Up Chart

A burn-up chart plots completed work rising over time against a separate total-scope line, so progress and scope changes are visible independently; the work is finished when the two lines meet.

Resource Leveling

Resource leveling is a resource optimization technique that adjusts activity start and finish dates so that demand for a resource never exceeds its availability, accepting a longer schedule and a changed critical path if necessary.

Deliverables

A deliverable is any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project, such as a software release, an audit report, or a trained support team.

Critical Path Method (CPM)

The Critical Path Method (CPM) is a schedule network analysis technique that calculates early and late start and finish dates for every activity to find the longest path through the project, the minimum project duration, and the float on every other path.

Part of

Stakeholder Management

Study full domain →

Practice Customer/End User

Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.