By Bob Rhubart-Oracle on Nov 22, 2013
One of the observations that came out of the SOA expert roundtable discussion captured in the latest OTN ArchBeat podcast was that while SOA tools and technologies are mature, some organizations still struggle with SOA because they lack the organizational maturity to overcome the lack of communication, cooperation, and trust between siloed development groups.
You'll find additional insight into those issues in the latest blog post from David Sprott, which includes highlights from a survey in which he asked architects, designers and project managers about service specification practices.
Among the highlights from that survey:
- DIY is the dominant service specification approach
- Documents and spreadsheets still dominate tool usage for service planning, reporting and management
- Dissatisfaction with tool support, "particularly in the context of communicating service specifications between the different roles and groups across the organization."
On that last point, are the tools really to blame? If, as those participating in my podcast pointed out, the "not invented here" syndrome still seems to throw up barriers to service reuse across siloes, isn't that a people, rather than a tool problem?