Links for
Organizational Learning and
Software Development
Part of Software Development as Organizational Learning delt with the failure of traditional software development methodologies to adequately describe or improve the development process. Alistair Cockburn adopted a similar theme in his PhD dissertation People and Methodologies in Software Development.
Authors and websites cited
-
Jim Coplien and Neil Harrison - site for Organizational Patterns, their book Organizational Patterns of Agile Software Development was published in mid-2004.
-
Ric Holt - "Software Architecture as a Shared Mental Model" (was at "Software Architecture as a Shared Mental Model")
-
Lorne Olfman - co-author of Organizational Learning through the Process of Enhancing Information Systems
- John Seely-Brown
General stuff
-
PPIG - Psychology of Programming Interest Group - more programming focused but interesting still
-
GBN - Global Business Network - perhaps the home of scenario planning, certainly the home of Peter Schwartz, author of The Art of the Long View. And if your stuck for a book check out their book club and past recommendation.
-
The Agile Manifesto - Kent Beck, etc.
-
Organizational learning and communities-of-practice by John Seely Brown and Paul Duguid - very good article
-
Society for organizational learning "SoL" and the UK chapter
- IEE Software ran an editorial entitled Learning Organizations and the Software Developer, I'm not sure of the date of this but I think it was sometime in 2004.
Other
During my investigation into this topic I became aware that I was not the first to link Software Development and Organizational Learning. However in June 2004 there was actually a conference with workshops on the subject of Learning Software Organizations contained within the Software Engineering and Knowledge Management conference.
In addition now know there is a journal, International Journal of Software Engineering and Knowledge Engineering (IJSEKE), on the same subject. Obviously I wish I had know this earlier.
Part of the problem with this topic is that "knowledge engineering" and "knowledge management" are frequently seen as something that you do with software, i.e. knowledge engineering helps you create software to create Pharmaceuticals. The important difference with my interest is that I am primarily concerned about the role of knowledge and learning within the development process, not as a result of it.