Re: [service-orientated-architecture] Will SOA Conflict with Agile?
- Agile is in the other end of warterfall - break down
the project into more smaller iterations. For agile
methods change is good. For waterfall, change is bad
to be controlled. They are all RUP vairiations. For
RUP change is inevitable. there is no way to do
things right the first time.
SOA method is different from RUP in kind. SOA method
has the capacity to do things right the first time.
--- jeffrschneider <jeffrschneider@...> wrote:
> If an organization chooses to embrace a service____________________________________________________________________________________
> oriented composition /
> integration method, are they likely to find the
> process conflicting
> with one or more of the principles of the Agile
> see: http://www.agilemanifesto.org/
Low, Low, Low Rates! Check out Yahoo! Messenger's cheap PC-to-Phone call rates
- I did point out in my original post that while the actual service
components of SOA are (IMHO) inherently non-Agile, they support an Agile
approach to building applications that use the service components (what
you're calling Business Agility, if I understand you correctly).
Overall, the improved agility at the business level more than makes up
for the loss of agility at the service level (or at least it should -
otherwise your SOA is just pouring money down a rat hole).
Dennis M. Sosnoski
SOA, Web Services, and XML
Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-296-6194 - Wellington, NZ +64-4-298-6117
Gervas Douglas wrote:
> Nick, you are of course right - I might have known someone would spot
> the intellectually dishonest discrepancy!
> I did however have a purpose. This Group, as you have probably
> observed, has a tendency to get into deeply technical discussions,
> whatever the original theme. This time I thought I would do the
> opposite and divert people's thoughts upwards to the layers that
> concern the ultimate enabling technology - money! In general I think
> proponents of SOA and its design and implementation aspects need to do
> more to keep an eye on the overall business objectives of the systems
> in question.
> --- In firstname.lastname@example.org, "Nick Gall"
> <nick.gall@...> wrote:
>> On 11/1/06, Gervas Douglas <gervas.douglas@...> wrote:
>>> At a purely business level [...], a good SOA
>>> structure should make Business Agility a lot easier.
>> The compatibility between SOA and the vague concept of "Business
>> was not the original question. It was the compatibility of SOA and the
>> specific principles of Agile Methods. Just because both espouse
> agility as a
>> benefit doesn't mean they are compatible.
>> -- Nick
>> Nick Gall
>> Phone: +1.781.608.5871
>> AOL IM: Nicholas Gall
>> Yahoo IM: nick_gall_1117
>> MSN IM: (same as email)
>> Google Talk: (same as email)
>> Email: nick.gall AT-SIGN gmail DOT com
>> Weblog: http://ironick.typepad.com/ironick/
>> Furl: http://www.furl.net/members/ngall
> Yahoo! Groups Links