January 7, 2008

...Learn TDD with Codemanship

SOA Doesn't Work In A Disjointed Enterprise

What with all the to-ing and fro-ing and huffing and puffing and screaming and shouting (and biting and gouging) that goes on in most business IT organisations, it can be all-too-easy to forget that we are ultimately all working on different parts of the same system.

By arbitrarily breaking software into chunks - projects, applications, components, services - and then organising ourselves around those chunks, we can end up losing sight of the bigger picture. And that can lead to situations where the left hand doesn't know what the right hand is doing. Which can, in turn, lead to duplication, disarray and conflicting goals.

This can often be a symptom of a disjointed enterprise, where the silo mentality prevails from department to department and business function to business function. It's no wonder, in those situations, that the team building the order processing web application fails to collaborate and co-operate with the team working on the stock management system, if the business people working in order processing and stock control don't speak much, either.

And the last thing that any IT or business manager should be contemplating when they have a disjointed enterprise is any attempt at service-oriented architecture. If you cannot remove the duplication from your business, then you have little or no hope of removing it from your business IT systems.
Posted 12 years, 10 months ago on January 7, 2008