|
| This Article | ||
| | ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
 Digg  Furl  Spurl  Blink  Simpy  Google  Del.icio.us  Y!MyWeb | ||
| Search | ||
| ||
| ASCII Text | x | ||
| Warren Harrison, "Learning Organizations and the Software Developer," IEEE Software, vol. 21, no. 2, pp. 5-7, March/April, 2004. | |||
| BibTex | x | ||
| @article{ 10.1109/MS.2004.1270753, author = {Warren Harrison}, title = {Learning Organizations and the Software Developer}, journal ={IEEE Software}, volume = {21}, number = {2}, issn = {0740-7459}, year = {2004}, pages = {5-7}, doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2004.1270753}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Software TI - Learning Organizations and the Software Developer IS - 2 SN - 0740-7459 SP5 EP7 EPD - 5-7 A1 - Warren Harrison, PY - 2004 KW - learning organization; organizational behavior VL - 21 JA - IEEE Software ER - | |||
Most software development organizations strive to become learning organizations, but far too few are successful. Why is this so rare? With some reflection, it?s easy to identify a three-step process any learning organization must master. First, the organization learns something; second, it manages this knowledge; and finally, organizational behavior is somehow changed by virtue of this new knowledge.
Index Terms:
learning organization; organizational behavior
Citation:
Warren Harrison, "Learning Organizations and the Software Developer," IEEE Software, vol. 21, no. 2, pp. 5-7, March-April 2004, doi:10.1109/MS.2004.1270753
Usage of this product signifies your acceptance of the Terms of Use.