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

Phenomenon

For example: after having met the requirements, the project manager or the developer works on further enhancing the product, thinking the customer will be delighted to see additional or more polished features, rather than what was asked for or expected. The customer might be disappointed in the results, and the extra effort by the developer might be futile. [1] [2] [3] [4] [5]

Gold plating is also 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 outcomes of gold plating can ultimately lead to negative realities for a project manager or for 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 leading 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."

A project plan, according to the Project Management Body of Knowledge (PMBOK), is: "...a formal, approved document used to guide both project execution and project control. The primary uses of the project plan are to document planning assumptions and decisions, facilitate communication among project stakeholders, and document approved scope, cost, and schedule baselines. A project plan may be sumarized or detailed."

<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.

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">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">Requirements analysis</span> Engineering process

In systems engineering and software engineering, requirements analysis focuses on the tasks that determine the needs or conditions to meet the new or altered product or project, taking account of the possibly conflicting requirements of the various stakeholders, analyzing, documenting, validating, and managing software or system requirements.

Agile software development is the mindset for developing software that derives from values agreed upon by The Agile Alliance, a group of 17 software practitioners in 2001. As documented in their Manifesto for Agile Software Development the practitioners value:

<span class="mw-page-title-main">Dynamic systems development method</span> Agile project delivery framework

Dynamic systems development method (DSDM) is an agile project delivery framework, initially used as a software development method. First released in 1994, DSDM originally sought to provide some discipline to the rapid application development (RAD) method. In later versions the DSDM Agile Project Framework was revised and became a generic approach to project management and solution delivery rather than being focused specifically on software development and code creation and could be used for non-IT projects. The DSDM Agile Project Framework covers a wide range of activities across the whole project lifecycle and includes strong foundations and governance, which set it apart from some other Agile methods. The DSDM Agile Project Framework is an iterative and incremental approach that embraces principles of Agile development, including continuous user/customer involvement.

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.

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 project documentation (PID) is one of the most significant artifacts in project management, which provides the foundation for the business project.

Managing Stage Boundaries is one of seven processes that make up PRINCE2, a systematic approach to project management developed by the UK's Office of Government Commerce and used widely in UK government and industry. The fundamental principle of Managing Stage Boundaries (SB) is to ensure that, at the end of each stage, the project stays focused on delivering business benefit.

Coding best practices or programming best practices are a set of informal, sometimes personal, rules that many software developers, in computer programming follow to improve software quality. Many computer programs require being robust and reliable for long periods of time, so any rules need to facilitate both initial development and subsequent maintenance of source code by people other than the original authors.

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.

<span class="mw-page-title-main">Project management triangle</span> Model of the constraints of project management

The project management triangle is a model of the constraints of project management. While its origins are unclear, it has been used since at least the 1950s. It contends that:

  1. The quality of work is constrained by the project's budget, deadlines and scope (features).
  2. The project manager can trade between constraints.
  3. Changes in one constraint necessitate changes in others to compensate or quality will suffer.

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)