Code of Conduct for Scrum Guide Expansion Pack Translations - ScrumGuides/ScrumGuide-ExpansionPack GitHub Wiki
Translators of the Scrum Guide Expansion Pack and its associated materials do our community an invaluable service and are greatly appreciated. The Code of Conduct for Scrum Guide Expansion Pack Translation-Guide outlines expectations and standards to ensure that translation work is of the highest quality and serves the best interests of the communities served by the Scrum Guide Expansion Pack.
Translators must agree to this code of conduct before translating, re-translating, or continuing to translate any written materials associated with the Scrum Guide Expansion Pack.
Suggestions to improve this code of conduct can be submitted using discussions at https://scrumexpansion.org.
1. Glossary
Translation refers to any translated document from the official website(s) publishing the Scrum Guide Expansion Pack, currently the Scrum Guide Expansion Pack website https://scrumexpansion.org.
A translation guardian is one or more individuals responsible for ensuring the quality of Translation-Guide, maintaining consistency, and ensuring coherence with this Translation Code of Conduct document for the Scrum Guide Expansion Pack.
A translator is a person who facilitates, creates, amends, or reviews the translation(s) of documents on the official website(s) for accessing the Scrum Guide Expansion Pack, currently located at https://scrumexpansion.org.
The administrators of the official website(s) for accessing the Scrum Guide Expansion Pack, currently the Scrum Guide Expansion Pack website https://scrumexpansion.org, act as the translation guardian.
2. General Rules
- The community owns the Translation-Guide, not the groups or individuals who perform the translation(s). Therefore, other groups or individuals can take over the translation(s) for subsequent updates without requesting permission from the previous translators, provided they obtain written permission from the translation guardian.
- The translator must verify that the translation appears as expected in HTML, Markdown, and PDF formats. For images, the translator should use the Scalable Vector Graphics (SVG) format if applicable.
- Translators are expected to follow the written GitHub processes on the Scrum Guide Expansion Pack website.
- The translation guardian or delegate will publish Translation-Guide in both markdown/HTML and high-quality PDF formats for electronic distribution (so that hyperlinks work).
- The translation should render no material changes to content (such as changes in meaning, emphasis, or inattention to nuance); this includes the acknowledgment section.
- A translation can be presented in side-by-side paragraph format (to enhance reader trust), fully translated, or both (in a single document). If both side-by-side and full Translation-Guide are in the same document, the side-by-side translation must appear first.
- Copyright information and creative commons collection or license information in the original document must not be altered and, therefore, should not be translated.
- The translation must include a Translator Acknowledgement section and a Change Log, as specified in Section 6 of this Code of Conduct. The Translator Acknowledgement section must include details for the current translation version and should consist of previous translator groups, subject to their permission.
- The translation guardian reserves the right to remove acknowledgments or Translation-Guide should they determine that the group of translators, or individuals therein, bring the Scrum Guide Expansion Pack into disrepute.
- During translation, reviewers should submit all feedback through constructive and respectful comments to help ensure that it is not ignored or diminished. Alternatively, reviewers can provide audio or video feedback.
- Translators, like everyone else, are welcome to suggest a change(s) to the Scrum Guide Expansion Pack by following the GitHub process on scrumexpansion.org.
- One translation per language is preferred. There are some acceptable exceptions due to regional differences.
- A translator who, in the eyes of the translation guardian, demonstrates a breach of the Scrum Values or the three pillars for Scrum Empirical Process Control as described in the Scrum Guide Expansion Pack will receive a private written warning from the translation guardian.
- A translator who, in the eyes of the translation guardian, for the 2nd or 3rd time, demonstrates a breach of the Scrum Values or the three pillars for Scrum Empirical Process Control as described in the Scrum Guide Expansion Pack, will receive a public written warning from the translation guardian. There is no appeals process.
- The translation guardian reserves the right to remove translators who, in the eyes of the translation guardian, demonstrate four times (or more) a breach of the Scrum Values or the three pillars for Scrum Empirical Process Control as described in the Scrum Guide Expansion Pack. There is no appeals process.
3. Responsibilities of Translation Guardian
- Notify the translator of any updates to the Scrum Guide Expansion Pack within two business weeks of publication. Translation-Guide will go live after the source document has been updated, not beforehand.
- Monitor the consistency of Translation-Guide.
- Withdrawal of Translation-Guide that do a disservice to the communities served by the Scrum Guide Expansion Pack.
- Monitor that translators are abiding by this code of conduct.
- Approve the beginning of Translation-Guide.
- Approve the publication of Translation-Guide.
- Publish HTML/Markdown and PDF versions of the approved Translation-Guide.
- Resolve queries from translators within four business weeks.
- Address breaches of the Scrum Values and the three pillars of Scrum’s empirical process control in a timely manner.
4. Responsibilities of Translators
- Follow the written GitHub process at scrumexpansion.org for all translation work.
2. It is forbidden to add translator names to the original list of acknowledgments.
3. It is forbidden to add to or modify the original Creative Commons licence/attribution.
4. Provide the details below in a Translator Acknowledgement section regarding translators and reviewers whose feedback affected the published translation, subject to the consent of each named person. No feedback, no mention, permission or not.
| (optional) Translator Name(s) : | |
|---|---|
| (optional) Translation Group Name : | |
| (optional) Primary Contact Email : | |
| (optional) Website : | |
| (optional) Social media handles: |
- It is permitted to use AI as an aid to translation, but the final translation must have been reviewed and corrected by at least five human reviewers whose mother tongue is the language of the translation.
- Provide written/audio/video responses from a minimum of five translation reviewers whose first language is the same as the language of translation. Ideally, three reviewers will have Scrum knowledge, and two will not.
- All reviews and responses for reviews should be in line with the Scrum Values and the three pillars of Scrum’s empirical process control, as described in the Scrum Guide Expansion Pack.
- Complete the translation within a reasonable timeframe as agreed upon with the translation guardian.
- Advise the translation guardian as soon as possible if unable to complete or maintain the translated document.
- Respond to requests for needed changes (e.g., translation errors) in a reasonable amount of time as negotiated with the translation guardian.
- The translator may not exchange a translation related to the Scrum Guide Expansion Pack for monetary gain.
- The translation group name, social media handles, and email addresses must not bring the Scrum Guide Expansion Pack into disrepute, as decided by the translation guardian.
5. Reserved Words
Some terms are challenging to translate into other languages, yet readers must understand them.
Given the above, translation is allowed for any instance of the terms below. The American English term must appear in parentheses following the first instance of each translated term. Subsequently, the term may appear in the translated language. The translator may use the American English term throughout if that is the best option.
If the translation of a reserved word/expression is awkward in the translated language, the translator should consult with the translation guardian. Including a glossary at the end of a translated document might be beneficial to readers.
For example, AI translation in French (France):
Pour une adoption plus réussie, ce Pack d’Extension (the Expansion Pack) propose des recommandations supplémentaires adaptées à l’époque actuelle, basées sur le Scrum Guide 2020 de Ken Schwaber et Jeff Sutherland.
The references section must not be translated; video, article, paper, and book titles are as they are.
For example:
Stripe (2025) ‘Sir Jony Ive and Patrick Collison Fireside Chat | Stripe Sessions 2025’, YouTube video, 8 May. Available at: https://youtu.be/wLb9g\_8r-mE?si=1rEJxU0sxixvblQ3\&t=1390 (Accessed: 8 June 2025)
| Scrum Guide Terms | Expansion Pack Terms | Expansion Pack Terms | ||
|---|---|---|---|---|
| Scrum | Scrum Guide Expansion Pack | Cynefin | ||
| Scrum Values | Leader | strategy | ||
| Three Pillars | Stakeholder | Strategy -Deployment-Guide | ||
| Sprint Planning | Supporter | descaling | ||
| Daily Scrum | Acceptance Criteria | Product Operating Model | ||
| Sprint Review | Outcome Criteria | goal-oriented | ||
| Sprint Retrospective | Definition of Output Done | de-scaling | ||
| Scrum Team | Definition of Outcome Done | Adaptive enterprise | ||
| Scrum Master | Product Backlog Item | Adaptive executive or board member | ||
| Product Owner | Value | Humanocracy | ||
| Developer | Outcome | Sociocracy | ||
| Product Backlog | Empirical Process Control | Intent-Based Leadership | ||
| Sprint Backlog | Empiricism | Immunity to Change | ||
| Increment | Scrum’s Three Pillars of Empirical Process Control | Beyond Budgeting | ||
| Focus | Lean | First Principles Thinking | ||
| Openness | Systems Thinking | People and Change | ||
| Courage | Product Thinking | Scrum Expansion | ||
| Commitment | Discovery | Scrum Expanded | ||
| Respect | Value validation | data-informed ** | ||
| Transparency | Values realization | Leadership | ||
| Inspection | Multi-Scrum-Team | theory-informed ** | ||
| Adaptation | adaptiveness | evidence-informed ** | ||
| Product Goal | effective ** | informed ** | ||
| Sprint Goal | emergence ** | Expansion Pack | ||
| Definition of Done | probe ** | |||
| Accountability | safe-to-fail ** | |||
| accountable | Product | |||
| risk ** | ||||
| expectations ** | ||||
| limits ** | ||||
| complex ** | ||||
| complexity | ||||
| scaling | ||||
| Role | ||||
| Self-managing Scrum Team | ||||
| Professionalism | ||||
| Cadence | ||||
** Not a reserved word, but due care and attention.
6. Data protection
Scrum Guide Expansion Pack is committed to protecting individual privacy and personal data and expects the same from those providing translation services.
Distribution of names, email addresses, or other personal information acquired during translation without written permission from the person(s) affected is prohibited. Any potential data leak must be reported to the translation guardian immediately, along with a remediation plan.
The translator and the translation guardian must cooperate and assist each other in complying with all laws and regulations regarding the protection of personal data and privacy.
7. Termination
Translators can terminate their service at any time. The translation guardian will continue to manage any completed or in-progress Translation-Guide.
The translation guardian may choose to terminate a translator if they determine the translator has violated this translation code of conduct.
The translation guardian must notify the translator(s) of discontinued service in writing at the time of termination.
8. Change history
A change history log must appear on the last page of a translation, documenting the changes from one version to the next. For example:
| Version number | Significance | Version date (long date format) |
|---|---|---|
| 1.0 | Original translation | 18th June 2025 |
Version History of Code of Conduct for Scrum Guide Expansion Pack Translators
| Version number | Significance | Version date (long date format) |
|---|---|---|
| 1.0 | Original publication | 18th June 2025 |
| 1.1 | Additional condition for behavior | 20th June 2025 |