Now that we’ve determined that your company is in need of SOA, you must now tackle the further complicated task of working with people to get this thing rolling. Most IT projects fail due to people-related issues rather than from technology problems. For one, IT is an expensive investment. Two, we’re resistant to change. And third, leaders and users fall short of delivering and fully using new technology. Unless your company has a greater ratio of robots and machines to people, you may want to brace yourself for the following list of IT human-hurdles.
Mistake: Failure to explain SOA's business and organizational value
When making any kind of proposal, you must pique the listener’s interest. Just as a savvy car salesman would highlight different features of an SUV when trying to sell to a college student, a mother of 3, or an elderly couple, you want to do the same when explaining SOA to different people at your company. So don’t approach SOA from a purely technology perspective, but highlight its abilities to solve real business problems. Remember, people are always thinking, “So, what’s in it for me?”
Mistake: Resistance to Organizational Change
As with any initiative for change, resistance may just be the strongest project killer. Well get ready, because SOA is the king of change. Inform all people throughout the organization of what to expect because SOA will affect people at different levels in different ways. Knowledge provides the mental preparation needed for a successful organizational change.
Mistake: Weak Executive Sponsorship
Without strong executive sponsorship, it is highly unlikely that your SOA initiative will accomplish its goals. SOA spans multiple departments, multiple systems, and is a major undertaking. You need a strong executive to keep the initiative moving forward despite challenges and protests. An ideal leader will maintain a sense of urgency in making SOA its priority.
Mistake: Lack of SOA Expertise
The idea of implement SOA without any SOA experience is a major mistake. If you think that your company can take on a SOA project without outside help to avoid the high rates of expert consultants, think again. Unless you have an in-house team that know SOA inside and out, trying to do SOA on your own can be a recipe for disaster—and be more costly at the end. SOA covers not only the IT departments of testing, infrastructure, and security, but also business. You need SOA professionals that have the skills to successfully deliver SOA to your organization, as well as train your staff on process improvement.
Mistake: Poor Project Management
To sum, PM is all about making the project happen. It is a discipline of initiating, planning, executing, and managing resources with the goal of completing specific deliverables within budget and time. A successful project manager is one who can envision the entire project from start to finish, and have the prowess to realize this vision. If your organization struggles delivering normal projects, your chances of success with SOA will be twice as challenging.
Mistake: Giving SOA Vendors Full Reign and a Blank Check
Most vendors have much in common with sales—their main goal is to sell you as much products as possible. “Mucho Tools = IT Success!” Such a concept will leave you with a heap of expensive useless technology. To prevent such a disaster from occurring, it is important to do your homework before signing any kind of contract with a vendor. Read up on SOA, talk to other companies that have implemented SOA, and perform a thorough vendor evaluation process.
Previous << Page 4 of 6 >> Next
