|
|||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||
ABSTRACT
Innovations in software engineering organizations frequently emerge from risky behavior. Most often, these risks are taken by only a small percentage of the software engineering staff - radical engineers (REs). They go against the status quo, experiment with new methods or technologies, and have the burden of bringing the innovations into the mainstream of the organization. Most organizations however, do a poor job of adequately and effectively managing radical engineers (REs). They can be found at either end of the order-chaos continuum. Successful software organizations are those that are able to balance between the extremes and manage REs effectively. In this paper, we discuss lessons learnt in managing REs from software organizations. REFERENCES
Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.
INDEX TERMS
Primary Classification:
Additional Classification:
General Terms:
Keywords:
|
|||||||||||||||||||||||||||||||||||||||||||