Gold plating (project management)

Last updated

In time management, gold plating is the phenomenon of working on a project or task past the point of diminishing returns.

Contents

For example, after having met a project's requirements, the manager or the developer works on further enhancing the product, thinking that the customer will be delighted to see additional or more polished features, beyond that which what was asked for or expected. If the customer is disappointed in the results, the extra effort put into it might be futile. [1] [2] [3] [4] [5]

Gold plating is considered a bad project management practice for different project management best practices and methodologies such as Project Management Body of Knowledge (PMBOK) and PRINCE2. In this case, 'gold plating' means the addition of any feature not considered in the original scope plan (PMBOK) or product description (PRINCE2) at any point of the project. This is because it introduces a new source of risks to the original planning such as additional testing, documentation, costs, or timelines. However, avoiding gold plating does not prevent new features from being added to the project; they can be added at any time as long as they follow the official change procedure and the impact of the change in all the areas of the project is taken into consideration.

Effects of gold plating

Even the best results of gold plating can lead to negative consequences for a project manager or the project as a whole. In a best-case scenario, the customer accepts the project deliverable with the out-of-scope work, and customer expectations on future projects may forever be elevated to unrealistic levels. In a worst-case scenario, the customer might reject the project deliverable entirely and nullify the contract. [6]

See also

Related Research Articles

Project management is the process of supervising the work of a team to achieve all project goals within the given constraints. This information is usually described in project documentation, created at the beginning of the development process. The primary constraints are scope, time and budget. The secondary challenge is to optimize the allocation of necessary inputs and apply them to meet pre-defined objectives.

<span class="mw-page-title-main">Work breakdown structure</span> A deliverable-orientated breakdown of a project into smaller components.

A work-breakdown structure (WBS) in project management and systems engineering is a deliverable-oriented breakdown of a project into smaller components. A work breakdown structure is a key project management element that organizes the team's work into manageable sections. The Project Management Body of Knowledge defines the work-breakdown structure as a "hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables."

<span class="mw-page-title-main">Project Management Body of Knowledge</span> Body of knowledge for project management

The Project Management Body of Knowledge (PMBOK) is a set of standard terminology and guidelines for project management. The body of knowledge evolves over time and is presented in A Guide to the Project Management Body of Knowledge, a book whose seventh edition was released in 2021. This document results from work overseen by the Project Management Institute (PMI), which offers the CAPM and PMP certifications.

Project management software are computer programs that help plan, organize, and manage resources.

A software company is an organisation — owned either by the state or private — established for profit whose primary products are various forms of software, software technology, distribution, and software product development. They make up the software industry.

<span class="mw-page-title-main">Software release life cycle</span> Stages in creation of computer software

The software release life cycle is the process of developing, testing, and distributing a software product. It typically consists of several stages, such as pre-alpha, alpha, beta, and release candidate, before the final version, or "gold", is released to the public.

<span class="mw-page-title-main">PRINCE2</span> Project management method

PRINCE2 is a structured project management method and practitioner certification programme. PRINCE2 emphasises dividing projects into manageable and controllable stages.

<span class="mw-page-title-main">V-model</span> Graphic of a systems development lifecycle

The V-model is a graphical representation of a systems development lifecycle. It is used to produce rigorous development lifecycle models and project management models. The V-model falls into three broad categories, the German V-Modell, a general testing model, and the US government standard.

Enterprise Project Management, in broad terms, is the field of organizational development that supports organizations in managing integrally and adapting themselves to the changes of a transformation. Enterprise Project Management is a way of thinking, communicating and working, supported by an information system, that organizes enterprise's resources in a direct relationship to the leadership's vision and the mission, strategy, goals and objectives that move the organization forward. Simply put, EPM provides a 360 degree view of the organization's collective efforts.

A business case captures the reasoning for initiating a project or task. Many projects, but not all, are initiated by using a business case. It is often presented in a well-structured written document, but may also come in the form of a short verbal agreement or presentation. The logic of the business case is that, whenever resources such as money or effort are consumed, they should be in support of a specific business need. An example could be that a software upgrade might improve system performance, but the "business case" is that better performance would improve customer satisfaction, require less task processing time, or reduce system maintenance costs. A compelling business case adequately captures both the quantifiable and non-quantifiable characteristics of a proposed project. According to the Project Management Institute, a business case is a "value proposition for a proposed project that may include financial and nonfinancial benefit."

In agile principles, timeboxing allocates a maximum unit of time to an activity, called a timebox, within which a planned activity takes place. It is used by agile principles-based project management approaches and for personal time management.

Project Management Professional (PMP) is an internationally recognized professional designation offered by the Project Management Institute (PMI). As of 31 July 2020, there are 1,036,368 active PMP-certified individuals and 314 chartered chapters across 214 countries and territories worldwide.

The incremental build model is a method of software development where the product is designed, implemented, and tested incrementally until the product is finished. It involves both development and maintenance. The product is defined as finished when it satisfies all of its requirements. This model combines the elements of the waterfall model with the iterative philosophy of prototyping. According to the Project Management Institute, an incremental approach is an "adaptive development approach in which the deliverable is produced successively, adding functionality until the deliverable contains the necessary and sufficient capability to be considered complete."

The project documentation (PID) is one of the most significant artifacts in project management, which provides the foundation for the business project.

Product-based planning is a fundamental part of the PRINCE2 approach to project management, and is a method of identifying all of the products that make up or contribute to delivering the objectives of the project, and the associated work required to deliver them. The documents which define the Project itself are also considered Products.

Terms of reference (TOR) define the purpose and structures of a project, committee, meeting, negotiation, or any similar collection of people who have agreed to work together to accomplish a shared goal.

Software Quality Management (SQM) is a management process that aims to develop and manage the quality of software in such a way so as to best ensure that the product meets the quality standards expected by the customer while also meeting any necessary regulatory and developer requirements, if any. Software quality managers require software to be tested before it is released to the market, and they do this using a cyclical process-based quality assessment in order to reveal and fix bugs before release. Their job is not only to ensure their software is in good shape for the consumer but also to encourage a culture of quality throughout the enterprise.

A glossary of terms relating to project management and consulting.

Lean project management is the application of lean concepts such as lean construction, lean manufacturing and lean thinking to project management.

The following outline is provided as an overview of and topical guide to project management:

References

  1. McConnell, Steve (1996-07-02). Rapid Development . Microsoft Press. ISBN   978-1-55615-900-8.
  2. McConnell, Steve. "Classic Mistakes Enumerated". stevemcconnell.com. Retrieved 2010-05-03.
  3. Atwood, Jeff (2004-12-07). "Gold Plating". CodingHorror.com. Archived from the original on 2013-12-22. Retrieved 2010-05-04.
  4. Atwood, Jeff (2008-07-15). "The Ultimate Software Gold Plating". CodingHorror.com. Archived from the original on 2013-10-03. Retrieved 2010-05-04.
  5. Fletcher, John. "Gold Plating". Archived from the original on 2011-07-18. Retrieved 2010-05-03.
  6. Burke, Simon, PMP (16 August 2022). "Gold Plating in Project Management". All Things Project Management. Retrieved 2022-10-14.{{cite web}}: CS1 maint: multiple names: authors list (link)