Shifting Left Webinar Slideshow
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Shifting Left Webinar Slideshow

on

  • 633 views

 

Statistics

Views

Total Views
633
Views on SlideShare
559
Embed Views
74

Actions

Likes
0
Downloads
2
Comments
0

3 Embeds 74

http://www2.lingoport.com 69
https://pi.pardot.com 4
http://www.lingoport.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Globalyzer has three main components:[Click]The Server holds rule sets used to scan source code with the other components. A rule set contains i18n detection and filtering rules for a programming language, such as Java or C#.[Click]The Workbench is a feature-rich i18n environment. It detects and manages internationalization issues. [Click]The Workbench uses the rule sets from the server to scan the code. You can easily refactor code, externalize strings, check resource bundles, generate reports and so on. [Click]The Command Line scans code using rule sets from the server and generates reports without a user interface. Command Line can be automated and integrated in continuous builds and automated
  • Yin & Yang: used to describe how polar opposites or seemingly contrary forces are interconnected and interdependent in the natural world, and how they give rise to each other in turn.In this hands-on one-hour online session, Lingoport will demonstrate how Globalyzer 4.0 (in beta now) fits into the development environment of the engineer. Interacting with source code repositories and a resource assistant to externalize, manage, validate and pseudo-localize strings. See real-time internationalization as we work with source code and learn how Globalyzer, the leading internationalization product, ensures best-step i18n practices and compliance.
  • Yin & Yang: used to describe how polar opposites or seemingly contrary forces are interconnected and interdependent in the natural world, and how they give rise to each other in turn.1). Handle data2). Localize on single code-base3). Methods to handle multiple inputs and outputs4). Hard-coded fonts5). Cultural issues6). Bi-di enablement
  • Translation: cloud-based TM’sMachine translation + post-editingWorkflow tools (TMS, integrators into TMS)MarketplacesAuctionsVLT toolsTesting (costmetic, functional)
  • I18n is often not well understood.Hard to test.

Shifting Left Webinar Slideshow Presentation Transcript

  • 1. Shifting LeftAdam AsnesPresident & CEOadam@lingport.comOlivier LiboubanGlobalization Lead Tuesday, February 21, 2012olivier@lingoport.com Beginning at 11am PT Feel free to ask questions using the GoToWebinar Q&A interface. Twitter hash-tag: #ShiftLeft
  • 2. 2012 Internationalization and LocalizationConference│March 14-15, Santa Clara, CAWednesday, March 14thFull-day technical internationalization training classLed by Olivier Libouban, Globalization Lead at LingoportThursday, March 15thInternationalization and Localization ConferenceThe main conference features an entire day of i18n and L10n focusedpresentations, roundtables, and panel discussions.Presenting companies include: Acrolinx, Adobe, Autodesk, Cisco, Common SenseAdvisory, Intel, Jonckers, LinkedIn, Lingoport, Moravia, ReardenCommerce, Twitter, Yahoo!, Zynga, and more.Learn more and register at: www.lingoport.com/2012-i18n-conference orwwww.lingoport.com or contact Chris @ craulf@lingoport.com
  • 3. Lingoport• Help software developers excel in delivering global-ready applications for worldwide customers – Internationalization Services – Globalyzer
  • 4. Shifting Left - Background• Larger percentages of revenues are worldwide• Companies win global customers faster• Lots of churn in development – Fast to market – Fast release cycles – Mergers and acquisitions – New mix of mediums, including mobile
  • 5. Shifting Left – Mature Localization• Localization practices and technology – Translation Memory hardly new – Tools/technology to manage words & processes – Sourcing • Machine translation • Crowdsourcing – Price pressure
  • 6. What about Code?• Internationalization (i18n) – Often not well understood – Difficult to test• If the code is poorly internationalized: – Delays – Quality – User-experience• “50% of our L10n issues are in the code”
  • 7. Shifting Left• Adding focus to creating world-ready products as an integrated product development goal. – Broadening localization focus to it’s preceding activities during development Shifting Left = Before typical localization
  • 8. Organizational Perceptions of i18n Developers: •Isn’t that localization’s L10n Managers: problem? •I’m caught in the •I have other features to middle deliver Business Managers: •Where is it already? •Over budget and late
  • 9. Organizational Perceptions of i18n Developers: L10n Managers: •Straightforward, simple, •Issues come up with handled every release •Tier 3 bugs, at best •Tier 1,2 &3 bugs •Features come first •Not enough support •Not enough time from dev. •No way to verify until localization •Lack deep knowledge of code Business Managers: •Sales/biz expectations •Time to market •Over budget and late
  • 10. Traditional Testing & Pseudo Localization Localize and see what you’re missing Search, overwhelm Test, Pseudo-Localize developers View pages. Pour Externalize and through code for refactor one by one strings, methods, etc.
  • 11. L10n Testing - Limited Approach• Hard to test all cases – Difficult to find complex processes beyond U/I labels• People and time intensive• Late in the process = more expensive to fix
  • 12. Static Analysis• Analyze the code for issues – As it’s created – Regular intervals like builds – As a QA release requirement – Keep score over time
  • 13. What to Look For• Embedded strings• Locale-limiting functions/methods/classes – Date/time – Collation – Encoding• Programming patterns – Hard coded fonts & encoding – Programmatic logic that breaks i18n/L10n
  • 14. A Peek at Globalyzer 4.0 (in beta) Server Command Line Workbench
  • 15. What About ROI?• Head count – i18n experts duplicate and scale• Time to release – faster time to global markets – Value in being global ready & knowing it• Cost of a bug – $X = $500? • Find • Manage • Fix • Verify
  • 16. Beyond ROI in $• Intel: “Delight our customers, employees and shareholders by relentlessly delivering the platform and technology advancements that become essential to the way we work and live.”• Mission: touching the lives of all the people on Earth – Lots of bugs logged but that’s not the main purpose – “Being able to understand our own business, internal customers and proactively solve problems.”
  • 17. Tweets from @CiscoL10N• Defining user perceptions of a localised product plays a critical role in how internationalization is scored and ranked• An organisation is only managing #i18n if requirements are defined reactively. However #i18n must be controlled and then optimised.• Reactive internationalization_is unpredictable and_poorly controlled #i18n
  • 18. Tweets from @CiscoL10n• Absence of a methodical approach to measuring global readiness leads to aimless and chaotic internationalisation practices.• A Global Maturity Model can and should use #i18n static analysis tools e.g. @Lingoport #globalyzer to sustain accountability.
  • 19. Lingoport Champions Your Company Here?
  • 20. Questions & AnswersAdam Asnes Resources: www.lingoport.comadam@lingoport.com 2012 i18n & L10n ConferenceChris Raulf March 14-15, Santa Clara, CAcraulf@lingoport.com www.lingoport.com/2012-i18n-conferenceNext steps:- Talk to us about your i18n needs- Free Globalyzer trial: www.lingoport.com/globalyzer-trial
  • 21. Shifting Left Part II – i18n in Real-TimeAdam BlauVP Salesablau@lingoport.comOlivier LiboubanGlobalization Lead Thursday, February 23, 2012olivier@lingoport.com Beginning at 11am PT Feel free to ask questions using the GoToWebinar Q&A interface. Twitter hash-tag: #ShiftLeft
  • 22. 2012 Internationalization and LocalizationConference│March 14-15, Santa Clara, CAWednesday, March 14thFull-day technical internationalization training classLed by Olivier Libouban, Globalization Lead at LingoportThursday, March 15thInternationalization and Localization ConferenceThe main conference features an entire day of i18n and L10n focusedpresentations, roundtables, and panel discussions.Presenting companies include: Acrolinx, Adobe, Autodesk, Cisco, Common SenseAdvisory, Intel, Jonckers, LinkedIn, Lingoport, Moravia, ReardenCommerce, Twitter, Yahoo!, Zynga, and more.Learn more and register at: www.lingoport.com/2012-i18n-conference orwwww.lingoport.com or contact Chris @ craulf@lingoport.com
  • 23. Yin & Yang of Software Globalization
  • 24. Yin & Yang of Software GlobalizationInternationalization (i18n): Process of making a single codebase locale-independent, so it can be localized withoutsource code changes.Localization (l10n): Translation & application of localeterms and style so that it looks locale-specific, i.e. looksand reads like a product native to the respective market.
  • 25. Globalization focus: content and words• TM’s: Cloud-based TM, integration with TMS & machine translation engines.• Machine Translation + post-editing• Crowdsourcing• Translation Management Systems• Marketplaces, auctions and management platforms• Centralized localization service groupsIs there another tool / process that can bring 15% savings tocurrent, mature localization models?
  • 26. Yes, no, maybe?
  • 27. Challenges to focus on i18n• Who owns i18n? Software development or L10n?• What processes and tools can: – mold i18n guidelines with developers environment around the world? – ensure compliance during development or QA, not during localization?• Development times are shorter. – Focus on “hot fixes” or i18n bugs? – Are i18n bugs Tier 1 or 3?• Difficult to test complex process beyond U/I labels.
  • 28. Importance on i18n compliance• i18n compliance through iterative QA cycles and releases is a waste of money and time.• Finding, managing, fixing and verifying i18n bugs is costly. Averages start at $500.• Releasing core products to worldwide markets faster creates revenue opportunities, not just cost savings.• “Reactive internationalization is unpredictable and poorly controlled.” – Gary Lefman.
  • 29. Founded on three core principles:1. Making software world-ready is a priority, not a side project.2. There should not be surprises in coding software for the world.3. Internationalization (i18n) should be a leading priority for software development.
  • 30. i18n Focus to streamline L10n• Develop products that produce scalable, repeatable and accurate processes for global releases.• Design them specifically for software engineers, QA teams and their managers to find, fix and report i18n bugs.• Produce knowledge for management to measure & scope i18n readiness and progress on technical debt.