In the global village, some talks inEnglish the others in their own local langauge, when it comes to the global websites with international users, their users should be able to interact with the website with their own language.

The process of internationalization for a large-scale application (website) is usually time consuming; I'll show you how to split the internationalization process into different sprints and implement a successful internationalized application.


2 favorite thumb_down thumb_up 6 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist

Outline/structure of the Session

HTML5 Slideshow

Learning Outcome

Participants whould learn how to  localize and internationalize web applications

Target Audience

Web Designers, Web Developers, Project Managers, Agile Architects

schedule Submitted 5 years ago

Comments Subscribe to Comments

comment Comment on this Submission
  • steve ropa
    By steve ropa  ~  5 years ago
    reply Reply

    Hi Nasser,

    I'm thinking about would make me want to attend this session at an Agile conference.  I think what would sway me is there were more information on how Agile affects my ability to localize and internationalize.  You mention in the cooments you use Agile arechitecture.  Can you update your proposal with a little information on what that means and how you will explainit?




    • Nasser Hadjloo
      By Nasser Hadjloo  ~  5 years ago
      reply Reply

      Dear Steve

      Localization is not a matter of displaying text in different languages, it is about BiDirectionality, Culture specific elements, Calendars, input character encoding and many other aspects in which influence the application. Clearly, it is not wise to consider all of these aspects from the scratch, you should know how to split these different items in different sprints so that you can have a successful ulti-cultural application.

      I'll talk about this splition and give you a perspective of Agile architecture for a multi-language application



  • Sachin goel
    By Sachin goel  ~  5 years ago
    reply Reply

    Hi - will help if you can add a bit more details on Process section. How would you take along the audience with you in this journey?

    thanks - sachin

    • Nasser Hadjloo
      By Nasser Hadjloo  ~  5 years ago
      reply Reply

      Dear Sachin

      I'll provide an interactive HTML5 slideshow which covers my talk, during the talk I'll ask some questions from the audiencess.

      All in all my talk is more about the process of localization in an Agile architecture. at the end of the presentation you can answer this questions

      What is the best way to make a multi-cultural application 

      Which parts can be post-poned and which parts should come first


  • Pramod Sadalage
    By Pramod Sadalage  ~  5 years ago
    reply Reply


    This is a relevant topic of concern to many teams, maybe you can clarify the tecnologies used in your case study and also clarify if the techniques can be translated to any other language/technology.




    • Nasser Hadjloo
      By Nasser Hadjloo  ~  5 years ago
      reply Reply

      Dear Pramod

      I'll talk about Microsoft .NET technology especially Asp. NET and Asp .NET MVC. Most of my presentation would be fillen by Agile Architecture we need to implement a successful multi-language application

      Clearly, you cantranslate architecture parts but when it comes to MVC, you may not be able to use MVC parts


  • Liked Prasanna Vaste

    Prasanna Vaste - Should we stop using Story Points and Velocity?

    Prasanna Vaste
    Prasanna Vaste
    Business Analyst
    schedule 5 years ago
    Sold Out!
    20 Mins
    Experience Report

    On Agile projects we estimate user stories in order to allow team to

    1. 1. Track velocity
    2. 2. Decide scope for the Iteration
    3. 3. Help Prioritize stories
    4. 4. Help Release planning

    But most of the time we faced issues with estimation. It takes lot of time in estimating user stories, managers tend to relate estimate to number of days it will take to complete the story, in some teams estimate is equal to deadline. Most of the teams which use story points to estimate the work face these issues. This results in lack of confidence on development team when stories are taking more time to complete.

    Here I am going to talk about better alternative for both the suppliers of software products (financially and ethically) and their customers (internal and external). This alternative is being used in real companies delivering to real customers with great effect where team uses count of stories completed in an Iteration as measure of progress. Will talk about how this alternative can be used to track velocity, prioritize stories, planning Iteration and for release planning.

    I will share some exmples from my past projects where team did not use story points/velocty but used count of stories completed in Iteration to measure progress and also as best indicator of future performance.

  • Liked Allen Rutzen

    Allen Rutzen / Sunil Roy - Nokia Maps Agile Journey.....(Agile Transformation, Scaling and Overcoming Challenges)

    45 Mins

    We (at Nokia Maps Division) began our Agile Journey in 2009, with a Top Down approach for Agile Transformation. The formation of an Agile Working Group (with members having Agile experience behind them) at two major sites was instrumental in shaping the transformation and scaling and also overcoming the challenges from time to time.

    The challenges were huge, but our spirit was bigger, and the high level strategy was decided. Interestingly, the Agile Working Group itself ran the whole Transformation and Scaling program using Agile values and Scrum frame work. Scrum was also used as the preferred framework for the agile projects (after success in our pilots), except where Scrum would not work. Kanban or hybrid methods were used in those few teams.

    What were the challenges faced, and how did we overcome them? What values helped us in our transformation journey?

    How did we migrate to the Scaling phase? What helped us in scaling and stabilizing?

    Can we rest easy now? Of course not!

    What are the next steps? And of course, the challenges ahead?

    Let us share our Nokia Agile journey with you, and help you all be successful too, in your Agile journey!

  • Liked Pradeepa Narayanaswamy

    Pradeepa Narayanaswamy - Agile Testing- What is my success mantra??

    45 Mins

    As more and more organizations are transitioning to agile, it’s inevitable that Agile testing is not just a concept any more. It is also not just about placing a tester in every team. What is so radically different now? How to be successful at agile testing? How to be an effective cross-functional team that embeds and honors all specialties including testing?

    In this presentation, I am going to share my teams’ success with Agile testing and how we incorporated these 3 aspects – people, process and tools/techniques. This talk will benefit any members in an organization who has a stake in the product quality. It is also highly beneficial for those agile testers (from aspiring to veteran) to understand the 3 main aspects as it relates to testing and why we need to embrace- not just one, not two, but all these 3 aspects to be successful in Agile testing. 



  • Liked Ankush Sabharwal

    Ankush Sabharwal - Step-by-Step Process for Release Planning and Release Level Retrospectives

    45 Mins

    In the session two processes will be explained viz. Release Planning and the Release Level Retro. Step by Step approach will be discussed so that the same can be readily used in your Agile Projects.

    I have created these approaches of conducting effective Release Planning and Release Retrospectives in Agile projects. I have used these processes in various successful Agile projects.


    Note: Please refer to the Links section below to see the steps invoved in both of these processes.

  • 90 Mins

    Have you ever thought why scrum works? That too from NeuroScience perspective?
    We all acknowledge and understand that we have moved beyond and past machine age or service era and are living in what is called “Knowledge Era”. Focus of current times is shifting from behaviours to values. From people to brain. Yet, we know very little about people or brain or its working.
    Through this talk, I will attempt to link hard neuroscience to scrum and its practices to see why it works or does not work. Also we would look at practices required beyond scrum to create an environment where scrum can flourish. Or even exists!