International SOA Symposium, World Trade Center, Rotterdam. (www.soasymposium.com)
On October 22 and 23, 2009 the second international SOA Symposium will take place at the World Trade Center in Rotterdam, the Netherlands. Just coming out of a highly successful agile SAP service oriented project (likely the first in it’s type in the Netherlands or even a wider area), Twan van den broek (of Ciber) and I thought it would be a good idea to share our experiences at the SOA Symposium. And so did the organisation.
Twan and I wil do an inspiring talk on agile SOA projects on the first day; next we will both feature a panel discussion, and on the 23rd I will do a talk on how to model services using smart use cases, which works really fine!
Check out the conference description for this panel discussion.
Agile Development and Service-Orientation: Can They be Successfully Combined?
Agile development and SOA methodologies both speak to tighter collaboration of business to IT, but the mechanisms each approach is based on is dramatically different and in some cases clearly conflicting. How then can these two methodologies be successfully combined?
The panel will voice opinions regarding the compatibility and disparity of these two methodologies.
Panelists (in alphabetical order):
Read more: Sander at SOA Symposium 2009.
The key that ties these two approaches together is simplicity. If simplicity is embraced as a fundamental architectural concept, then SOAs and Agile Development can complement each other nicely and the combined effort can invigorate the business. However, this will only happen if the discipline of simplicity is taken as seriously as the disciplines of SOA and Agile Development.
Roger, I couldn’t agree with you more! Simplicity is key. Funny thing though, simplicity. Much harder to achieve than complexity.
By the way, simplicity is not only key to service orientation. The same goes for model driven development. Just wrote a white paper on pragmatic model driven development (but structured) that ends with Einstein’s words: make everything as simple as possible, but not simpler. I’ve seen highly sophisticated model driven development projects fail miserably, and on the other hand I’ve seen oversimplified model driven development project that also fail.
P.S. The white paper I mentioned can be downloaded following this link: http://www.capgemini.com/resources/thought_leadership/pragmatic_model_driven_development_using_smart_use_cases_and_domaindriven_design/.
Nice white paper :), curious about the sessions and the expert panel.