I always recommend a "think big, take small steps" methodology. So I concur with the "take one small step at a time" advice. But I find that many organizations forget the "think big" part of the equation.
Anne On 12/18/08, htshozawa <[email protected]> wrote: > Hi, a little bit late but want to put my +1 with take it one step at > a time. That's what I've seen too. Many companies are interested in > doing one project at a time instead of one large enterprise level > project. The trick is to have institute governance one step at a > time. :-) > > H.Ozawa > > --- In [email protected], Michael > Poulin <m3pou...@...> wrote: >> >> This is what I've received today by e-mail from the SearchSOA.com >> >> Gartner's Yefim Natis is sure that "SOA is integration". Are we > getting anywhere with this opinion? >> >> "You can only do it in parts of a domain where you have control." - > sounds to me like you can make some money "in parts" (hey, it is > the financial crisis, dude) and do not even think about approaching > your Business telling them that they might make much more money if > they do it top-down for the real business parts (that cannot be small > by nature). >> >> Thanks to such "experts", "This past summer was a cold one for > SOA". Indeed, a keyboard (especially, wireless) is not the best tool > for nut-cracking; why we need it at all? >> >> What can we do to slow down spreading such Integration SOA madness? >> >> - Michael >> >> >> FROM THE EDITOR >> >> >> Gartner AADI Summit: SOA going into 2009 >> [Jack Vaughan] >> >> >> Several years into the SOA era of application and integration > development, SOA continues on without a full consensus opinion of > what SOA is. >> Yet there were plenty of takes on what SOA is at this year's > Gartner's Application Architecture, Development & Integration Summit > 2008 in Las Vegas, and while the definitions and prognostications on > SOA remained diverse, a picture emerges. >> It does seem one great trait of SOA is that it is an ongoing > process. Its goal is to favorably and repeatedly change development > outcomes based around logically partitioned services. It shares this > goal with predecessor components, objects and elements of CASE > methodologies. But it is different. >> The idea that 'one SOA fits all' may be fading. "SOA is > integration. It is a strategic initiative," said Gartner analyst > Yefim Natis. "You can only do it in parts of a domain where you have > control." >> One SOA at a time >> At last week's Gartner Summit, Natis discussed varieties of SOA, > and pointed to the fact that many companies are instituting SOAs, but > they are doing so without a singular architectural blueprint for all > IT. Some people, according to Natis, are starting to try to federate > their 'domain SOAs' based on agreed-to interoperability protocols and > transports that span the full organization. >> Sometimes, things are best seen in comparison to what they are not. > In this example, the 'anti-SOA' may be seen as the mainframe > application of yore. Said Natis: "The monolithic application is the > other side of SOA." In other words, a SOA is not part of just one app. >> This past summer was a cold one for SOA, with critics tossing > barbs, and denigrating aspects of SOA. Some criticism may be well > placed. The Gartner conference brought to mind a paraphrase of an old > Elvis Costello song: 'What's so funny about shareable, swappable and > modular?' SOA is less a technology than a way to dependably extract > business value from technology. It is a journey, and it involves work. >> Read more about the Gartner Summit. >> >> >> >> Gartner AADI Summit: SOA going into 2009 >> [Jack Vaughan] >> >> >> Several years into the SOA era of application and integration > development, SOA continues on without a full consensus opinion of > what SOA is. >> Yet there were plenty of takes on what SOA is at this year's > Gartner's Application Architecture, Development & Integration Summit > 2008 in Las Vegas, and while the definitions and prognostications on > SOA remained diverse, a picture emerges. >> It does seem one great trait of SOA is that it is an ongoing > process. Its goal is to favorably and repeatedly change development > outcomes based around logically partitioned services. It shares this > goal with predecessor components, objects and elements of CASE > methodologies. But it is different. >> The idea that 'one SOA fits all' may be fading. "SOA is > integration. It is a strategic initiative," said Gartner analyst > Yefim Natis. "You can only do it in parts of a domain where you have > control." >> One SOA at a time >> At last week's Gartner Summit, Natis discussed varieties of SOA, > and pointed to the fact that many companies are instituting SOAs, but > they are doing so without a singular architectural blueprint for all > IT. Some people, according to Natis, are starting to try to federate > their 'domain SOAs' based on agreed-to interoperability protocols and > transports that span the full organization. >> Sometimes, things are best seen in comparison to what they are not. > In this example, the 'anti-SOA' may be seen as the mainframe > application of yore. Said Natis: "The monolithic application is the > other side of SOA." In other words, a SOA is not part of just one app. >> This past summer was a cold one for SOA, with critics tossing > barbs, and denigrating aspects of SOA. Some criticism may be well > placed. The Gartner conference brought to mind a paraphrase of an old > Elvis Costello song: 'What's so funny about shareable, swappable and > modular?' SOA is less a technology than a way to dependably extract > business value from technology. It is a journey, and it involves work. >> Read more about the Gartner Summit. >> > > >
