I’ve been digging into service-oriented architecture this week again in an effort to understand a bit better the technical requirements of a SOA implementation. Daunting.
What I’ve found is that when doing a SOA implementation, wrapping an existing application exposes an interface in order to increase access. In addition, refacing an application provides a new interface to not only increase access but also to allow reuse. Deconstructing an application into components (“componentizing”), so that it can be reassembled exposes new services. And that feat, it seems, is the province of enterprise artists, tapping into the collective business and digital imagination of the company.
Reading up in preparation for some interviews with companies using service-oriented architecture, I kept coming across variations on the statement that doing a SOA implementation is more an art than a science. Knowing which services to expose for the maximum value requires judgment and taste, sensibilities rarely afforded much value in the world of IT. The notion that judgment and taste can make a huge difference made more sense after talking yesterday to Fred Falten, the chief architect at Amtrak. Here is Falten on designing for future generations with SOA:
“When you’re building a service, you need to plan ahead. Always think about how the service can be reused. Make the extra investment to not just have the project at hand be the mechanism that says, ‘Here is what the interface definition should be,’ but take the extra time to think about what would the entire company, or at least the next reasonable set of potential users, want.
“That pays dividends in so many ways, in terms of future savings. Don’t build services point to point, where you’re really defeating the purpose of SOA.
“The other thing I would say is granularity of the service. It’s extra work, but if you have existing environment it is all too easy of fall into the trap of taking the existing transactional environment and just exposing each transaction as a service. That makes it so fine grained that it is usually meaningless to other applications and other potential service users. It is exposing things at a level that no one knows what to do with, or if they did, it is a lot of extra hassle for them to figure out how to move all the little transactional pieces together. So, what you want to do, if you have a legacy environment that is highly transactional and has relatively small transactions in it, is take the extra time to think about how an external business unit would want this information to be presented, not the way the original team built it, but how it really means something to be business now.”
Check in with us next week to read details on how Falten dealt with the art and science of using SOA to make the Amtrak environment more fleet of foot, er … track.
Happy belated Halloween! I hope everybody who celebrated had a great time — any creative IT-related Halloween costumes you’d like to tell us about?
Last week on SearchCIO.com, we talked about demonstrating the business value of IT, agile development methodologies, a botched IT outsourcing contract and six ways to fail with your SOA implementation. (Come to think of it, the latter two probably provided you with some pre-Halloween shudders, right?) Check out the full stories linked below.
The Real Business of IT: Free chapter download — This book focuses on how CIOs can demonstrate the value of IT as a strategic partner. And who doesn’t like free?
Agile development methodology not easy but worth the effort, users say — The agile methodology is giving development organizations the “speed they need” to respond to changes in the market and bring more value to the business faster. Here’s how you can do the same!
Botched IT outsourcing contract shows need for governance, SLAs — Virginia’s $2 billion IT outsourcing contract has gone awry, with service interruptions and missed deadlines. Find out what lessons were learned on IT governance and clear SLAs. To share your views, read our post on IT outsourcing contracts without penalties.
Six ways to fail with your SOA implementation — A service-oriented architecture is one way to make application development more agile, a growing business requirement. Here are the top risks for SOA failure — avoid them if you want to do it right!
An end to information overload may be in sight. Call me late to the party (or perhaps naïve!), but I think I’m starting to make social media work for me, and not in the way you might think.
This is what I’m talking about:
Now if only I could find a way to get my LinkedIn updates, Gmail and other sundry faves from across the Web together in a similar fashion, I’d be even more efficient, informed and responsive than I am now. Yes, really using Twitter “right” (for networking, relationship building and so on) requires more than I’m giving it, but for now this approach fits my reality and my needs. I highly recommend it.
You hear a lot of analysts, clients and, of course, vendors touting the benefits of IT outsourcing, especially as the U.S. emerges from this economic recession, which the latest government numbers show is over. In larger organizations, outsourcing can help globalize operations, and proponents inevitably point to the bottom line: It usually saves organizations money.
But if you follow the news, you might have also heard about what must be considered an IT outsourcing failure in the state of Virginia, which is currently embroiled in controversy over its $2 billion IT outsourcing contract with security firm Northrop Grumman. Although there have been a number of missed deadlines and service failures, as we reported this week, breaking the current contract could cost the state hundreds of millions of dollars in taxpayer money – that’s no pocket change! It leaves the state with little choice but to get this deal back on track.
So what went wrong? Perhaps most importantly, there was a poor governance framework in place for overseeing this deal. I wasn’t so surprised to hear that – a lot of organizations struggle before successfully implementing a governance framework for IT outsourcing contracts. But I’m still wondering how the state could not include penalties for any missed deadlines and service levels below those specified in SLAs. Isn’t that the entire basis of a contract — to hammer out those details? It’s mind-boggling.
(And, just so you know I’m not new to such failures: As a community journalist, I covered the construction of a new high school with a budget that’s ballooned to nearly $200 million, almost double the initial estimates. So, trust me, I know government incompetence.)
I’m scheduled to speak to Virginia CIO George Coulter Friday about the corrective action plan proposed by Northrop Grumman and how the state intends to straighten this mess out. Do you have questions regarding IT outsourcing contracts or what went wrong here? I’d love your input.
Also, for those who view Virginia’s mess as a cautionary tale, remember to check out SearchCIO.com, where we have information on IT outsourcing governance, outsourcing trends going into next year, and more.
Good morning! Last week on SearchCIO.com, we focused on how to build innovation and flexibility into IT outsourcing deals, discussed how to select the right BPM tools for success, and shared Gartner’s top 10 strategic technologies for 2010. Check out the stories and podcast linked below and let us know if you have any comments to add.
How to build IT innovation, flexibility into your IT outsourcing deals — Learn how to draw IT innovation from your IT outsourcing vendors and structure your contracts to cover new technology models like cloud and SaaS.
BPM tool selection: Strategies for success — Get the most out of your BPM tools. Learn how to assess your business and technical needs and choose the best vendor and tool to meet your BPM needs.
Gartner’s top 10 strategic technologies for 2010 — Gartner’s list of technologies that bear examination during the next three years show an agile, mobile, secure enterprise that can spot early warning signs and predict trends.
We’ve written a lot lately about what leads to IT project failures and what causes CIOs to get fired. Today I heard about business failure — and its flip side, how companies go from good to great. Yes, this was a talk by Jim Collins, author of the book by that name. And though he’s probably given this talk hundreds of times, his speech during the CIO lunch at Gartner’s Symposium ITxpo was a rousing testimonial to leadership — from what makes a great leader to what distinguishes him or her from a mediocre one, and the causes (almost all self-inflicted) of business failure.
The talk was full of useful insights, especially for all of us looking ahead to 2010 and trying to figure out what to do and what’s going to happen (beyond Gartner’s prediction of 3.3% IT spending growth).
Some of it was even CIO-specific. But more on that in a moment.
First, some things he said about who leaders of “great” organizations are:
And here are some of the things they do:
As for CIOs, Collins talked to a dozen or so of them before his speech, and reported having a lively conversation on what makes a “great” CIO. (His use of great generally refers to consistency of strong results.) The outcome: “They agreed that the truly great CIOs have the leadership capacity that they could be CEOs.” In order words, all of the characteristics above apply.
Are you a “great” CIO or “great” IT leader? Do you want to be? Try Collins’ free diagnostic tool for going from good to great.
p.s. For those interested in the business failure side of his talk, another attendee blogged on Collins’ stages of decline.
Good morning! We had a snowy weekend here in the Boston area, as anybody who watched the Patriots game knows. What better way to warm up than by enjoying a piping-hot cup of coffee or tea and reviewing our latest SearchCIO.com content?
Review these trends in IT disaster recovery planning and outsourcing — IT disaster recovery outsourcing can help enterprises protect data centers more effectively than doing it themselves if catastrophe strikes. Want to show us how much you know about outsourcing DR, or looking to learn more? Review our latest stories and take our quiz?
Multi-sourcing requires IT governance strategy with multiple tiers — An IT governance strategy for multi-sourcing activities requires a multi-tier approach with participation throughout the enterprise. Read how NASA (yes, the NASA that recently bombed the moon to learn more about its surface) learned to govern multi-sourcing.
FAQ: IT and organizational change management — The CIO’s role in organizational and IT change management is to ensure service availability and business support. In our latest FAQ guide, learn more about IT’s role in change management.
Lean thinking in IT: Case studies and advice from practitioners — Lean thinking in IT can improve customer satisfaction and business alignment and cut waste, as TransUnion, Harley-Davidson and Flextronics have found. Read each company’s story here.
Is there a difference between recession-era thinking and recovery-era thinking for IT? That was the question posed last night to members of the Boston chapter of SIM (where the percentage of the 100 people in attendance introducing themselves as “in transition” probably exceeded the unemployment rate). But the biggest challenge that people saw ahead? IT staff retention.
The good news is that budget cutbacks have taught many IT teams how to prioritize, work smarter and find creative solutions to problems they don’t have money to fix. The bad news is that companies that aren’t thinking ahead may see these teams splinter apart through attrition. Those that cut training budgets and don’t restore them in time to invest in their people, for example, won’t be in a good position to retain staff once the economy stabilizes and jumping ship doesn’t seem like such a huge risk.
It wasn’t clear how many organizations could find themselves in that position. Some members mentioned preventative measures under way, such as one company that was hiring at pre-recession salary rates in the hope that new staff would stay beyond a short stint. But for all those still coping with tight resources and few extra benefits, there is probably still time to figure out some IT staff retention measures — by most accounts, the economic recovery will be slow and cautious, and the IT jobs turnaround has just barely begun. (Foote Partners notes that U.S. labor statistics show IT-related job growth of 1,400 jobs since July, with 32,600 IT jobs lost in the first seven months of the year.)
I was on vacation when the news hit that customers of T-Mobile’s cloud-serviced Sidekick phones had likely lost their data due to a failure of the storage service provided by a company recently acquired by Microsoft, ironically named Danger. So, rather than following the story in real time, I found myself reading the historical account of the incident on Thursday. My reading of this was interrupted by another calamitous story, also related to clouds– a small boy whisked up 10,000 feet in the air by a helium balloon and carried in horrifying swoops across the Colorado skies. When the balloon landed gently some two hours later, the boy was not there and feared lost. Both stories, as it turns out, were much less horrifying than originally imagined.
“Balloon boy” was hiding in his family’s attic. The Sidekick data was not lost either; it was hiding somewhere as well. Yesterday Microsoft announced that it had recovered most, if not all, of the customer data.
Despite the good news, we’re seeing evidence now of storm clouds when it comes to cloud storage. The Sidekick data failure was attributed to a storage area network (SAN) upgrade gone awry. In this case, there appears to have been a difference of opinion about whether a backup was necessary in order to go forward with the SAN upgrade. According to sources of blogger Daniel Eran Dilger, instead of doing a backup that would have taken six days, Microsoft management is said to have decided to curtail the process two days into it. What then ensued is not yet clear, but the implication is that an Oracle system responded to some abnormality in the SAN upgrade that caused the data’s “disappearance.”
Whatever the cause, this scenario highlights the enormous complexity of cloud storage and the inherent risks involved with such a new data-handling approach. Indeed, another recent cloud mishap, in which a hacker was sending spam through an Amazon email server, elicited another calamitous response: Amazon EC2 subscribers had their email put on a spam blacklist by Spamhaus because of this one bad apple.
It’s not surprising these technology glitches are happening, given the newness and complexity of cloud computing. But I think what all three cases show — from the overblown police and media reaction to the image of an airborne balloon, to the software response to a SAN upgrade gone wrong, to Spamhaus’ Draconian solution to deal with a single hacker, is that we’re inexperienced. We don’t yet have enough understanding to deal with these unusual events in a calibrated — not exaggerated — way. The heart of the matter is that, in each case, there may have been an overreaction to an unexpected, but as it turned out not particularly serious, problem.
With all new things, there is a learning curve. Single hackers will be dealt with in a different way in the future. Microsoft will never do an upgrade without backing up first. As for “balloon boy,” it’s likely some adults will look in the attic before calling out the National Guard. And if the balloon incident was staged, a family conspiracy? Well, there are those who believe the Sidekick data wipeout was insider sabotage.
I’m a huge Boston sports fan, so forgive me for moving a bit more slowly than usual this morning. Yesterday’s “Black Sunday” (as it’s already being dubbed) really knocked me — and much of New England, I’d wager — for a loop. At least we have an excellent Celtics season to look forward to….
I’m diving into my SearchCIO.com wrap-up to chase away the blues. As always, read the stories linked below and contact us with any thoughts!
Email archiving solutions and strategies for enterprise CIOs – As an email scandal in the Boston mayor’s office is currently demonstrating, effective email archiving solutions and strategies are an important part of a CIO’s job, as e-discovery, litigation and compliance regulations require detailed email policies.
Disaster recovery is dead; long live continuous business operations – IT disaster recovery is dead, according to the head of the Disaster Recovery Institute International. Here’s how DR is becoming synonymous with business continuity.
ITIL case study: ITIL best practices at two financial services firms – When Barclays Global Investors and Wachovia invested in ITIL, they saw improved efficiencies and huge cost savings. Read their stories here and feel free to share your own ITIL experiences below.