Fredrik Carleson's

The Gamemasters Framework for Software

- An Alternative To Other Frameworks On How To Deliver Great Software

Create a Scenario

▢ Complete background story 
▢ Get necessary buy-in and go-ahead received from sponsors.
▢ Ensure the team has all the necessary skills to complete the scenario.
▢ Do Stakeholder mapping
▢ Inform and book NPC’s as needed
▢ Agree on Goals and measuring principles
▢ Decide on the number of experience points.
▢ Give adventurers relevant handouts and background.
▢ Take deadlines into account. 

Start scenario

▢ Gather all adventurers and ensure 100% commitment during the scenario.
▢ The GM informs the team; all scenario conditions have been agreed upon—for example, deadlines, NPC’s, goals and OKRs, XP, etc.
▢ The team plans how to complete the scenario using their abilities, skills and taking existing conditions into account.

During scenario

▢ Team act and react to complete goals using their skills and problem-solving activities. The team works on what is within their zone of control.
▢ The GM thinks proactively, anticipating the team's subsequent actions, preparing whatever is needed for the team to have a “flow.” The GM shields the team from outside noise allowing the team to focus. 
▢ The GM makes sure that NPC’s and conditions are available/ready just in time.
▢ The GM works on preparing the following scenario for the team in advance.
▢ The GM adapts the scenario due to unexpected actions from the players or unforeseen external events.

Ending a scenario

▢ Verify all goals are completed.
▢ The GM debriefs the scenario.
▢ Distribute experience points to the team.
▢ Celebrate if a new level has been reached.
▢ The team discusses if they had the right skills for the scenario, if they had flow and why (if any) the team could not achieve some goals. 
▢ GM prepares for the following scenario (if not already done).
▢ The team can be on standby for a few days correcting bugs, refactoring, reading up on new technology or material for the following scenario.