Enterprise Service Bus
Planning and Conducting Enterprise Service Bus Rides (Part II)
By Brenda M. Michelson, Principal, Elemental Links
*Editor’s Note: This is an excerpt prepared for ebizQ from a report originally issued by the Patricia Seybold Group on December 15, 2005. The full report details are available at http://www.psgroup.com/detail.aspx?ID=668
Read part I of the ebizQ excerpt here.
CONDUCTING THE VENDOR RUN-OFF
- Get Everyone on the Same Page. Day one, hour one, bring your team and the vendor team together to walk through the objectives, schedule, roles, and expectations for the vendor run-off period. Be explicit about the rules of interaction during the test period—particularly when it is appropriate for observers to ask questions, and how that time will be recorded. Remember, the vendor is in a race.
- Learn by Observation. Take the opportunity to watch as the vendor team exercises the products in design, development, deployment, and
runtime. Make note of the artifacts the vendor has produced on-site and what (if any) were produced ahead of time.
- Schedule Check-Ins. Assuming the run-off is a multiday engagement, schedule start- and end-of-day check-ins. Discuss status, problems encountered, and the next day’s plan. Use this time to get a demo of work to date.
- Use Problems as Opportunities. If there are problems during development or execution, use them to learn about the product’s problem detection and resolution capabilities.
- Remember Quality of Service and Protection. While it is difficult to test all aspects of QOS and QOP in a run-off, ask the vendor to share how QOS and QOP can be achieved in your environment. The information may be relayed in a whiteboard discussion, through documentation, or pointing out console options.
- Stay in the Room! Observe the entire process, to learn, and to evaluate.
As always, choose wisely, for your business.
About the Author
Brenda Michelson is an IT strategist, hands-on practitioner, and the voice of business-driven architecture. Brenda’s day job is principal consultant for Elemental Links. Brenda also contributes architecturally to the Patricia Seybold Group. Brenda spent 19 years in corporate IT, most recently as Chief Enterprise Architect for L.L. Bean. At L.L. Bean, Brenda was responsible for the articulation and execution of the enterprise architecture strategy (J2EE transformation, enterprise integration, SOA and EDA), strategic planning, portfolio management and talent development. Previous to L.L. Bean, over the span of 10 years, Brenda provided development services for Insurance, Banking, a Chip Manufacturer and a world leader in Aircraft Engine Design & Manufacturing. Email Brenda.More by Brenda M. Michelson
About Elemental Links
Elemental Links is an IT consulting and advisory practice specializing in strategy, architecture, and portfolio planning for business-driven IT.