Comments on: Open Source and Agile – oil and water? http://boldlyopen.com/2009/04/08/open-source-and-agile-oil-and-water/ To boldly muse about Open Source Sat, 20 Aug 2011 22:38:00 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Renzo http://boldlyopen.com/2009/04/08/open-source-and-agile-oil-and-water/comment-page-1/#comment-83681 Renzo Tue, 14 Apr 2009 18:23:34 +0000 http://boldlyopen.com/?p=385#comment-83681 Gianugo, we are in front of two successful development models. Open source development evolved as it is today without a strict use of pairing, co-location and sometimes without a clear definition of customer. This doesn't mean that open source teams aren't communicating, rapidly responding to change or lacking a continuous code reviewing process. Open source development evolved to fill these gaps with specific tools and practices. Similarly Agile solved typical corporate problems using a set of accepted practices. An example. It doesn't make sense to me to try to pair (by the XP book) with a remote developer full time (with what we have today). I'm using a practice evolved for co-location for a distributed context. What it makes sense is to screenshare on demand a few times a day. Is this better than pairing? No. Is this a compromise that works with limitations? Yes. At the same time, it doesn't make sense to have 10 call conferences a day within the same company when we can stay all in the same room. The good thing is that for problems that open source solved like distributed teams, Agile can borrow practices and vice-versa. So Agile and open source development are two different and successful processes with evident areas of overlap. So yes, horse shit with cow manure definitely is a great fertilizer! :) PS: co-location does scale. Just add more desks ;) Gianugo, we are in front of two successful development models. Open source development evolved as it is today without a strict use of pairing, co-location and sometimes without a clear definition of customer. This doesn’t mean that open source teams aren’t communicating, rapidly responding to change or lacking a continuous code reviewing process. Open source development evolved to fill these gaps with specific tools and practices. Similarly Agile solved typical corporate problems using a set of accepted practices.

An example. It doesn’t make sense to me to try to pair (by the XP book) with a remote developer full time (with what we have today). I’m using a practice evolved for co-location for a distributed context. What it makes sense is to screenshare on demand a few times a day. Is this better than pairing? No. Is this a compromise that works with limitations? Yes. At the same time, it doesn’t make sense to have 10 call conferences a day within the same company when we can stay all in the same room.

The good thing is that for problems that open source solved like distributed teams, Agile can borrow practices and vice-versa. So Agile and open source development are two different and successful processes with evident areas of overlap. So yes, horse shit with cow manure definitely is a great fertilizer! :)

PS: co-location does scale. Just add more desks ;)

]]> By: Gianugo http://boldlyopen.com/2009/04/08/open-source-and-agile-oil-and-water/comment-page-1/#comment-83671 Gianugo Fri, 10 Apr 2009 16:45:01 +0000 http://boldlyopen.com/?p=385#comment-83671 Liam, makes for a great fertilizer. Exactly what we need. Liam,

makes for a great fertilizer. Exactly what we need.

]]> By: Liam http://boldlyopen.com/2009/04/08/open-source-and-agile-oil-and-water/comment-page-1/#comment-83668 Liam Fri, 10 Apr 2009 01:07:28 +0000 http://boldlyopen.com/?p=385#comment-83668 Mixing open source with agile is like mixing horse shit with cow manure. Mixing open source with agile is like mixing horse shit with cow manure.

]]> By: Symphonious » Do-ocracy and his French-speaking twin JFDI http://boldlyopen.com/2009/04/08/open-source-and-agile-oil-and-water/comment-page-1/#comment-83666 Symphonious » Do-ocracy and his French-speaking twin JFDI Thu, 09 Apr 2009 11:34:41 +0000 http://boldlyopen.com/?p=385#comment-83666 [...] Gianugo Rabellino, among a bunch of interesting stuff on Agile and Open-source development: do-ocracy and his French-speaking twin JFDI [...] [...] Gianugo Rabellino, among a bunch of interesting stuff on Agile and Open-source development: do-ocracy and his French-speaking twin JFDI [...]

]]> By: Don’t call it Scrum | ][ stefano maffulli http://boldlyopen.com/2009/04/08/open-source-and-agile-oil-and-water/comment-page-1/#comment-83665 Don’t call it Scrum | ][ stefano maffulli Thu, 09 Apr 2009 06:51:23 +0000 http://boldlyopen.com/?p=385#comment-83665 [...] about my research on Free/Libre Open Source software development and Agile/Scrum methods. His latest post contains a sentence that summarizes my key finding so far: At the end of the day, this means that [...] [...] about my research on Free/Libre Open Source software development and Agile/Scrum methods. His latest post contains a sentence that summarizes my key finding so far: At the end of the day, this means that [...]

]]>