Your Game Workspace

Before anything else, one team member creates the GitHub repo, then:

  1. Add Collaborators → Settings → Collaborators → Invite your team (they need write access)
  2. Enable Issues & Projects → Settings → Features → Check both boxes
  3. Each person clones → git clone <repo-url> in Terminal
  4. Open in VSCode → code <repo-folder> be sure to source your venv

Critical: Everyone must have the repo open in VSCode with collaborator access. No access = can’t contribute = can’t get credit.

After cloning your repo, here’s where you’ll be working:

The workflow from GameBuilder to Assessment:

  1. Test locally → make dev then save and test to see it works
  2. Open in browswer the project is localhost:4500/gamify
  3. Power through README here
Game Status: Not Started

Team Project Launch (Using _projects)

You are now moving from individual file structure (_notebooks, _posts) into team project structure (_projects).

Use this 5-step launch flow:

  1. Pick a Team
    • Form a balanced team and agree on roles (planner, scrum master, scrummers, technologist, reviewer, tester, demo lead, finisher).
    • Keep roles lightweight and rotate when needed.
  2. Start Project Coordination
    • Create a Kanban board for your team workflow.
    • Track work in GitHub Issues and assign ownership.
    • Move tasks through To Do -> In Progress -> Done.

Example Kanban:

Example Kanban

Example Kanban Link

Example Team Issue:

Example Team Issue

Example Team Issue Link

  1. Reuse Your Pro Dev Tools
    • Keep using VSCode, terminal, GitHub PRs, GitLens, and Copilot as you already practiced.
    • Run make dev during active development so changes regenerate as you work.
  2. Use the Gamify Layout (Do Not Re-define It, complement it!)
    • Follow the project structure and workflow in the gamify README.
    • Add to your new _project in a structure and planned way
    • Add documentation, see sample in project
  3. Start Planning
    • Define a short project goal for your gamify experience.
    • Break work into small issues for the first sprint.
    • Decide what each member will demo in formative/summative evidence.

Pro Dev Execution Playbook

Now that your team has launched the project, use this section for daily execution. The goal is simple: small changes, clear ownership, visible evidence.

Daily team loop:

  1. Pull latest changes from your team branch/repo.
  2. Run make dev and keep it running while you work.
  3. Pick one Issue card and complete one scoped change.
  4. Commit and open/update a PR with a short summary.
  5. Move Kanban cards and post Issue progress notes with evidence.

Your tool stack in practice:

  • VSCode for editing and debugging
  • Terminal for make dev and quick validation commands
  • GitHub Issues + Kanban for coordination and accountability
  • PRs + reviews for quality checks before merge
  • GitLens + Copilot to move faster with traceability
  • Upstream sync remote and merge when instructed

What a strong work session looks like: Sample VSCode

Capture evidence for formative/summative checks:

  • Active Issue with status update
  • Linked commit or PR
  • Screenshot of running game change
  • Brief note on what worked and what needs next