Weekly Edition
Return to the Press page
| |||||||||||||
What Corporate Projects Should Learn from Open Source (O'ReillyNet)
O'ReillyNet looks
into project management. "[It] is rare to find a corporate
environment where the project team has anything approaching the level of
planning, documentation, or review found in successful open source
projects. For some reason, as soon as a budget and a deadline are involved,
all of the lessons we've learned over the years and applied successfully to
open source projects seem to fly out the window."
(Log in to post comments)
What Corporate Projects Should Learn from Open Source (O'ReillyNet) Posted Feb 28, 2006 19:32 UTC (Tue) by avik (guest, #704) [Link] It's rare to find these qualities in successful open source projects too.
What Corporate Projects Should Learn from Open Source (O'ReillyNet) Posted Mar 5, 2006 9:29 UTC (Sun) by pimlott (guest, #1535) [Link] This is a nice article, and reminds me of a piece I started (and never finished) back when I was in the corporate development world, which looked at the same phenomenon from the other side: Instead of showing the corporate world what they could learn from free software, I wanted to show the free software world how bafflingly poor corporate practices are. This was not long after "The Cathedral and the Bazarre", and (in addition to venting my frustration at work) I wanted to offer another explanation to the mystery of why free software tends to be better than proprietary: not because of any inherent advantage in the development process, but because corporate development houses tie their own legs together. It opened:Many free software developers assume that corporate development will be like free software development, only better, due to more resources, structure and teamwork.At least, that's what I expected until I got there and was quickly disillusioned.
|
|||||||||||||