Ir al contenido

Gold Plating

De Scrum Manager BoK
Esta página es una versión traducida de la página Gold Plating. La traducción está completa al 100 %.
⏱ 2 min  ·  📅 2026
Gold plating is a term used to refer to the practice of adding unnecessary or excessive features to a project or product, beyond what is actually required to meet the established objectives.

Description

It involves adding elements that provide no real value but can increase the costs, time, or complexity of the project without any significant benefit.

This phenomenon may arise from decisions made by the development team, which tries to add "extra value" to the project. However, this "extra value" can have negative effects.

Motivations

They are varied and may be related to psychological, professional, and organizational factors. Some of the most common may be:

  • Seeking recognition: people sometimes believe that by adding features or making unrequested improvements, they will be able to prove their worth within the team or the organization.
  • Perfectionism: some people have a natural inclination toward perfectionism. This can lead them to invest time and resources in details that are not essential to the project's success.
  • Fear of criticism: some people may choose to add more than necessary to the project in an effort to please everyone.
  • Professional insecurity: professionals may feel insecure about the quality of their work or their ability to meet the expectations of the customer or the team. They believe that resorting to Gold Plating will be a way to demonstrate their commitment.
  • Disconnection from the customer or end user: when there is no clear understanding of the needs and priorities of the customer or end user. In these cases, it is common to assume what we believe the customer or end user wants.
  • Internal pressure: the organizational culture may put pressure on employees to "go the extra mile," without being clear about what that means exactly.
  • Lack of guidance and clear goals: this can lead teams to find their own way and make decisions without involving everyone else.

Consequences

The consequences can be harmful to both projects and businesses. Some of them are:

  • Increased costs: every additional feature or unrequested improvement requires time, resources, and effort to implement. The budget may overrun, and more resources than initially planned will have to be allocated.
  • Delays: it can significantly slow down the project's progress. Delivery delays arise, and customer satisfaction and the competitiveness of the product or project in the market may decline.
  • Waste of resources: the time, effort, and resources invested do not add value to the product. This has a negative impact on the organization's operational efficiency and profitability.
  • Compromised customer satisfaction: customers may feel that resources have been spent on elements that are not aligned with their real needs and expectations. As a result, the customer's trust in the organization is damaged.
  • Unnecessary complexity: every additional feature adds complexity to the project, which can make long-term management and maintenance more difficult.

Strategies to avoid it

1. Establish clear requirements

The project requirements must be clearly defined and documented from the outset. These requirements should be specific, measurable, and aligned with the needs of the customer or stakeholders.

2. Open and frequent communication

It is important to maintain constant communication with stakeholders and the customer throughout the entire project lifecycle. For example, through regular meetings with the customer.

3. Establish a clear scope

It is essential to define and document the project scope, specifying what is included and what is not.

4. Requirements prioritization

It can be useful to apply prioritization techniques to rank requirements according to their importance and value to the project.

5. Follow a project management methodology

We can adopt a project management methodology such as Scrum or Kanban. These methodologies focus on delivering value iteratively, which helps avoid Gold Plating.

6. Change control

Another strategy is to put a change control process in place. It should require proper approval and documentation before any changes are made to the project scope.

7. Retrospectives

They are a very valuable tool that can help us detect and work on the motivations behind Gold Plating.

During these meetings, team members can identify and openly discuss motivations such as the pursuit of recognition, perfectionism, fear of criticism, and professional insecurity. Specific improvement goals can be set: fostering collaboration, defining limits to perfection, and improving communication with stakeholders and the customer.

Example

The TechSolutions development team is making progress on the project and meeting the established deadlines. However, one team member, Jaime, suggests adding an extra "custom report generation" feature that would allow users to create highly customized reports based on their project data.

Although this feature was not included in the requirements agreed upon with the client, Jaime argues that it could give the application a competitive advantage and would impress end users.

The problem is that adding this new feature would increase costs, cause delays, and jeopardize customer satisfaction. The customer is not pleased with the delays and additional costs, since this function was not essential to their basic project management needs.

Gold plating and AI

Generative AI tools have lowered the unit cost of adding functionality, which can accelerate gold plating: if generating a new configuration option or an additional report takes minutes instead of hours, the temptation to add it "since it's easy anyway" is greater. The KISS principle and rigorous prioritization of the Product Backlog become more relevant, not less, when the marginal cost of adding features drops.

Common mistake

Confusing gold plating with technical excellence. Technical excellence means building well what has been committed to: clean code, sufficient testing, and adequate documentation. Gold plating means building more than what was committed to. They are different things: the former is part of the Definition of Done; the latter is a deviation from the agreed scope.

Materials

📄 En qué consiste el Gold Plating [What Gold Plating Is, in Spanish]Exercise · Scrum Manager

See also

Want to advance in agility? You can search for course and exam calls, or go at your own pace by becoming a member of the Agile Club. This membership includes exclusive resources, e-learning classrooms, and access to Skill Arena: a space to practice and measure your agile skills at your own pace.