Platformer Game Search and Help System

As teams of 3 across the class will all be working on the same Platformer Game. We will be adding or extending the Help system to use and develop the game..

  • Each team will make a fork of platformer4x.

  • Each team of 3 will own, update, and customize a topic(s) within the help system.

  • Each team will complete pull requests to platformer4x and present a review.

  • Each team will include topics on how a portion of the game is designed and coded.

  • Each team will prepare ideas for extending that topic.

  • Each individual will prepare final review. Try to highlight 3 to 5 things and be reflective.

  • Team will share their accomplishments with entire class.

Materials

Materials have been provided for key topics. These should be consider starters or guidelines.

  • Key Objectives
    • Read the materials provided
    • Learn your topic in the game.
    • Build ideas on how to change the game.
    • Add learnings and ideas to help system
    • Think that you will be leaving a legacy of work to next Platformer coders, pay forward.
  • Future
    • Building a help and idea system is a great Computer Science skills
    • Think of your work as plan for Sprint 6

Checklist Suggestions

Here are suggested activities. These should be considered minmal, but can be enhanced if they lack detail.

  • Scrum Master of Scrum Masters
    • Start Issue of Team Assignments
    • Starts Kanban Board using Issue from individuals
    • Make sure we are not duplicating by doing reviews with each Scrum Master and Assistant Scrum Master
    • Accept pull requests and ensure they match Team and Individual Assignments
    • Pull in other Scrum Master to support integrations.
  • Scrum and Assistant Scrum Master
    • Build an Outline of Topic and Help Materials using provided materials
    • Discuss Ouline of Topic and of Help Materiasl with Team and with Scrum Master of Scrum Masters
    • Start Individual Issue(s) for Team Members, be sure Issue(s) have burn down lists.
    • Make sure your Issue(s) get on to the Kanban Board
  • Teams of 3
    • Team meets and describes parts of game that will have help system, capture ideas in Team Issue.
    • Break down parts of game into Individual Issue(s) for each Developer
    • Each Developer build skeletal notebooks into platformer game, be sure to update front matter.
    • Make sure skeletal notebooks get into game in 1st week of sprint
    • Make second pass on notebooks to update content and future ideas for system. Make this interesting including code fragments and runn code fragments in code cells. Updating DOM and having help interactive is highly encouraged.
    • Team makes pull request.