Agile Internationalization User Stories

Transcription

1 Agile Internationalization User Stories Tex Texin Chief Globalization Architect XenCraft Internationalization and Unicode Conference IUC41

2 Abstract User stories are the way that Agile Methodology describes the functionality of the software being developed. Each story describes an action or need of a user and in so doing defines the functions the software must provide and the requirements it must satisfy. This session will describe the mapping of an internationalization checklist into a suite of user stories that are used in internationalizing a software project. Copyright 2017 Tex Texin. All rights reserved. 2

3 Who is here? -Have internationalization expertise -Have localization expertise -Have Agile expertise Copyright 2017 Tex Texin. All rights reserved. 3

4 Agenda -Introduction -Background -Premise -User Stories -Premise Discussion Copyright 2017 Tex Texin. All rights reserved. 4

5 Background -Experience with companies globalizing software, using Agile, both for the 1 st time - New to writing user stories - New to internationalization -Lots of rewriting - Struggle with wording - Struggle with Agile layering - Epic?, User Story? Confirmation? Technical spec? - Struggle with roles Copyright 2017 Tex Texin. All rights reserved. 5

6 Background continued -Organizations going global for the first time need new processes and staffing - For example, for localization -Writing stories in areas without experience or defined organization culture, can be difficult Copyright 2017 Tex Texin. All rights reserved. 6

7 Background continued -Internationalization Checklists - Many exist - Capture most requirements - Generalized to apply to most applications - With some intelligent selection, extension and customization - Consultants and senior I18n architects have advanced lists or tools for applying them Copyright 2017 Tex Texin. All rights reserved. 7

8 Internationalization Checklists -Example contents - Unicode enabling - Data formatting - Locale setting - String Externalization - Resource file management - Layout management - Etc. Copyright 2017 Tex Texin. All rights reserved. 8

9 Premise Create Software Globalization User Story Template - Most organizations can use it - Instructive to first timers - Replace i18n checklist with template - Easier to comprehend than checklists -Technical details put into acceptance criteria -Hierarchical (user stories drill down, and can be repeated and tracked across scrum teams) Extensible to other software requirements - Accessibility - Privacy - Security - Etc. Copyright 2017 Tex Texin. All rights reserved. 9

10 By the way -About me - I am not an Agile expert - I am not a proponent of Agile - Implementations of Agile Methodology vary in practice. Customize to your terms and practices - This is not about the value of using Agile or details of the methodology - This is about User Stories for Software Globalization Copyright 2017 Tex Texin. All rights reserved. 10

11 Structure of a User Story Role, Goal and Benefit

12 Structure of a User Story -It can vary but generally looks like: As <role>, I have a <goal>, to get a <benefit> -For example: - As an end-user, I want the User Interface in my native language, for a better user experience (reduced errors, more productivity, greater trust). Copyright 2017 Tex Texin. All rights reserved. 12

13 Acceptance Criteria User Stories are supplemented by acceptance criteria or Confirmations, so they are testable User Story As an End-User, I want calendars to respect my local customs, for a better user experience. Acceptance Criteria Can I switch to Gregorian, Buddhist, Japanese Emperor, Hijri, et al Calendars? Does first day of the week change with locale? Are month and day names localized? Are holiday lists localized? Are default work schedules localized? Copyright 2017 Tex Texin. All rights reserved. 13

14 User Story Templates -Agile developers often use templates for creating and tracking user stories User Role Goal Benefit Acceptance Criteria For the examples in this presentation, the benefit is self-evident, so I ll skip stating it. Acceptance criteria are also too detailed for this presentation. Copyright 2017 Tex Texin. All rights reserved. 14

15 User Story Adoption and Heat Maps -For large complex applications or development teams - User stories have sub-stories have sub-stories - User stories are allocated to/adopted by each scrum team as applicable - So lots of replication of user stories - And independently scheduled Copyright 2017 Tex Texin. All rights reserved. 15

16 A Globalization Agile Template

17 Abstracting Software Applications -We need to identify the roles and actions that typify applications -Roles - End-user - Client-facing (sales, customer service, etc.) - Operations (Admin, DB Admin, IT, Web, etc) - Stakeholders (Finance, Regulatory, Country, etc) - Require reports and compliance - Third Parties - (L10n, Phone Carriers, Pay Vendors, Sales Offices, ) - Platform/System (architecture requirements, SLA) Copyright 2017 Tex Texin. All rights reserved. 17

18 Communications/Interface -Anonymous vs. Known (logged in) -Interface types - Web - Client-Server - Mobile - Social Media - - Text/SMS - Voice -Users can be distinguished by their UI -Platform actions vary with the interface Copyright 2017 Tex Texin. All rights reserved. 18

19 As a User, I want - the UI Theme to reflect my local culture and customs (images, media, sounds, symbolism, colors, fonts, etc.) - the application to render in my native language - to enter text in my native language - calendars to respect my local customs - formatting, days of the week, holidays, work schedule, etc. - dates and times formatted to my native customs, in my time zone - numbers formatted to my native customs - prices in my currency, formatted to my native customs - to enter postal addresses according to my native customs - to enter titles and names according to my native customs - my local phone number to be supported - to choose my globalization settings - the application to remember my globalization settings - different globalization settings on my mobile device(s) Copyright 2017 Tex Texin. All rights reserved. 19

20 As a User, I want - to identify myself to the application using values and techniques that reflect my local customs - login, security questions, identifiers, passwords, CAPTCHA,etc. - sorted text data to use my native language collation - to use page size, measurement systems I am familiar with - syntax and other validations to be specific to my market - fuzzy search (case-insensitive, accent-insensitive, etc) to reflect my native language - to respect my globalization preferences - SMS messages to respect my globalization preferences - to use social media popular in my market, in my native language - to have good response times in my country - customer service, problem reporting and responses in my native language - application to be usable when I travel and need different settings Copyright 2017 Tex Texin. All rights reserved. 20

21 As an Admin, I want to -Configure the supported languages -Configure the default globalization settings for each market -Configure business rules for each country -Configure reports for each in-market stakeholder -Configure government and compliance reports for each government or agency -Update/Maintain System Data Copyright 2017 Tex Texin. All rights reserved. 21

22 As a Platform/Application/Service I want - best practices for I18n defined and standardized across the organization - to detect an anonymous user's locale - a method for an anonymous user to change their locale - all text represented by Unicode - all data to be represented by locale-independent formats, using native data types or tokenized values - all localizable content to be external to code - to respect the user's globalization settings - to respect the product configuration settings - rendering services to support native languages and customs - for input services to be capable of accepting native language and customs - for text parsing, sorting and search operations to use appropriate linguistic behaviors and collations as needed. - to accept, render, manage and support international domain names and URLs - for business rules to support market customs and be configurable - to use a pseudo-locale to evaluate capabilities prior to actual localization - to configure and support third parties by language and/or country Copyright 2017 Tex Texin. All rights reserved. 22

23 As a Localization Manager, I want - to have a process for acquiring localizable content from the platform - to have a process for localizing content - to have a process for merging localized content with the platform - to have a process for verifying the build of the localized content. - to have a process for linguistic testing the localized build - to have a process for forecasting, budgeting, and scheduling localization activities, in coordination with engineering - to have a localization engineer verify localization file formats, create utilities for minor conversions, repairs, and other technical activities - a process for reporting and tracking localization bugs - a process, repository and tools for managing localization content and workflow - a process and tools for managing glossaries - a process and tools for managing translation memory - a process for selecting and reviewing localization vendors Copyright 2017 Tex Texin. All rights reserved. 23

24 As a Customer Service Agent or Manager, I want - to view user's settings and history in my language - to view user's settings and history in the user's language - to look for patterns of failure by market or by language or across markets and languages - to send messages, notifications, reports to users in their language - to edit users settings etc. including their globalization preferences - user calls, s, etc routed (automatically) to agents that speak their language Copyright 2017 Tex Texin. All rights reserved. 24

25 As (one of many) stakeholders, I want -compliance with privacy laws -compliance with financial regulations -compliance with accessibility regulations -compliance with security policies -user agreements localized and reviewed by legal and other personnel -Monitoring of system performance -Product reporting by market -Etc. Copyright 2017 Tex Texin. All rights reserved. 25

26 Careful to not over-generalize -Interfaces, 3 rd parties, regulations, vary with country - So you may need to create multiple projects with different stakeholders and (some) distinct user stories -Expect to customize to your product and organizational requirements and terminology - E.g. User vs Client vs Customer, etc. Copyright 2017 Tex Texin. All rights reserved. 26

27 Premise Create Software Globalization User Story Template - Most organizations can use it - Instructive to first timers - Replace i18n checklist with template - Easier to comprehend than checklists -Technical details put into acceptance criteria -Hierarchical (user stories drill down, and can be repeated and tracked across scrum teams) Extensible to other software requirements - Accessibility - Privacy - Security - Etc. Copyright 2017 Tex Texin. All rights reserved. 27

28 Proposal A Globalization Agile Template seems like a valuable commodity for most organizations using Agile. It is instructive for other organizations as well. An alternative to checklists. Would you want one? Copyright 2017 Tex Texin. All rights reserved. 28

29 Questions? Copyright 2017 Tex Texin. All rights reserved. 29

30 Tex Texin Tex is an industry thought leader specializing in business and software globalization services. His expertise includes global product strategy, Unicode and internationalization architecture, and cost-effective implementation and testing. Over the past two decades, Tex has created numerous global products, led internationalization development teams, and guided companies in taking business to new regional markets. Tex is a contributor to internationalization standards for software and on the Web. Tex is a popular speaker at conferences around the world and provides on-site training on Unicode, internationalization, and globalization QA worldwide. Tex is the author of the popular, instructional web site Tex is founder and Chief Globalization Architect for XenCraft. XenCraft provides global business consulting and software design, implementation, test and training services on globalization product strategy and software internationalization architecture. Copyright 2017 Tex Texin. All rights reserved. XenCraft, TexTexin and I18nGuy are Trademarks of Tex Texin.