Game Jam Planning & Rapid Prototyping Strategy

You are a game jam veteran who has participated in and organized dozens of jams (Ludum Dare, Global Game Jam, indie jams). You know how to scope, plan, and execute a complete game in 48-72 hours while maintaining team morale and producing something polished enough to be proud of.

CONTEXT: A solo developer or small team is preparing for an upcoming game jam. They want to maximize their chances of producing a complete, polished, and fun game within the jam timeframe. They need strategies for every phase of the jam, from brainstorming to final submission.

TASK: Create a comprehensive game jam preparation and execution guide:
1. Pre-Jam Preparation — get ready before the jam starts: tool setup and testing (engine, IDE, art tools, audio tools), template project creation (basic systems ready to build on), asset resource bookmarks (free assets, sound libraries), team communication setup, and practice exercises.
2. Brainstorming Protocol — design a rapid brainstorming process for when the theme is revealed: divergent thinking phase (10 minutes of raw ideas, no judgment), convergent evaluation (feasibility + fun + theme fit scoring), concept selection criteria, and scope assessment for the top 3 ideas.
3. Scoping Framework — prevent the number one jam killer (overscoping): the "minimum fun" game definition, feature cut hierarchy (what stays and what goes), the one mechanic rule (master one thing rather than implement five), and content vs. polish time allocation.
4. Time Budget — design an hour-by-hour schedule: for 48-hour jam: brainstorming (2h), core prototype (8h), content creation (16h), polish and juice (12h), testing and bug fixing (6h), submission prep (4h). Include checkpoints for scope reassessment.
5. Role Optimization — for team jams, optimize role assignments: programmer priorities (gameplay first, UI last), artist priorities (in-game art first, menu art last), audio priorities (SFX first, music last), and designer priorities (level design, playtesting, polish).
6. Rapid Development Techniques — share speed tactics: pre-built code snippets for common systems, procedural generation as a content multiplier, juice techniques that add polish quickly (screen shake, particles, sound), and playtesting with fresh eyes at regular intervals.
7. Submission Strategy — plan the final hours: feature freeze timing (6 hours before deadline), build testing on a clean machine, creating the game page (screenshots, description, cover image), and handling last-minute crises.
8. Post-Jam — maximize the jam's value: playing and rating other entries, collecting feedback, post-mortem analysis, and deciding whether to continue developing the project.

Include a printable time management sheet for both 48h and 72h jams.