Welcome to the
Entrepreneurial Game Studio.

The Entrepreneurial Game Studio (EGS) is a game studio incubator that helps create and support independent, student-led teams from original concept to full release.

Now Playing
Now Playing
Our fully released titles from student-developed, student-led studios.
Now Playing
In Production
In Production
EGS teams are constantly moving, working, and joining. Here are the incubators still in development.
In Production
Research
Research
We also work on research projects that reach out and promote technology to our local community and beyond.
Research
Archive
Archive
Not every project is developed into a final release. Here are our archived and unreleased incubator projects.
Archive

It’s easy to get involved in the EGS Incubator – you don’t even need to have a game design, just a passion to create games and willingness to work hard. We are looking to mentor teams of 2-5 members that can commit to completing their projects in a 6-9 month development cycle.

Part 1: Forming a Team

Here’s what you need to get started:

1. A Team of 2-5 Members

When building your team, consider your coverage of the skills that will be needed to complete your project: game design, programming, narrative, art, music, testing, marketing, and so on. Look for members that you know will be able to consistently attend meetings and contribute to your project as if it were a part-time job (10+ hours/week). Solo projects or large teams (6+) are not usually recommended, but feel free to talk to Tony or Corey if you feel you may have an exception.

2. A Team Lead

Select a member of your group that will serve as the lead for the project and the team. The team lead should be someone with good communication skills who is willing to devote extra time to the project. The lead will act as the public “face” of the group, delegate tasks, track dependencies, facilitate group meetings, report status, resolve conflicts, and drive the schedule. The team lead will be responsible for organizing (or delegating) the sprint retrospective presentations and will report to Tony each week on group progress.

Part 2: Creating the Pitch

Reach out to us to let us know your team is ready to begin the development process.  We will regularly be in touch to make sure you team is always moving forward together. We will be available to help your team brainstorm game ideas, give feedback on pitch materials, and assist with team coordination upon request.

A good pitch should include the following: The design of the game, the makeup of the team, and the business plan to make it into a reality.

Once a pitch is ready to go, reach out to us to schedule a time to pitch. Presentations should be 20-30 minutes long, with another 30 minutes afterwards for Q/A. Pitches with either be accepted for incubation, or given feedback for redevelopment and asked to pitch again at a future date.

Part 3: Developing the Game

Once the pitch is accepted for incubation, the development process begins. Teams will begin to meet with our mentors on a regular weekly basis, and begin following a sprint development model. Over the course of the project, the team should develop the following four items:

1. Game Document

Eventually, each team will write up a clear vision for their project that is updated as the group progresses. The game design will include description of game mechanics and rules, story elements, art specs, as well as scope consideration and risks. Part of the game design will include establishing “pillars” for the design that will codify the team’s vision and establish the intent of the game.

2. Investment Pitch

Each team will create a pitch for their game that will be ready to present at any time and that will adapt as development progresses. This should be a professional and rehearsed presentation that includes applicable media and demos. Additionally, each team should create an “elevator pitch” for the game that can be used to briefly explain their concept.

3. Project Schedule and Budget

The project schedule will be created to track development and team expectations. Though the overall schedule can be vaguely defined, each team will maintain a more precise schedule for the current and upcoming sprint, along with a feature backlog and budgets for their areas.

4. Contract

The team will create an agreement that codifies group expectations and delineates the ownership of the intellectual property created by the group.

Go top