Developer Driven Development: Difference between revisions
m Remove Afc Messages and templates |
m automatic correction by IA |
||
| Line 3: | Line 3: | ||
---- | ---- | ||
'''Developer-driven development''', or missing-requirements-driven development is an [[anti-pattern]] where the requirements are determined by what the developer thinks the user requires or would appreciate, or what the developer feels like doing on that particular day. | '''Developer-driven development''', or missing-requirements-driven development, is an [[anti-pattern]] where the requirements are determined by what the developer thinks the user requires or would appreciate, or what the developer feels like doing on that particular day. | ||
The introduction of [[Agile]] development methodologies has done little to suppress the practice of | The introduction of [[Agile]] development methodologies has done little to suppress the practice of developer-driven development. | ||
== References == | == References == | ||
Latest revision as of 19:58, 28 March 2025
Developer-driven development, or missing-requirements-driven development, is an anti-pattern where the requirements are determined by what the developer thinks the user requires or would appreciate, or what the developer feels like doing on that particular day.
The introduction of Agile development methodologies has done little to suppress the practice of developer-driven development.
References
| Stub icon | This software-engineering-related article is a stub. You can help EverybodyWiki by expanding it. |
This article "Developer Driven Development" is from Wikipedia. The list of its authors can be seen in its historical and/or the page Edithistory:Developer Driven Development. Articles copied from Draft Namespace on Wikipedia could be seen on the Draft Namespace of Wikipedia and not main one.
