Software Peter principle
Engineering term for a complex, failing project / From Wikipedia, the free encyclopedia
Dear Wikiwand AI, let's keep it short by simply answering these key questions:
Can you list the top facts and stats about Software Peter principle?
Summarize this article for a 10 year old
SHOW ALL QUESTIONS
The Software Peter principle is used in software engineering to describe a dying project which has become too complex to be understood even by its own developers.
![]() | This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these template messages)
|
It is well known in the industry[citation needed] as a silent killer of projects, but by the time the symptoms arise it is often too late to do anything about it.[citation needed] Good managers can avoid this disaster by establishing clear coding practices where unnecessarily complicated code and design is avoided.
The name is used in the book C++ FAQs (see below), and is derived from the Peter principle ā a theory about incompetence in hierarchical organizations.