Working in a team of three students, you will analyse the strengths, weaknesses, opportunities, and threats (SWOT) of your three individual prototype games from MMST12017 Game Design. After the SWOT analysis, you will choose one prototype to further develop in the first half of Term 2. Working collaboratively, and in your assigned role(s) you will help your team complete, playtest and deploy an advanced version (i.e. extended and refined) of the selected game prototype game to Itch.io and develop supporting documentation in accordance with the task criteria. Finally, you will pitch the your prototype game to your classmates during 'Crunch Week' in the week 5 Zoom session, with the goal of having it selected for further development after the mid-term break.

The first assignment consists of four assessment tasks which are worth 30% of the overall grade for DGTL13007:

1. Task 1A - Draft Game Design Document (GDD) & supporting Gantt Chart - 12 marks
2. Task 1B - Informal pitch of advanced (i.e. extended & refined) prototype game (to be delivered in Week 5 Zoom session) - 8 marks
3. Task 1C - Team development blog (Weeks 2-4) - 5 marks
4. Task 1D - Self & Peer Assessment - 5 marks

Task 1A: Game Design Document (GDD) & Gantt Chart

Your team will create and submit a preliminary (draft) GDD and accompanying Gantt Chart. This will lay the foundation for your team's game development during weeks 1-5 of Term 2.

What is a GDD?

The GDD is a crucial document for game designers, often called the 'bible' of the project. It is continuously referred to and shaped by the designer's interactions with the development team throughout the project's lifespan. As part of the Game Development Life Cycle (GDLC), the GDD is a living document that undergoes regular updates.

Creating a GDD doesn't follow a single prescribed method. Game design teams can choose a format based on preference or company guidelines. Regardless of the structure, the purpose remains the same - to effectively communicate the game designer's vision for the game, including its mechanics, dynamics, and aesthetics. The information in the GDD should be organised into clear sections that are easy to understand yet provide enough detail for the entire team, including artists, programmers, and team leaders, to collaborate effectively.

"In broad terms, the purpose of documentation is to communicate the vision in sufficient detail to implement it. It removes the awkwardness of programmers, designers and artists coming to the producers and designers and asking what they should be doing. It keeps them from programming or animating in a box, with no knowledge of how or if their work is applicable or integrates with the work of others. Thus, it reduces wasted efforts and confusion." - Ryan 1999

Resources:

1. Resource 1 - Google Drive GDD Template (editable)

• Download the GDD template that I've created (link below) and use the template guide in the 'Assessment' area of the unit website (Moodle) to help you populate it.
• Upload the document to your personal Google Docs workspace. This will allow you to collaborate on the document with others in a cloud-based environment.
• Feel free to customise the visual appearance of the GDD template according to your preferences. You are encouraged to make it look and feel the way you want.Once you have uploaded the document, you can edit it at any time and from anywhere. You can share the link with your tutor or me to receive feedback on your GDD as it progresses.
• Link: Editable GDD template (Google Drive)

2. Resource 2 - Student Exemplar GDDs

• Within the ‘Assessment’ section of the unit website you will find examples of student GDDs.
• The exemplar GDDs from previous years may have a different format, structure, and methodology compared to this year's requirements. However, they serve as an indication of the level of quality needed to achieve a high grade.
• Link: Student exemplar GDDs (located on the unit website)

3. Resource 3 - Game Design Dashboard with Gantt Chart - Template (editable)

• Gantt Charts are project management tools used to ensure timely completion of milestones and key deliverables. By using a Gantt Chart in conjunction with your GDD, you can provide visibility to team members and stakeholders on the project's progress, allowing them to identify and address issues and risks promptly.

• Please download the DGTL13007 Game Development Dashboard (link below, and on the unit website), which includes a customizable Gantt Chart. You can adjust the Gantt Chart to match your team's proposed development timeline.

• Alternatively, you can create your own Gantt Chart, but it must be included in your GDD or accessible through a link if it's cloud-based.

• Link: MMST13007 Game Development Dashboard Tool (Google Drive)

Task 1B: Informal pitch of advanced (i.e. extended & refined) prototype game (to be delivered in Week 5 Zoom session)

In the Week 5 Zoom session, student teams will present their advanced digital game prototype (i.e. extended & refined) to their peers. The pitch should not only demonstrate the strengths of the game for continued development, but also demonstrate the capabilities of the individual students and team with respect to skills & knowledge in fundamental game design & development. These prototypes will undergo evaluation through voting by students and staff. The purpose of this evaluation, referred to as 'Crunch Week', is to narrow down the number of prototype games under development. Students whose prototypes are not selected will be reassigned to larger teams starting from Week 6. In these teams, they will be given specific roles and responsibilities. The objective is to have around 6 students in each team, collaborating to develop a more refined and higher-quality prototype for Assignment 3.

Consider the following points when preparing your game pitch:

1. The main goal of the pitch is to convince your classmates and staff that your game prototype is suitable for further development, whilst highlighting the work and capabilities of individuals and the team.
2. The secondary goal is to attract new team members from your class for your game prototype. Clearly explain the skills you are looking for and the roles you need to fill.
3. The pitch should accurately represent your game at its current stage. Keep it concise and effectively highlight the opportunities, strengths, and weaknesses of the game prototype and your team.
4. Make your game pitch engaging, interesting, and informative, while maintaining an informal tone suitable for presenting to your peers, rather than a business audience.
5. Show an understanding of your game's target audience in your pitch.
6. Demonstrate your game prototype in action, even if it's not fully complete. Supporting resources like concept art, game world, or character designs can be used to enhance the pitch.
7. It's important to be realistic in the content and avoid any exaggerations regarding functionality or progress.
8. Be prepared to answer questions from your tutor and classmates after your pitch.

Considerations:

Please keep in mind the following when planning your pitch:

• Ensure that all team members contribute to the extension and refinement of the MMST12017 prototype that you have selected. Your aim is to deliver a more advanced version of the prototype for consideration in your pitch.
• The pitch will be presented during the week 5 Zoom session.
• Ensure that all team members contribute to the pitch. It is preferable if each team member presents a portion of the pitch.
• Depending on your team members availability, the pitch may be presented live in the Zoom session or using a combination of live and pre-recorded elements.
• The pitch should not exceed 5 minutes.
• The pitch will demonstrate the functionality of your game.
• Ensure you consider the target audience (classmates) who may potentially join your team in development roles starting from week 6.
• Remember that the overall goal is to secure a positive vote to continue the development of your game prototype with a larger team from week 6 onwards.

Examples:

• Previous game development student team playlist (YouTube)
• Additional student samples will be made available via the DGTL13007 website

Task 1C: Game Development Blog (Week 2-4)

As part of the assessment, your team will maintain a weekly Moodle blog during weeks 2-4, addressing predefined topics. Additionally, you are required to provide a minimum of two meaningful comments on blog posts belonging to other teams.

Weekly Blog Topics:

During weeks 2-4 you will briefly address the following topics, in addition to listing (dot points) what each member of the team has been working on:

• Week 2 - Critically reflect on your SWOT Analysis i.e. the process of selecting the game design for your team to focus on (i.e. what shaped your thinking; did you agree; how did you negotiate?)
• Week 3 - Critically reflect on your approach for providing shared (and reliable) access to the team's game project files, and ensuring regular backups are made i.e. are you using Github, Cloud-based storage (Google Drive), or some other technique?

• Week 4 - Critically reflect on your role in the development of the game prototype (i.e. explain how each member contributed)

Considerations:

• Only one blog post is required per team, per topic, so not all team members have to contribute individually. Instead, create a single post as a team to address the designated topic.
• Use the Moodle Blog Tool provided in the DGTL13007 'Assessment block'.
• Create one weekly blog post reflecting on your involvement in the team game development process.
• Read and provide meaningful responses to at least two blog posts from other teams.
• Blog posts can be in written, video, or audio format.
• No minimum word length, but posts should be substantial and meaningful.
• Ensure you tag your post with your team name.
• Submit blog posts weekly for full marks.
• Blog posts submitted after the designated due date will not be scored.

Task 1D: Self & Peer Assessment

To evaluate the team's performance and assess individual members, all students will complete a self and peer assessment form using a supplied template. This unit aims to foster important employment attributes such as collaborative and cohesive work, as well as taking responsibility for individual roles and deadlines. Teamwork is not without challenges, but it is authentic and mirrors the demands of the modern digital workforce.

• The assessment tasks revolve around a team of three (3) students extending and enhancing a previously developed digital prototype game from MMST12017 Game Design. These tasks should be completed together with your team, with equal contributions from all members.
• You are allowed to use Third Party components or frameworks from the Unity Asset Store, Public Domain, or Creative Commons as long as they only form a portion of the overall solution and are properly referenced. If you're unsure, it is best to check with the Unit Coordinator.
• Artificial Intelligence (AI) engines can be utilised in your workflow (refer to GenAI statement below) but must be treated as an additional/virtual team member. If you incorporate AI, make sure to explain its usage in your submission.
• Avoid using someone else's Intellectual Property (IP) in your work, such as ideas from Star Wars or other popular culture franchises.
• Higher marks will be awarded for demonstrating successful experimentation and innovation.
• Late submissions or failure to comply with assessment requirements may result in penalties.
• For more detailed assessment criteria, please refer to the DGTL13007 website.

Use of Generative Artificial Intelligence agents (Gen AI)
Within this assessment, the use of Microsoft Copilot, Chat GPT or other Gen AI agents is as follows:

• Gen AI may only be used as specified in the assignment instructions in Moodle.
• Gen AI content can be used to generate concepts, ideas and general structures.
• GenAI can be used to assist with creating C# code for Unity.
• Gen AI can be used for proofreading.
• Gen AI cannot be used to create media assets (art, sound, animation etc) for your collaborative game. 
• If you are unsure, ask the Unit Coordinator.

Working in collaboration as part of a larger team (5/6 students) post 'Crunch Week', you will contribute to the following three (3) assessment tasks which are worth 30% of the overall grade for DGTL13007:

1. Task 2A - Revised Game Design Document (GDD) & Gantt Chart - 20 marks
2. Task 2B - Development Blog (Weeks 6-8) - 5 marks
3. Task 2C - Self & Peer Assessment - 5 marks

Task 2A: Revised Game Design Document (GDD) & Gantt Chart

Your team will develop and deliver a complete and accurate Game Design Document (GDD) and supporting Gantt Chart that provides a clear roadmap for your proposed game development process during weeks 6-12 of Term 2. You do NOT need to create a new GDD, rather you will update and extend the initial GDD that was developed to support the chosen game prototype for Assignment 1. Allocate sections of the GDD against the roles and responsibilities of the student team members. For the remainder of the term, the GDD must be regularly maintained and map out team development (this will be reviewed in Assignment 3). Update the Gantt Chart to ACCURATELY reflect team progress with respect to milestones and deliverables.

Task 2B: Game Development Blog (Week 6-8)

As part of the assessment, your team will maintain a weekly Moodle blog during weeks 6-8, addressing predefined topics. Additionally, you are required to provide a minimum of two meaningful comments on blog posts belonging to other teams.

Weekly Blog Topics:

During weeks 6-8 you will briefly respond to the following topics, in addition to listing (dot points) what each member of the team has been working on:

• Week 6 - Define the roles and responsibilities of team members in the new group
• Week 7 - Has any conflict arisen within your team? If so, how did you deal with this? If not, reflect on how your team would deal with conflict.
• Week 8 - Define the expected deliverables from team members, and comment on whether these are running to schedule, or are falling behind.

Considerations:

• Only one blog post is required per team, per topic, so not all team members have to contribute individually. Instead, create a single post as a team to address the designated topic.
• Use the Moodle Blog Tool provided in the DGTL13007 'Assessment block'.
• Create one weekly blog post reflecting on your involvement in the team game development process.
• Read and provide meaningful responses to at least two blog posts from other teams.
• Blog posts can be in written, video, or audio format.
• No minimum word length, but posts should be substantial and meaningful.
• Ensure you tag your post with your team name.
• Submit blog posts weekly for full marks.
• Blog posts submitted after the designated due date will not be scored.

Task 2C: Self & Peer Assessment

To evaluate the team's performance and assess individual members, all students will complete a self and peer assessment form using a supplied template. This unit aims to foster important employment attributes such as collaborative and cohesive work, as well as taking responsibility for individual roles and deadlines. Teamwork is not without challenges, but it is authentic and mirrors the demands of the modern digital workforce.

• The assessment tasks revolve around a team of 5/6 students extending and enhancing a previously developed digital prototype game from MMST12017 Game Design. These tasks should be completed together with your team, with equal contributions from all members.
• You are allowed to use Third Party components or frameworks from the Unity Asset Store, Public Domain, or Creative Commons as long as they only form a portion of the overall solution and are properly referenced. Bare in mind that you are working as part of a large team, so there is an expectation that as many of the required resources as possible will be created by team members. If you're unsure, it's best to check with the Unit Coordinator.
• Artificial Intelligence (AI) engines can be utilised in your workflow (refer to GenAI statement below) but must be treated as an additional (virtual) team member. If you incorporate AI, make sure to explain its usage in your submission.
• Avoid using someone else's Intellectual Property (IP) in your work, such as ideas from Star Wars or other popular culture franchises.
• Higher marks will be awarded for demonstrating successful experimentation and innovation.
• Late submissions or failure to comply with assessment requirements may result in penalties.
• For more detailed assessment criteria, please refer to the DGTL13007 website.

Use of Generative Artificial Intelligence agents (Gen AI)

Within this assessment, the use of Microsoft Copilot, Chat GPT or other Gen AI agents is as follows:

• Gen AI may only be used as specified in the assignment instructions in Moodle.
• Gen AI content can be used to generate concepts, ideas and general structures.
• GenAI can be used to assist with creating C# code for Unity.
• Gen AI can be used for proofreading.
• Gen AI cannot be used to create media assets (art, sound, animation etc) for your collaborative game. 
• If you are unsure, ask the Unit Coordinator.

Working in collaboration as part of a larger team (5/6 students) you will contribute to the final four (4) assessment tasks which are worth 40% of the overall grade for DGTL13007:

1. Published Game & GDD (finalised) - 19 marks
2. Marketing Strategy & Social Media Page - 10 marks
3. Development Blog (Weeks 9-12) - 6 marks
4. Self & Peer Assessment - 5 marks

Task 3A: Published Game & GDD (finalised)

Working collaboratively, and in your assigned role(s), you will collaboratively help your team complete, playtest and deploy your published game to the Itch.io online game publishing portal so that it is accessible for public feedback. Additionally, you will supply the final version of your GDD which should reflect the final stage of development.

• Completed game must be fully functional, play-tested and delivered as a well-polished advanced prototype that demonstrates the input of all team members.
• Game must be published to a WebGL / HTML-compliant format for online hosting.
• Game must be uploaded to Itch.io and must be open to the public for comment.
• Full source-code and project files must be uploaded as a ZIP file through the assignment submission page (or via a link to Google Drive / Dropbox) and made available through your team's online project sharing / collaboration tool.

Task 3B: Marketing Strategy (Max 1000 words) & Social Media Page

Don't let your amazing game go unnoticed! It's time to unleash your marketing strategy. Team members will be assigned to create a marketing strategy document (maximum 1000 words) along with a dedicated social media page(s) to promote your game's development.

Describe your team's proposed strategy by addressing the following points:

• Who is your target audience, and how will you target them?
• Does your game have a niche?
• Who are your competitors? Why?
• What channels will you use to spread your message? Why?
• What evidence have you found to support this approach?
• How will you use your game/team social media page(s)? Why?

Constraints:

• Team Marketing Strategy is to be delivered as a professionally presented Microsoft Word document labelled Team_MarketingStrategy.doc (insert your team name where it says 'Team').
• Document is to be no more than 1000 words.
• The marketing strategy will demonstrate research and be supported by evidence. This is not an opinion piece, so ensure that include some quality references to support your decisions. 
• References are to follow guidelines provided in the APA 7th Edition Referencing Guide. 
• Link to your game/team's social media page(s) MUST be included within your team marketing document.
• The team social media page(s) will demonstrate active, regular and carefully considered content designed to promote audience engagement.
• The team social media page(s) MUST be open to public feedback. You are are encouraged to engage with your audience for the purpose of collecting playtesting feedback.
• Once the game has been successfully published to Itch.io for playtesting, and final delivery, the social media page(s) must be hyperlinked to the live game on Itch.io.

Task 3C: Game Development Blog (Week 9-12)

As part of the assessment, your team will maintain a weekly Moodle blog during weeks 9-12, addressing predefined topics. Additionally, you are required to provide a minimum of two meaningful comments on blog posts belonging to other teams.

Constraints:

• Only one blog post is required per team, per topic, so not all team members have to contribute individually. Instead, create a single post as a team to address the designated topic.
• Use the Moodle Blog Tool provided in the DGTL13007 'Assessment block'.
• Create one weekly blog post reflecting on your involvement in the team game development process.
• Read and provide meaningful responses to at least two blog posts from other teams.
• Blog posts can be in written, video, or audio format.
• No minimum word length, but posts should be substantial and meaningful.
• Ensure you tag your post with your team name.
• Submit blog posts weekly for full marks.
• Blog posts submitted after the designated due date will not be scored.

Weekly Blog Topics:

During weeks 9-12 you will respond to the following blog topics, in addition to listing (dot points) what each member of the team has been working on:

• Week 9 - Free choice
• Week 10 - If you were to adapt your prototype game for mobile devices, what changes would need to be made? 
• Week 11 - Critically reflect on the deployment of your team game (i.e. alpha/beta testing; how did you apply audience feedback; publishing)
• Week 12 – Critically reflect on challenges or problems that have arisen, and how your team overcame them

Free-choice Blog suggestions:

• Relevance of your weekly tasks to game design theory
• Things that have inspired or motivated you (e.g. games, movies, books, TV, ideas)
• Challenges that you have encountered (i.e. which areas have proved the most difficult?)
• Research & development (i.e. what have you done to expand your knowledge of game development?)
• Examples of content that you are producing in support of the game
• Team dynamics
• Game development progress
• Have you received any public feedback? Has it been supportive, or have comments relating to bugs or potential features/improvements been given?
• Are you going to push the development of your game further in the future? If so, how?

You are not bound by these topics and can use one of your own!

Task 3D: Self & Peer Assessment

To evaluate the team's performance and assess individual members, all students will complete a self and peer assessment form using a supplied template. This unit aims to foster important employment attributes such as collaborative and cohesive work, as well as taking responsibility for individual roles and deadlines. Teamwork is not without challenges, but it is authentic and mirrors the demands of the modern digital workforce.

• The assessment tasks revolve around a team of 5/6 students extending and enhancing a previously developed digital prototype game from MMST12017 Game Design. These tasks should be completed together with your team, with equal contributions from all members.
• You are allowed to use Third Party components or frameworks from the Unity Asset Store, Public Domain, or Creative Commons as long as they only form a portion of the overall solution and are properly referenced. Bare in mind that you are working as part of a large team, so there is an expectation that as many of the required resources as possible will be created by team members. If you're unsure, it's best to check with the Unit Coordinator.
• Artificial Intelligence (AI) engines can be utilised in your workflow (refer to GenAI statement below) but must be treated as an additional (virtual) team member. If you incorporate AI, make sure to explain its usage in your submission.
• Avoid using someone else's Intellectual Property (IP) in your work, such as ideas from Star Wars or other popular culture franchises.
• Higher marks will be awarded for demonstrating successful experimentation and innovation.
• Late submissions or failure to comply with assessment requirements may result in penalties.
• For more detailed assessment criteria, please refer to the DGTL13007 website.

Use of Generative Artificial Intelligence agents (Gen AI)

Within this assessment, the use of Microsoft Copilot, Chat GPT or other Gen AI agents is as follows:

• Gen AI may only be used as specified in the assignment instructions in Moodle.
• Gen AI content can be used to generate concepts, ideas and general structures.
• GenAI can be used to assist with creating C# code for Unity.
• Gen AI can be used for proofreading.
• Gen AI cannot be used to create media assets (art, sound, animation etc) for your collaborative game.
• If you are unsure, ask the Unit Coordinator.