International Game Developers Association
Back to Credits Main Page PDF Version 8.5
The following recommendations are meant to aid the implementation of a company approach to formalized crediting for each game project.
Table of contents
- 1 METH.1 – Establish Approach: At the start of each project, the team, a representative subset of the team, or the management of the team must establish the crediting approach and rules to be used (e.g., adopting the rules set forth in this Guide, and resolving applicable or pertinent issues presented in this Guide).
- 2 METH.2 – Final Review: Team members should be given a chance to review their final credit before the game is finalized.
- 3 METH.3 – The team should establish a cap on multiple credits. Along with management, the team should establish written eligibility rules for multiple credits. Eligibility rules may disqualify contributions of lesser proportion or magnitude.
- 4 METH.4 – [Optional] Regular Review: It is recommended that the credit records be reviewed by the team upon completion of major project milestones. Records should be updated to reflect only cumulatively significant role changes and additions.
- 5 METH.5 – [Optional] Designated Credits Keeper: It is recommended that a team member be appointed to keep and maintain the credit records, including the change logs, from the start of a project. A producer or manager is usually the most appropriate person.
- 6 METH.6 – [Optional] Accessible Credit Records: It is recommended that credit records and change logs be accessible to all team members in a place that does not require a request to obtain the information, such as a .txt file on a local server, or a wiki page.
|
[edit] METH.1 – Establish Approach: At the start of each project, the team, a representative subset of the team, or the management of the team must establish the crediting approach and rules to be used (e.g., adopting the rules set forth in this Guide, and resolving applicable or pertinent issues presented in this Guide).
[edit] METH.2 – Final Review: Team members should be given a chance to review their final credit before the game is finalized.
1. On-site team members should be shown their proposed credits and have at least a two week period to voice concerns or suggest corrections to management before the credits are finalized.
2. All reasonable effort should be used to inform departing or terminated team members of the credit they will receive as a standard part of the process of departure.
3. All reasonable effort should be used to inform contract and similar off-site contributors of the credit they will receive at the time services are rendered.
4. [Optional] A sign-off sheet could be circulated among the on-site team as a record of this process.
[edit] METH.3 – The team should establish a cap on multiple credits. Along with management, the team should establish written eligibility rules for multiple credits. Eligibility rules may disqualify contributions of lesser proportion or magnitude.
[edit] METH.4 – [Optional] Regular Review: It is recommended that the credit records be reviewed by the team upon completion of major project milestones. Records should be updated to reflect only cumulatively significant role changes and additions.
[edit] METH.5 – [Optional] Designated Credits Keeper: It is recommended that a team member be appointed to keep and maintain the credit records, including the change logs, from the start of a project. A producer or manager is usually the most appropriate person.
[edit] METH.6 – [Optional] Accessible Credit Records: It is recommended that credit records and change logs be accessible to all team members in a place that does not require a request to obtain the information, such as a .txt file on a local server, or a wiki page.
Take a Survey
Back to Main Page
