Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Localization To The Far East Case Study


Published on

This presentation was part of a lecture that was given durign LISA 2009 - Global Outsourcing Services and Software Development held in Talinn Estonia June 2009

Through a case study of a global localization project, the presntation describes the advantages and challenges created when combining offshoring , global delivery model and agile development methodology

Published in: Technology, Business
  • Be the first to comment

Localization To The Far East Case Study

  1. 1. Localization to the Far East - Case Study Aviram Eisenberg, CEO, Ignite
  2. 2. Agenda Off-Shoring Global Delivery Agile Development
  3. 3. Ignite Ltd <ul><li>Ignite is an Outsourcing Boutique </li></ul><ul><li>Pure Play Software Development Company </li></ul><ul><li>Global Delivery Model (onsite-offshore) </li></ul><ul><li>Agile Development Methodology </li></ul><ul><li>Strong onsite staff (senior R&D Managers) </li></ul><ul><li>Five offshore centers (in Russia, Ukraine, Belarus and Mexico) </li></ul><ul><li>Tailor-made software development solutions </li></ul>
  4. 4. The Need for Localization - 2009 <ul><li>Global economy require global solutions </li></ul><ul><li>Current financial crisis drive ISVs to inspect their business models </li></ul><ul><li>Small to mid-size ISVs are shifting focus to the BRIC countries </li></ul><ul><li>While India does not require localization Brazil, Russia and China do </li></ul><ul><li>35% increase in localization projects started </li></ul>
  5. 5. The Customer <ul><li>A mid-sized international software vendor </li></ul><ul><ul><li>US management and marketing </li></ul></ul><ul><ul><li>Israeli RD center </li></ul></ul><ul><li>Until 2008 focused only on the US and EU markets </li></ul><ul><li>A highly technical product targeting IT managers </li></ul><ul><li>High investment in trainings, hence expensive deployments </li></ul><ul><li>As financial crisis developed changed focus to the Far East market: China, India, Japan </li></ul>
  6. 6. The Project Scope <ul><li>Deliver the Japanese-based version within three months </li></ul><ul><li>Over 60,000 resource lines </li></ul><ul><li>Over 3500 online documentation pages </li></ul><ul><li>Globalization infrastructure to be done by internal R&D staff </li></ul><ul><li>Translation to be done by external provider </li></ul><ul><li>QA: joint effort customer + provider </li></ul><ul><li>Acceptance to be done by a Japanese distributor </li></ul>
  7. 7. Global Delivery Model Marketing R&D Translation team? Test team? Acceptance
  8. 8. The Challenges <ul><li>Where? </li></ul><ul><ul><li>What is the offshore location best suited for this task? </li></ul></ul><ul><li>What? </li></ul><ul><ul><li>The project scope does not fit the time frame </li></ul></ul><ul><li>How? </li></ul><ul><ul><li>How do we meet the deadline? </li></ul></ul><ul><ul><li>How do we transfer knowledge in such a short time frame using globally distributed teams? </li></ul></ul>
  9. 9. Where? <ul><li>Japanese team and Chinese team </li></ul><ul><ul><li>Expensive </li></ul></ul><ul><ul><li>R&D Bottleneck </li></ul></ul><ul><li>Pure Chinese team </li></ul><ul><ul><li>Translate English-Chinese first and then translate Chinese-Japanese </li></ul></ul><ul><ul><li>Cost-effective </li></ul></ul><ul><ul><li>Not according to customer priority </li></ul></ul><ul><li>Belarusian team </li></ul><ul><ul><li>Hybrid native speakers and linguistics team </li></ul></ul><ul><ul><li>Cost-effective </li></ul></ul><ul><ul><li>Same time zone as R&D </li></ul></ul>
  10. 10. What? <ul><li>Only three months for the Japanese localization project </li></ul><ul><li>Delivery dates to end-customers cannot be changed </li></ul><ul><li>Prioritize the requirements </li></ul><ul><li>Adjust the scope - not the delivery date </li></ul><ul><li>Initial scope included: </li></ul><ul><ul><li>Installer </li></ul></ul><ul><ul><li>User Manual </li></ul></ul><ul><ul><li>The main admin component </li></ul></ul><ul><li>A second and third deliveries included the rest of the components </li></ul>
  11. 11. How? <ul><li>Even after the scope change – the time frame is still very tight… </li></ul><ul><li>Vertical work instead of horizontal one </li></ul>
  12. 12. Waterfall-based Localization Build Glossary Test Fix Translate Translate Test Test Fix Fix Translate
  13. 13. Agile-based Localization Fix Fix Test Test Translate Translate Translate Translate Fix Fix Test Test Translate Translate Build Glossary Translate Test Fix Update Glossary Translate Test Fix
  14. 14. Agile-based Localization (cont) <ul><li>Test Automation: </li></ul><ul><ul><li>Code level automation of resource occurrences in UI </li></ul></ul><ul><ul><li>Automate translation tests </li></ul></ul><ul><ul><li>String length comparison automation </li></ul></ul><ul><li>String too long/short </li></ul><ul><ul><li>Identify suspects using string length comparison automation </li></ul></ul><ul><li>Wrong translation/Missing translation </li></ul><ul><ul><li>Identify suspects using automated translation tests </li></ul></ul><ul><ul><li>Pinpoint the screens in which a resource is used using code level automation of resource occurrences </li></ul></ul>
  15. 15. Knowledge Transfer <ul><li>Testing team does not enough time to learn the software </li></ul><ul><li>Send QA manager from the customer site in Israel to Belarus </li></ul><ul><li>Attach a Belarusian senior tester to him </li></ul><ul><li>Spin Testing </li></ul>
  16. 16. Global Delivery Model Marketing R&D Translation team Test team Acceptance Requirements I18N Ready SW Translated SW QA Leader Defects Localized SW
  17. 17. Q&A Aviram Eisenberg [email_address]