 Scott Ambler: Agile Software Development at Scale
Scott is Practice Leader Agile Development with IBM Rational. He is the (co)-author of 19 books on software development topics ranging from very traditional to very agile approaches. In recent years his focus has been on techniques to scale agile software development, in particular how modeling, documentation, and database issues can be addressed agilely. He works with customers around the world to improve their software processes in a manner which reflects their unique situation. He is a senior contributing editor with Dr. Dobb's Journal and a keynote speaker at software conferences internationally.
|
|
Scott Ambler
|
|
I just wanted to round out my discussion about agile approaches to geographically distributed development (GDD) with a few important words of advice:
1. Get some experience. Worry less about enterprise adoption and instead get started with a small project, or better yet a series of increasingly more complex projects. There will be learning experiences as you build a relationship with the offshore service provider. This advice is applicable whether you?re... |
|
|
Scott Ambler
|
|
In my previous blog posting, http://www.ibm.com/developerworks/blogs/page/ambler?entry=strategies_for_distributed_agile_teams , I overviewed several strategies for improving your effectiveness at geographically distributed development (GDD). Those strategies were fairly generic and directly applicable to both traditional and agile development teams. In this posting I focus on strategies which are more agile in nature, although they could also be applied to... |
|
|
Scott Ambler
|
|
A common misunderstanding about agile software development is that it?s only for co-located teams. Things are definitely easier for co-located teams, and as I found with both the Dr. Dobb?s 2007 and 2008 Agile Adoption surveys (www.ambysoft.com/surveys/) co-located agile teams appear to have a higher success rate than distributed teams, Having said that, many organizations are in fact succeeding at distributed agile development.
I?d like to share... |
|
|
Scott Ambler
|
|
The explicit phases of the Unified Process -- Inception, Elaboration, Construction, and Transition -- and their milestones are important strategies for scaling agile software development to meet the real-world needs of modern organizations. Yes, I realize that this is heresy for hard-core agilists who can expound upon the evils of serial development, yet these very same people also take a phased approach to development although are loathe to admit it. The... |
|
|
Scott Ambler
|
|
A common question that I keep running into with customers is whether you can take an agile approach to service oriented architecture (SOA). The quick answer is yes, because Agile is orthogonal to the implementation technologies used. You can take an agile approach developing COBOL applications running on mainframes, fat-client Java applications, multi-tier J2EE applications, and yes, even services. Granted, it's easier to do with some technologies than... |
|
|
|
