Webinar: How FamilySearch fixed a disconnect between development and localization

Update – The Webinar Recording is Available – View it Instantly by Completing the Form Below
FamilySearch had been globalized for years. family search webinarIt’s an actively used, dynamic site with a worldwide audience and presented in fourteen languages. But despite having a large and resourceful team of translators and tools, site updates that require localization caused backlogs and disparities between development and localization teams. This problem was costing FamilySearch time, money and resources, all of which could have been deployed to develop new content and features. As a result, product teams experienced significant barriers in improving the global experience of the site. Many companies successfully internationalize and localize. But, because they have little technology to innumerate, support and maintain globalization, measuring and maintaining the process is difficult. As a result they experience expensive delays and reactive surprises. FamilySearch turned to Lingoport and Globalyzer Express solve these problems. FamilySearch selected Globalzyer Express because of the ease of implementation and minimal disruption to development release cycles. Using Globalyzer and Lingoport’s Professional Services, FamilySearch created an integrated system to automate, track, verify, approve and implement interface and content changes.
As a result, FamilySearch was able to:

  • unify development and localization teams
  • measure and share changes that affect localization in each sprint, translation scheduling, turnaround and updated builds
  • improve the workflow between product builds and translation updates
  • automate to eliminate chances for errors that cause blow-up problems, while keeping controls to ensure an accurate update process
  • significantly reduce time to market, making site improvements available to international users on an accelerated schedule

Update – The Webinar Recording is Available – View it Instantly by Completing the Form Below

Rob Thomas of FamilySearch.org and Adam Asnes, CEO of Lingoport, are hosting a joint webinar.

We will present:

  • the scope of the problems and project
  • architectural and process descriptions
  • examples of the process in action
  • measured results

Webinar: Managing Software i18n Development and Localization

Recording Now Available: Complete Form to View (instantly)

Let’s suppose you’re having new global sales opportunities, or your company’s software products are already global. You want to make the software development and localization process better. There’s usually plenty of room for improvement saving both money and hassle. Based on our experience performing and assisting companies with both i18n (internationalization) products and development services, we’ll be presenting a condensed approach to managing software i18n development and localization processes more effectively.

You’ll learn:

  1. How to manage the business case – get good metrics, enough time and money
  2. A Checklist for establishing requirements
  3. Building a plan (including examples)
  4. Steps for successful implementation coordinated across development and localization
  5. How to integrate localization with development
  6. Improving ongoing globally focused software development

While Lingoport is well known for our Globalyzer software suite, we also perform a considerable amount of software internationalization implementations – generally under tight deadlines and budget constraints. This webinar will include aspects of our methodology for repeatable success over a wide variety of technologies and applications.

Who should attend:

  • Development managers
  • Team leads
  • Internationalization leads
  • Localization managers and engineers
  • QA Leadership

Here are the details:

Date: April 9, 2014

Time: 9:30 am PDT/12:30 EDT/6:30pm CET.

Presenter: Adam Asnes, Lingoport’s Founder and CEO

Six Steps to Successfully Manage Software Internationalization

Global opportunities are going to force you to evaluate how to adapt your code and ongoing development to support localization. Sometimes it starts with a potential new partnership, sale or strategic initiative. Yet it’s not clear what will be involved for development.  When you manage internationalization poorly you create unknown risks to your budget, timing, resources and strategic objectives.

You may know some of the basics or even been through a project like this once or a few times before, but it’s typically a messy, poorly enumerated, trial and error process. It’s distracting to other development objectives while containing unknown risks to your budget and timing.

Here’s a brief guide towards a successful implementation:

1)   Learn, Build and Support the Business Case – Internationalization (i18n) and ongoing localization (l10n) is going to have a significant cost and unless the business case is defined, the project is unlikely to get done. Even if it seems like that should be sales and marketing’s job, you’ll need to have some parameters as budget can cause some trade-offs.  Companies should not go into globalizing product development without clear commitment, as a bad final product may hurt sales goals more than it helps. A failed i18n initiative can be harmful to your own company objectives as well.

2)   Clarify Your Global Release Objectives and Concurrent Development  – i18n isn’t like planning a feature release. It’s likely not to fit neatly with whatever concurrent sprint your team is planning. It touches a good deal if not all of your application, rather than being like adding a feature or fixing a bug in a particular sprint and area of your code. You’ll need a branching, merging and testing strategy that covers the full i18n scope. Keep that in mind as you go through the next two steps.

3)   Assess and Document Requirements – Establish user requirements as they relate to target locales. i18n is almost never just a string externalization exercise you can pass to an intern. You’re going to need to put some thought into locale requirements, how data is going to flow through your application, changes to your database, methods/functions/classes that will have to be made locale-aware and of course the U/I and all it’s strings.  At a higher level, there are some products that need rethinking in terms of user workflow for different countries. Write those i18n requirements down in a document. That will help you organize for the next process.

4)   Build a Plan – Tasks, Time, Cost, People and Dependencies. This is an essential step and even if you’re the type that thinks project plans are meant to be broken, you need to do this and do it to a granular level. When we work on a project we typically build a plan that starts with about 200 tasks and goes upwards with size and complexity (consider this for multi-tiered applications). To do this, we analyze the code base with our software product, Globalyzer, which gives us detailed static analysis on internationalization issues that will need to be addressed. We combine that with architectural analysis from whiteboard discussions and requirements documentation. Building a plan will give you a realistic check on the business case as well. That feedback to business case can have an effect on activities like phasing various levels of functionality if that’s appropriate to your user requirements.

5)   Reduce Risks and Manage Trade-offs – Every development project has its risks. In the case of i18n, being late is very expensive. The risk can be a broken agreement, market launch and business plan. A three month delay may make an annual revenue goal unattainable. Due to a lack of understanding of requirements and scope, poor internationalization will result in a poor localization outcome. If after all that investment, the end product can’t be properly executed, then it’s self defeating. There’s also the risk that due to distractions and/or misdirection, you don’t get the work done and the project just dies or hangs in limbo. As for trade-offs, internationalizing a large application is generally resource intensive. It’s a solid assumption that development teams don’t have lots of people with nothing to do, so in cases where you have lots of legacy code, you may need an implementation partner in order to keep up with ongoing development objectives outside of internationalization.

6)   Long Term Support – Once you internationalize and localize, your ongoing development has a new set of requirements. You’ll want to measure internationalization just like any other coding quality and ideally not have to wait until testing to find out if i18n is broken. For your ongoing agile development, it’s good to automate managing changes to strings that may change somewhat with every release. This keeps you from having to do engineering bookkeeping to process the localization of those 26 or so new words that may need translation into your supported languages in the latest sprint.

Our Globalyzer software is a keystone to our services operations when clients hire us to provide internationalization consulting and implementation for them, but it’s also important for our clients in supporting development teams in their initial and ongoing efforts to create and maintain software for global customers, faster, better and with less headaches.

Learn more about managing internationalization:

Agile and Localization:

Internationalization Planning:

Measuring Internationalization and Localization:

Making Static Analysis Work for Software Internationalization and Localization

Recording Now Available: For access, please fill out the form at the bottom of this page

A proactive approach to building and maintaining software supporting global customers, and their language and cultural requirements

Static Analysis, a process of evaluating source code for ongoing development without running the software like during testing, has been effectively harnessed for supporting quality, security and other coding requirements. We will show how it can be applied to globalized software development for big productivity and release gains.

What’s Good: Potential as a big time saver, better quality and releases. Quickly find and assist with internationalization (i18n) and ongoing U/I changes affecting localization (L10n).

What’s Bad: If it’s not properly implemented, static analysis can be a forest of false-positive issue distractions.

We’ll take a practical look at how to make static analysis internationalization and localization work for your team.

When: For recording access – fill out form below (this webinar was presented in December 2013)

Duration: 50 minutes

To View: form at bottom of page

Here’s what we’ll cover:

  • Background on static analysis and testing for globalization
  • Agile development demands on globalization
  • Successful real world examples
  • Benchmarks for accuracy and acceptance
  • Continuous integration for i18n & L10n
  • Working on legacy code
  • Working on ongoing development
  • Connecting U/I changes with translation systems

Who should attend: 

Technical managers and engineers looking for a systematic way to improve the development, release and ongoing features for software that supports languages and cultural formatting worldwide.

Bridging Gaps Between Localization & Development

Here’s a 10 minute whiteboard talk posing a solution for gaps in understanding that happen between localization, development, management and QA teams with a focus on agile teams and schedules. Organizational visibility and systems integrated cleanly with build management make for proactive internationalization and localization. We’ll have a webinar with more detail and examples on the subject on October 15th. Learn more and register for the webinar and please watch the video below.


Webinar: Bridging the Gap Between Development and Localization

Webinar: October 15, 2013, 9AM Pacific, Noon Eastern, 18:00 CEST

Recording Now Available! Please scroll down to the form and enter your information to view.

We hear a common complaint – a disconnection between management, development teams and localization. This is compounded by agile sprints and releases that are unforgiving in terms of backlogs for localization testing and bug fixing. In fact, the whole traditional iterative method of testing for internationalization and localization issues is inefficient and agile-unfriendly, as by nature it’s late in the process and requires additional iterative steps. It’s not generally integrated right into development except by hoping teams are “doing the right thing.”

Though global software customers are growing, they might not be getting the best user experience, and it’s hard for your teams to measure and integrate ongoing global quality metrics. We check for all kinds of bugs and security with automated tools that integrate into development process. But what about issues like software internationalization and localization?

What: Bridging the Gap between Development and Localization Webinar – a new integrated system for monitoring and managing internationalization and localization

When: Tuesday, October 15, 2013, 9AM Pacific, Noon Eastern, 18:00 CEST

(We are considering a second presentation at an earlier time for Europeans and others. Please email if you have a strong preference for that)

Cost: Free

In this webinar, we’ll be showing real world projects managed with a new solution using the best parts of Globalyzer’s internationalization (i18n) static analysis combined with technologies for localization and activity visualization that we’ve been developing since last year.  The result bridges development and localization processes simplifying activities, making metrics easy and visible and aiding the entire flow of building and localizing products for ongoing development.

What you’ll learn:

  • How to integrate software globalization more tightly with ongoing development
  • How to make faster and more complete progress on internationalization technical debt
  • Easier way to manage and integrate localization of existing and ever changing resource files
  • An easy way to pinpoint issues even before testing, and certainly before localization

Who should attend:

  • Development Managers
  • Localization Managers
  • Project and Product Managers
  • Developers
  • Localization Engineers
  • Localization Specialists

We’ll have live Q&A as well. You are welcome to submit questions in advance or during the webinar.

Whiteboard talk: Issues on supporting internationalization and localization during agile development

In the video below, Adam Asnes gives a short informal presentation introducing some conceptual issues around supporting i18n & L10n while meeting the challenges produced when supporting software globalization requirements using agile and other methodologies.

This video is a precursor to our Continuous Internationalization in Every Sprint and Release webinar we’ll be presenting on July 31, 2013. Registration is free, or if you’re seeing this after the webinar date, we will have a recording available in the resources section on http://lingoport.com. 

Painless Internationalization (i18n) for every Sprint

Making i18n reporting and fixing easy and a natural part of development

One of the main barriers to improving i18n processes is the investment it can take in tools, systems, expertise and personnel. What if we could make it easy? No expertise needed to get started. No tools to learn – nothing to install. Lingoport’s experts set it up for you – quickly and affordably. Developers can stay on top of i18n simply and easily for every sprint. Localization teams know what’s coming and Management has clear metrics for globalization status. Sounds nice right? We’re calling it Globalyzer Express. Look below:

Screen Shot 2013-06-28 at 6.15.09 PM(click image to enlarge)

This is a top-level view of our i18n Dashboard. It’s being fed by Globalyzer command line, which is connecting to source control. All issues can be drilled down in code line detail like so:

Screen Shot 2013-06-28 at 6.21.52 PM (click image to enlarge)

Developers can concentrate on the area of code they are working on, and simply go through the issues detected and fix them. The dashboard tracks activities. You’re product is i18n ready, right in the current sprint. No buildup of i18n technical debt, and if you have i18n debt, your team can clearly work its way through it. You get real time i18n code metrics and review, rather than trying to catch up later with ad-hoc testing. This is taking the best practices of software development and bringing them to internationalization but we’ve made it easy.

Agile and Internationalization

In discussing the Globalyzer Express concept with customers, it’s clear that there’s extra benefit to this solution if the team is using Agile or Agile-like development methods. There are several reasons for this:

  • There’s no time to go back and fix i18n issues later – the team has moved on
  • Each developer can quickly navigate to their part of the code reporting, and fix or mark their issues. I18n gets distributed where it’s least costly to fix.
  • Localization teams will know what changes are coming in advance (Globalyzer Express tracks changes to resource files), and be able to verify code readiness before localization starts on fast moving updates

How does it work?

We set it all up, configure and fine tune specifically for your software. Our team lives for i18n, so you leverage that quickly. It works for lots of programming languages and database scripts. There’s no learning curve or tools configuration and analysis burden for your team.

We host it all in a SaaS configuration when granted read access to your source repository, or Globalyzer Express can work behind your firewall by installing several of the Globalyzer Suite components. You’re productive right away. As for licensing fees, it’s all quite reasonable with quarterly payments within your budget. We think you’re going to like this. We’ll be providing more details shortly, but in the meantime, contact Lingoport to learn more and get a guided tour.


2013 Internationalization and Localization Conference Videos

All conference videos are available on Lingoport’s Vimeo page, here: http://vimeopro.com/lingoport/2013-internationalization-and-localization-conference

Also, see our conference photo album at Facebook.com/Lingoport

Presentation Slides

View the Recordings from the i18n & L10n Conference

Miss anything from this year’s Internationalization and Localization Conference? Have no fear. We recorded each of the sessions, and those sessions are now available for your viewing pleasure.

2013 Internationalization and Localization Conference Videos

All conference videos are available on Lingoport’s Vimeo page, here: http://vimeopro.com/lingoport/2013-internationalization-and-localization-conference

Click Here to View Recordings of the 2013 i18n & L10n Conference