Mark Wootton (talk | contribs) Fixed links |
Mark Wootton (talk | contribs) No edit summary |
||
| Line 11: | Line 11: | ||
====== RACI Roles Defined: ====== | ====== RACI Roles Defined: ====== | ||
You can check out a fuller description of RACI [[What is RACI?|here]] and an overview of why we us use it [[Development RACI - Overview|here.]] | You can check out a fuller description of RACI [[What is RACI?|here]] and an overview of why we us use it [[Development RACI - Overview|here.]] | ||
Once you are familiar with RACI and why we use it, you can see a table of the main development tasks and who is generally Responsible, Accountable, Consulted, and Informed [[Development RACI Table|here]]. | |||
====== Key Guidance: ====== | ====== Key Guidance: ====== | ||
Revision as of 17:34, 23 October 2025
What is the Development Wiki?
The purpose of this wiki is to outline what it means to be a Product Developer at AEG and how to do it.
Purpose of this wiki:
To establish the baseline expectations for what it means to lead a product through development at AEG—balancing creative ownership with real-world constraints of time, budget, and coordination.
What this means:
Being a product developer at AEG means more than designing or refining gameplay. It means owning the full arc of a product’s development—from idea to execution—while collaborating closely with cross-functional teams. Developers are responsible not only for the quality of the game, but also for how it fits within our schedule, budget, and publishing goals. To do this we use a system called RACI.
RACI Roles Defined:
You can check out a fuller description of RACI here and an overview of why we us use it here.
Once you are familiar with RACI and why we use it, you can see a table of the main development tasks and who is generally Responsible, Accountable, Consulted, and Informed here.
Key Guidance:
You are not just delivering a game—you are delivering a product.
Creative ideas are encouraged, but scope must match reality.
Baseline budget and timeline are set early and revisited at key checkpoints.
Late changes to scope ripple across the company. Plan carefully and update often.
Action Items:
Define initial product scope and ideal launch window during early development.
Coordinate with Production to estimate component costs and timeline feasibility.
Maintain a working timeline for major deliverables (art, files, prototypes, handoffs).
Flag risks early—schedule changes or budget overruns should be communicated before they become problems.
Follow through the process outlined on the the Development RACI table.
