Project Managers (PMs) help their teams stay organized, communicate clearly, and finish their work on time.
PMs do not boss anyone around — they guide the team, ask questions, check progress, and help everyone stay focused on the shared vision created by the Storytellers.
A PM ensures:
• Everyone knows their task
• Work matches Storyteller decisions
• Files are named correctly and uploaded properly
• Communication flows between teams
• All voices are heard, especially quieter or younger students
PMs support the process and protect team culture.
A PM’s first responsibility is making sure every student feels included.
PMs should:
• Make space for quieter or younger students to share ideas
• Ask for input from everyone, not just the confident talkers
• Step in if one person is dominating or interrupting
• Encourage respectful listening and turn-taking
• Make sure no student feels ignored or overruled
PMs help every team member feel valued and heard.
PMs must check the Storytellers’ latest decisions before approving or starting any task.
If the Storytellers have not confirmed a feature, creature, item, or location, that task should not move forward.
This prevents teams from spending time on unused or unapproved ideas.
At the start of each class, PMs ask:
• What is everyone working on today?
• Does anyone need help or clarification?
• Are we waiting on anything from other teams?
• Does each person have a small, achievable task?
PMs help create structure and clarity.
PMs keep the workflow organized by:
• Using the class Kanban board (Draw.io)
• Moving tasks to “To Do,” “In Progress,” or “Done”
• Helping break big tasks into smaller ones
• Keeping an eye on what the team needs next
PMs do not do the work — they organize it.
PMs help connect the whole project together.
PMs must regularly communicate with:
Other PMs
• To share updates between teams
• To confirm which assets are ready or not ready
• To coordinate timelines
• To prevent a team from getting blocked
• To resolve confusion before it becomes a problem
The Teacher
• When something is unclear
• When tasks are too difficult
• When a teammate needs help
• When decisions require approval
• When the team is stuck or unsure what to do next
PMs initiate communication — they do not wait for others to ask.
PMs check every finished asset before it goes into the project:
• Correct file name
• Correct file format (.png, .wav, .ogg)
• Transparent background if needed
• Matches the tone and direction defined by the Storytellers
• Is truly “done” and not missing details
When approved, PMs upload assets into the shared project folder (GitHub or Drive).
PMs help prevent too much work from piling up.
They:
• Keep tasks small
• Ensure work matches the schedule
• Prioritize the most important tasks
• Encourage finishing one thing before starting another
Good PMs help the project stay achievable.
PMs should not:
• Redesign the story or override Storytellers
• Make new features without approval
• Micromanage or pressure teammates
• Do all the work themselves
• Allow anyone to dominate the team
• Ignore quiet or unsure students
• Skip checking with other PMs or the teacher
PMs support collaboration — they do not take control away from others.
Before class ends, PMs quickly review:
• What each person finished today
• What needs to happen next time
• Any blockers to report to the teacher
• Whether any team needs something from us
• Whether the Kanban board is updated
A 1–2 minute wrap-up keeps everyone on track.
PMs are doing well if:
• Everyone feels included and heard
• Tasks are clear and manageable
• Communication is steady across all teams
• Assets are uploaded correctly and on time
• The team stays positive, calm, and productive
• The project moves forward every class