InfoQ

News

Benefits and Challenges of Open Source for Agile Teams

Posted by Deborah Hartmann Preuss on May 20, 2006

Community
Agile
Topics
Open Source
Tags
Complementary Practices
Combining open source resources with a team's Agile best practices can quickly yield some truly amazing results .Jeff Hodson recently wrote: to sustain these successes, teams must apply an architectural-centric approach in order to realize longevity, flexibility and independence in the application. His article Supercharge Your Application Development Open Source Strategy with an Architecture-centric Approach appeared in AgileJournal earlier this month.

Leveraging open source technologies has had a significant positive impact on both the development and runtime environments of software applications. Teams using this advantage find they are better able to deliver applications with expected functionality within timeframes acceptable to interested stakeholders. When given the option to choose between open source widget v1.0 or its commercial v1.0 equivalent, early released versions of open source software tend to be better tested and market-proven than their commercial counterparts.

But, of course, there are trade-offs. Hodson's article addresses developers' concerns about the challenges posed by open source software, including:
  • Community-based support structure is different from the more familiar commercialized software environments.
  • Sporadic release cycles
  • Contribution management: the luxury of the having access to open source code can be a double-edged sword and assumes a certain amount of responsibility and accountability.
  • Fluid project roadmaps: features, enhancements and fixes targeted for a particular release are rarely committed to well beforehand.
  • New Technologies: if it is not well understood internally it can have a detrimental effect on the developer's efforts going forward.
  • Extra-functional requirements: constraints and boundaries placed on an application due to certain open source ingredients.
Hodson has over 20 years of experience in delivering market proven real-time enterprise applications for the financial and telecommunications industries. He writes that "By applying an architecture-centric approach a developer's open source strategy can successfully address the challenges of open source software.".

His article looks at Using Architecture To Address Open Source Challenges, including Architectural Style, Architectural Framework the following Best Practices: Agile-centric development; Component-based development; Single purpose application of open source; Separation of concerns.

Related Sponsor

VersionOne is recognized by Agile practitioners as the leader in Agile project management tools. Companies such as Adobe, BBC, CNN, Dow, HP, IBM, Sony and 3M have turned to VersionOne to help deliver greater value to their customers.

No comments

Watch Thread Reply

Educational Content

Brian Marick on 4 Challenges and 5 Guiding Values of Agile Software Development

Brian Marick takes us through a quick tour of the most important values and challenges to adopting Agile successfully (they aren't the typical challenges and values we hear in the community).

Are You a Software Architect?

The line between development and architecture is tricky. Does it exist at all? Is an ivory tower actually needed? There's a balance in the middle, but how do you move from developer to architect?

Agile – A Way of Life and Pragmatic Use of Authority

The word 'authority' sometimes produces an allergic response in hard-line agilists. Freedom and authority – both are bad if misused and both are good if used in right spirit for a noble cause.

Getting Started with Grails, Second Edition

"Getting Started with Grails" brings you up to speed on this modern web framework. Companies as varied as LinkedIn, Wired, and Taco Bell are all using Grails. Are you ready to get started as well?

Using ITIL V3 as a Foundation for SOA Governance

Those familiar with only ITIL V2 often scoff at the thought that ITIL could serve as a governance framework for SOA. With ITIL V3, the focus of the framework shifted towards service-orientation.

Adrian Colyer on AspectJ, tc Server and dm Server

SpringSource CTO Adrian Colyer discusses AspectJ, SpringSource's dm Server and tc Server products, OSGi and Scrum.

Adam Wiggins on Heroku

Heroku's Adam Wiggins talks about Rails, Background Jobs, Add-Ons, Ruby, and how Heroku manages to work around Ruby's inefficiencies using Erlang and other languages.

SOA as an Architectural Pattern: Best Practices in Software Architecture

For Grady Booch the foundation of a good architecture is patterns, SOA being just one of many patterns. In this Second Life presentation, Booch attempts to bring more clarity on what architecture is.