Gold plating (software engineering)

Gold plating in software engineering or Project Management (or time management in general) refers to continuing to work on a project or task well past the point where the extra effort is worth the value it adds (if any). After having met the requirements, the developer works on further enhancing the product, thinking the customer would 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 Prince 2. In this case, gold plating refers to the addition of any feature not considered in the original scope plan (PMBoK) or business case (Prince2) at any point of the project since it introduces a new source of risks to the original planning i.e. additional testing, documentation, costs, timelines, etc. However, 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.

See also

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.
  4. ↑ Atwood, Jeff (2008-07-15). "The Ultimate Software Gold Plating". CodingHorror.com.
  5. ↑ Fletcher, John. "Gold Plating". Retrieved 2010-05-03.


This article is issued from Wikipedia - version of the Tuesday, November 11, 2014. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.