ESN 5860207120150315129

Rate Content: 1 vs Document Name: Lessons Learned from our first SOA implementation - Part 2 Document Description: WHAT NOT TO DO... NOT ENOUGH PROFESSIONAL SERVICES - OUR BUDGETING PROCESS ONLY INCLUDED ENOUGH HOURS TO INSTALL THE STACK. WE SHOULD HAVE COVERED A FEW MORE WEEKS OF PROFESSIONAL SERVICES FOR WHEN WE FIRST DEPLOYED CODE INTO THE DEVELOPMENT AND TESTING ENVIRONMENTS. ABOUT A MONTH AFTER WE INSTALLED THE BPMS AND ESB, WE DEPLOYED OUR FIRST BUILD ON THESE ENVIRONMENTS. WE ENCOUNTERED ALL KINDS OF ENVIRONMENTAL ISSUES AND VARIOUS INTEGRATION ISSUES BETWEEN THE VARIOUS COMPONENTS OF THE STACK, ESPECIALLY THE PORTAL AND BPMS. SINCE WE DIDN'T HAVE BUDGET FOR ANY MORE PROFESSIONAL SERVICES WE TRIED TO FIGURE IT ALL OUT OURSELVES. EVENTUALLY WE BROUGHT THE VENDOR IN AND ATE SOME INCREMENTAL COSTS BUT WE LOST ABOUT A MONTH WHICH DELAYED THE PROJECT. NEEDED MORE VENDOR REFERENCES - THIS IS NOT FOR THE SELECTION CRITERIA BUT FOR IMPLEMENTATION. WE SHOULD HAVE SOUGHT OUT MORE COMPANIES THAT HAD BEEN THROUGH AN IMPLEMENTATION USING THESE PRODUCTS. WE ARE NETWORKING WITH A FEW LOCAL COMPANIES NOW BUT IT WOULD HAVE BEEN NICE TO HAVE HEARD THEIR EXPERIENCES EARLIER AND WE MIGHT HAVE PREVENTED SOME OF THE SETBACKS OR RESOLVED ISSUES QUICKER. DOVE IN TOO FAST - THIS ONE WE DIDN'T HAVE MUCH CONTROL OVER. THE DOWNSIDE OF HAVING THE BUSINESS FUND SOA IS THAT THEY WANT RESULTS IMMEDIATELY. WE STARTED OUR FIRST PROJECT WITH NO GOVERNANCE, NO TESTING STRATEGY, NO AUTOMATED BUILD PROCESS, ETC. WE ARE TRYING TO IMPLEMENT GOVERNANCE ALONG THE WAY BUT IT ALWAYS TAKES A BACK SEAT TO DUE DATES. FORTUNATELY, A NEW BUDGET STARTS IN JANUARY AND WE CAN GET THE RESOURCES WE NEED TO GET THESE IMPORTANT TASKS DONE. THREW THE KITCHEN SINK AT THE FIRST ITERATION - I WROTE A NOT ENOUGH INTERNAL RESOURCES INVOLVED EARLY ENOUGH - WE PARTNERED WITH A CONSULTING FIRM TO HELP TEACH US HOW TO PROPERLY ARCHITECT SOFTWARE IN THE NEW WORLD OF SOA. AT THE SAME TIME I HAVE BEEN WORKING WITH THE LEADERSHIP TEAM IN IT AND THE BUSINESS TO FREE UP MORE INTERNAL RESOURCES SO WE CAN START DOING THIS OURSELVES. THIS HAS TWO BAD SIDE EFFECTS. FIRST, VERY FEW OF OUR OWN PEOPLE WERE RECIPIENTS OF THE KNOWLEDGE TRANSFER AND TWO, THE VENDOR DOES NOT KNOW OUR BUSINESS WHICH HAS LED TO SOME GAPS IN REQUIREMENTS AND SOME ARCHITECTURAL DECISIONS THAT WERE MADE THAT WE HAVE HAD TO CHANGE. NEEDED MORE CHANGE MANAGEMENT - I DID SPEND A LOT OF TIME FOCUSING ON COMMUNICATIONS & ORGANIZATION IMPACTS BUT THERE WAS STILL A LOT OF "WE VS. THEY", RESISTANCE, AND CONFUSION ABOUT THE OVERALL DIRECTION. THE CORE TEAM WAS HAS ALWAYS BEEN ON THE SAME PAGE, BUT MANY SPECTATORS ARE STILL IN THE DARK. THIS OFTEN LEADS TO RESISTANCE AND NEGATIVELY WHICH WE DEAL WITH IMMEDIATELY, BUT IT WOULD BE NICE NOT TO HAVE TO SPEND AS MUCH TIME RESOLVING THIS ISSUES. DIDN'T RESEARCH SOA TESTING ENOUGH - ONE OF THE THINGS WE DID RIGHT WAS RESEARCH THE HECK OUT OF SOA AND BPM. BUT ONE AREA THAT WE DIDN'T INVEST MUCH TIME IN WAS THE TESTING. WE ARE ACTIVELY RESEARCHING THE HECK OUT OF IT NOW BUT MY ADVICE TO OTHERS IS Author: Michael Kavis - Contact Author Publisher: Michael Kavis Licensee Name: Michael Kavis Reference URL: http://blogs.ittoolbox.com/eai/madgreek/archives/lessons-learned-from-our-first-soa-implementation-part-2-20936 Copyright: All Rights Reserved Registration Date: 12/2/2007 5:04:13 AM UTC Views: 1532

NUMLY.COM