Agile software development is challenging to support with localization when the source code is not ready for the world. Globalization and localization directors aspiring to run an effective operation need to ensure that the updates their developers push out follow localization requirements — but what does internationalization (i18n) readiness mean? What are the requirements that enable continuous localization? In this panel discussion three experts will elaborate on these requirements and present a “shift-left” approach to designing i18n-compliant software.
Takeaways: Attendees will learn the requirements for i18n readiness, developer best practices for i18n readiness and practical advice on how to explain the importance of I18n compliance to nonindustry members.