Computer Science & Software Engineering

Course Progress 0/0
Week 17 Sprint 5 - CSSE Objectives

Sprint 5 - CSSE Objectives

3 min read

OCS Game Engine Design/Redesign

Each team of three will be assigned a topic within the Game Engine. Your team is responsible for learning about this topic, making improvements, and becoming the class experts on it.

  • As a team, you will design or redesign your assigned area and submit at least three pull requests to the OCS system repository.

  • You will document your work by writing a blog post and creating Game Runner examples and guides. These should explain the coding fundamentals of your topic and describe the enhancements you made.

  • Finally, your team will present or share at least one of your enhancements with the entire class, teaching your peers about your topic and your contributions.

Materials and Topic Selection

Many materials have been provided for key topics. These are intended as starting points or guidelines for your work.

Key Objectives:

  • Read the materials provided on the pages.
  • Learn and understand your assigned topic in the game engine.
  • Brainstorm and develop ideas for improving or updating your topic.
  • Document your learning and ideas in a blog post and add them to the Search system category.
  • Remember, your work will serve as a legacy for future RPG coders—pay it forward!

Topic Selection Process:

  • Each team will select their top three topic choices (1st, 2nd, and 3rd).

  • Both CSSE classrooms will coordinate the signup process to ensure fair topic distribution.
  • After topics are assigned, each team will submit a pull request to the pages repository for their topic(s), including best original document and the names of all team members working on the task.

Key Roles and Management Checklists

This section outlines the main roles and their responsibilities for effective sprint management. Use these checklists as a guide, and feel free to expand them as needed for your team.

Scrum Master of Scrum Masters (Torin)

  • Start Issue for Team Assignments

  • Launch Project: Kanban Board and Timeline using Issues from individuals

  • Prevent duplication by reviewing with each Scrum Master and Assistant Scrum Master

  • Accept pull requests and ensure they match Team and Individual Assignments

  • Collaborate with other Scrum Masters to support integrations.

Scrum Master

  • Build an outline of the topic and lesson materials using provided resources

  • Discuss the outline of the topic and lesson materials with the team and with the Scrum Master of Scrum Masters

  • Start individual Issue(s) for team members, ensuring each Issue has a burn down list

  • Make sure your Issue(s) are added to the Kanban Board

Teams of 3

  • Meet as a team to describe parts of the game that will have updates and lessons; capture ideas in a Team Issue

  • OCS Game Engine Code Base

    • Team submits a pull request for Teacher review every 3 - 4 school days. At least three times during the 2 weeks.

    • Break down parts of the game into individual Issue(s) for each developer

  • OCS Blogs and Documentation

    • Each developer builds skeletal notebooks into the game, updating front matter as needed

    • Ensure skeletal notebooks are added to the game in the first week of the sprint

    • Make a second pass on notebooks to update content and add future ideas for the system. Make this interesting by including game runner code fragments that run when deployed. Updating the DOM and making help interactive is highly encouraged.

Course Timeline