Shifting Left Webinar Slideshow
-
Upload
lingoport-wwwlingoportcom -
Category
Technology
-
view
645 -
download
1
description
Transcript of Shifting Left Webinar Slideshow
Tuesday, February 21, 2012
Beginning at 11am PT
Feel free to ask questions using the GoToWebinar Q&A interface.
Twitter hash-tag: #ShiftLeft
Shifting Left
Adam AsnesPresident & [email protected]
Olivier LiboubanGlobalization [email protected]
2012 Internationalization and Localization Conference│March 14-15, Santa Clara, CA
Wednesday, March 14th
Full-day technical internationalization training class
Led by Olivier Libouban, Globalization Lead at Lingoport
Thursday, March 15th
Internationalization and Localization Conference
The main conference features an entire day of i18n and L10n focused presentations, roundtables, and panel discussions.
Presenting companies include: Acrolinx, Adobe, Autodesk, Cisco, Common Sense Advisory, Intel, Jonckers, LinkedIn, Lingoport, Moravia, Rearden Commerce, Twitter, Yahoo!, Zynga, and more.
Learn more and register at: www.lingoport.com/2012-i18n-conference or wwww.lingoport.com or contact Chris @ [email protected]
Lingoport
• Help software developers excel in delivering global-ready applications for worldwide customers– Internationalization Services– Globalyzer
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
Shifting Left – Mature Localization
• Localization practices and technology– Translation Memory hardly new– Tools/technology to manage words & processes– Sourcing
• Machine translation• Crowdsourcing
– Price pressure
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”
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
Organizational Perceptions of i18n
Developers:• Isn’t that localization’s
problem?• I have other features
to deliver
L10n Managers:• I’m caught in the
middle
Business Managers:• Where is it already?• Over budget and late
Organizational Perceptions of i18n
Developers:• Straightforward,
simple, handled• Tier 3 bugs, at best• Features come first• Not enough time
L10n Managers:• Issues come up with
every release• Tier 1,2 &3 bugs• Not enough support
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
Traditional Testing & Pseudo Localization
Localize and see what you’re missing
Search, overwhelm developers
View pages. Pour through code for
strings, methods, etc.Externalize and
refactor one by one
Test, Pseudo-Localize
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
Static Analysis
• Analyze the code for issues– As it’s created– Regular intervals like builds– As a QA release requirement– Keep score over time
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
Server
WorkbenchCommand Line
A Peek at Globalyzer 4.0 (in beta)
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
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.”
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
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.
Lingoport Champions
Your CompanyHere?
Questions & Answers
Adam Asnes
Chris Raulf
Resources: www.lingoport.com
2012 i18n & L10n Conference
March 14-15, Santa Clara, CA
www.lingoport.com/2012-i18n-conference
Next steps:
- Talk to us about your i18n needs- Free Globalyzer trial: www.lingoport.com/globalyzer-trial
Thursday, February 23, 2012
Beginning at 11am PT
Feel free to ask questions using the GoToWebinar Q&A interface.
Twitter hash-tag: #ShiftLeft
Shifting Left Part II – i18n in Real-Time
Adam BlauVP [email protected]
Olivier LiboubanGlobalization [email protected]
2012 Internationalization and Localization Conference│March 14-15, Santa Clara, CA
Wednesday, March 14th
Full-day technical internationalization training class
Led by Olivier Libouban, Globalization Lead at Lingoport
Thursday, March 15th
Internationalization and Localization Conference
The main conference features an entire day of i18n and L10n focused presentations, roundtables, and panel discussions.
Presenting companies include: Acrolinx, Adobe, Autodesk, Cisco, Common Sense Advisory, Intel, Jonckers, LinkedIn, Lingoport, Moravia, Rearden Commerce, Twitter, Yahoo!, Zynga, and more.
Learn more and register at: www.lingoport.com/2012-i18n-conference or wwww.lingoport.com or contact Chris @ [email protected]
Yin & Yang of Software Globalization
Yin & Yang of Software Globalization
Internationalization (i18n): Process of making a single code base locale-independent, so it can be localized without source code changes.
Localization (l10n): Translation & application of locale terms and style so that it looks locale-specific, i.e. looks and reads like a product native to the respective market.
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 groups
Is there another tool / process that can bring 15% savings to current, mature localization models?
Yes, no, maybe?
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.
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.
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.
• 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.
i18n Focus to streamline L10n