Localization To The Far East Case Study

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    Favorites, Groups & Events

    Localization To The Far East Case Study - Presentation Transcript

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

    + Aviram EisenbergAviram Eisenberg, 4 months ago

    custom

    265 views, 0 favs, 1 embeds more stats

    This presentation was part of a lecture that was gi more

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 265
      • 264 on SlideShare
      • 1 from embeds
    • Comments 0
    • Favorites 0
    • Downloads 5
    Most viewed embeds
    • 1 views on http://www.plaxo.com

    more

    All embeds
    • 1 views on http://www.plaxo.com

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories