Development RACI Table: Difference between revisions

Latest revision as of 20:24, 15 November 2025

The Development RACI matrix is a structured spreadsheet used to track and clarify every key action that occurs while a game is moving through AEG’s development process. It outlines who is Responsible, and Accountable, and links the users to the appropriate tools needed, as nwell as providing outline instructions to complete that task. A more detailed breakdown of these instructions is provided in this Wiki.

During the Development stage the assigned Developer is accountable for the overall progress of their title, specific tasks may be owned or approved by other team members across Production, Marketing, Art, and beyond. This framework provides visibility, promotes collaboration, and reinforces accountability across departments as we build each game to its fullest potential.

This is a quick glance summary of all of those that have been designated roles within the RACI matrix as it pertains to all of the key development tasks.

It is important to note that the RACI matrix spreadsheet (and this table) is a template, and certain specialist requirements and asset roles lines may need to be added on a product by product basis. But the principle of how it works should remain the same.

IMPORTANT: Many of the links to documents in this table link to TEMPLATE documents. It is important that when you go to these templates you do not overwrite them, but rather save a product-specific copy into the Google Drive folders that you have set up for your product.

Google Drive file structure can be found here.


Number	Task	Sub Task	Responsible	Accountable	Consultant	Informed
1	Project Management.	Read "What is RACI"	Dev	Dev
2		Find & cost appropriate external assets (typically art director, graphic designer, artists)	Dev	Mark
3		Fill out and submit Contract Asset Forms	Dev	Mark
4		Fill out and submit Cost reports	Dev	Mark
5		Set up RFQ document	Dev	Dev	Kirk/Josh/Mark
6		Check in on budget needs and spend versus projections	Dev	Mark
7		Maintain and update the Creative Brief for the product	Dev/Mark/Kirk/Josh	Dev
8		Create and update a 5 pillars data sheet for Cost of Goods	Dev	Mark
9		Add any new assets to the asset farm	Dev	Dev
10		Recruit External Assets, (Secure Contract, Cost Report template links in rows 5 & 6) - e.g. Graphic Designer, Editor, Rules Writer	Dev	Dev	Kirk/Josh/Mark
11		Keep AEG informed on progress timelines through 6 and 12 weekly progress meetings.	Dev	Mark	Mark, Z, Whitney, Adelheid, Nicolas
12	Playtesting	Create physical prototype	Dev	Dev	Kirk/Josh/Mark
13		Organise playtest sessions	Dev	Dev	Kirk/Josh/Mark
14		Communicate feedback and co-ordinate discussions with the designer(s).	Dev	Dev	Kirk/Josh/Mark
15	Online Testing	Put together & Maintain a TTS mod (can use external asset to do this)	Dev/Other?	Dev	Kirk	Josh/Mark
16		Organise times to playtest and receive feedback from AEG assets on design	Dev/Mark/Kirk/Josh	Dev	Mark, Z, Whitney, Adelheid, Nicolas	Josh/Mark
17	Mechanics	Receive and respond to playtest feedback with mechanical updates	Dev/Designer	Dev	Mark/Josh/Kirk	Josh/Kirk
18		Keep a templating and style guide (game terminology).	Dev/Designer	Dev	Mark/Josh/Kirk	Josh/Kirk
19		Maintain outline up to date rules.	Dev/Designer	Dev	Mark/Josh/Kirk	Josh/Kirk
20	Marketing engagement	Write marketing text for the back of the box	Dev/Whitney	Whitney	Adelheid
21		Help set up appropriate section of the Crowdfunding Plan sheet (Stretch Goals tab, Graphic assets tab)	Z, Ryan, Adelheid, Dev	Ryan	Mark/Josh/Kirk
22		Influencer relationships	Whitney, Dev	Whitney	Dev
23	Graphics & other Design assets	Manage Graphic Design and provide them with the design guide	Dev	Dev	Kirk/Josh/Mark	Josh/Mark
24		Provide and recieve feedback to AEG on graphic design progress and graphical components. - 12 weekly presentation to company on the latest version of the game - Upto 1 hour per week time allocation with Kirk - Meetings with Marketing (Adelheid and Whitney) and Licencing (Nicolas) to be scheduled by Developers.	Dev	Dev	Kirk, Z, Whitney, Adelheid, Nicolas	Josh/Mark
25		Provide ideas and brainstorm content for upgraded KS edition of game	Dev/Ryan	Dev	Z, Whitney, Adelheid	Kirk/Josh/Mark
26		Finalise ideas on KS deluxe/add on options for Graphics requirements	Dev/Ryan	Ryan	Z, Whitney, Adelheid	Kirk/Josh/Mark
27		Deliver high quality brand logo for product	Graphic Designer/Adeleheid/Z	Adelheid	Dev, Designer
28		Deliver high quality graphical components for product	Graphic Designer	Dev	Kirk/Josh/Mark/Z	Josh/Mark
29		Ensure that all files are handed off for approval within the AEG standards set for files	Graphic Designer	Dev	Adelheid/Kirk
30	Art Direction	Manage Art Director	Dev	Dev	Josh/Kirk/Mark	Kirk/Mark
31		Write/create art descriptions and guidelines for project	Art Director	Dev	Josh/Kirk/Mark	Kirk/Mark
32		Provide and receieve feedback to AEG on art progress and quality.	Art Director	Dev	Josh, Z, Whitney, Adelheid, Nicolas	Kirk/Mark
33		Produce cover and other marketing art	Graphic Designer/Adeleheid/Z	Adelheid	Dev, Designer
34	Rules Writing	Manage Rules Writer	Dev	Dev	Kirk/Josh/Mark
35		Write Rules	Writer	Dev	Kirk/Josh/Mark
36		Review Print files after Graphic Design	Writer	Dev	Kirk/Josh/Mark
37	Editor	Manage Editor	Dev	Dev	Kirk/Josh/Mark
38		Edit rules (and other necessary components)	Editor	Dev	Kirk/Josh/Mark
39		Proof Print files after Graphic Design	Editor	Dev	Kirk/Josh/Mark
40	Checklist Review	Set up Checklist Review doc	Dev	Dev	Kirk/Josh/Mark
41		Schedule Review, recruit reviewers	Dev	Dev	Kirk/Josh/Mark
42		Update RFQ	Dev, Adelheid	Dev	Mark/Josh/Kirk
43		Handoff for Production review - press files pending Ensure File naming and labelling follows AEG convention	Dev	Dev	Nicolas
44	Influencer Press File Handoff	Package all INDD & Adobe files.	Graphic Designer	Dev	Kirk
45		Move all files to Google Drive for pre-production	Graphic Designer	Dev	Kirk
46		Rename to Production naming conventions	Dev	Dev	Kirk, Adelheid, Dave
47		Move to Production Dropbox - press files pending	Production	Production	Kirk, Adelheid, Dave
48	Pre-Production Prototype	Review physical copy for production errors	Dev	Dev	Kirk/Josh/Mark
49		Review physical prototype for ergonomic play issues	Dev	Dev	Kirk/Josh/Mark
50	Production Press File Handoff	Make changes to files based on review	Graphic Designer	Dev	Kirk
51		Update RFQ	Dev	Dev	Kirk/Josh/Mark
52		Package all INDD & Adobe files.	Graphic Designer	Dev	Kirk
53		Move all files to Google Drive for pre-production	Dev	Dev	Kirk
54		Rename to Production naming conventions	Dev	Dev	Kirk, Adelheid, Dave
55		Move to Production Dropbox - press files pending	Production	Production	Kirk, Adelheid, Dave

@@ Line 10: / Line 10: @@
 It is important to note that the RACI matrix spreadsheet (and this table) is a '''template''', and certain specialist requirements and asset roles lines may need to be added on a product by product basis. But the principle of how it works should remain the same.
-===== IMPORTANT: Many of the links to documents in this table link to TEMPLATE documents. It is important that when you go to these templates you do not overwrite them, but rather save a copy into the Google Drive folders that you have set up for your product. =====
+===== IMPORTANT: Many of the links to documents in this table link to TEMPLATE documents. It is important that when you go to these templates you do not overwrite them, but rather save a product-specific copy into the Google Drive folders that you have set up for your product. =====
 Google Drive file structure can be found here.
 {| class="wikitable"
@@ Line 22: / Line 22: @@
 | style="" |'''Informed'''
 |-
-| style="" |1
+| style="" |[[What is RACI?|1]]
 | style="" |'''Project Management.'''
 | style="" |[[What is RACI?|Read]] "What is RACI"
@@ Line 30: / Line 30: @@
 | style="" |
 |-
-| style="" |2
+| style="" |[[02. Development RACI - Find and Cost Appropriate External Assets|2]]
 | style="" |
 | style="" |Find & cost appropriate external assets (typically art director, graphic designer, artists)
@@ Line 38: / Line 38: @@
 | style="" |
 |-
-| style="" |3
+| style="" |[[03. Development RACI - Asset Contract Forms|3]]
 | style="" |
 | style="" |[https://docs.google.com/spreadsheets/d/16wARUzRVTVL_8nhHg3ja7c3Ia1f2jLLJ/edit?gid=850046317#gid=850046317 Fill out and submit Contract Asset Forms]
 | style="" |Dev
 | style="" |Mark
-| style="" |
 | style="" |
 |-
-| style="" |4
+| style="" |[[04. Development RACI - Fill out and submit Cost Reports|4]]
 | style="" |
 | style="" |[https://docs.google.com/spreadsheets/d/1i-tDV-seWGL5tCFP2IuyX_k1235XMieE/edit?gid=1349561685#gid=1349561685 Fill out and submit Cost reports]
@@ Line 54: / Line 53: @@
 | style="" |
 |-
-| style="" |5
+| style="" |[[05. Development RACI - Set up RFQ document|5]]
 | style="" |
 | style="" |Set up RFQ document
@@ Line 62: / Line 61: @@
 | style="" |
 |-
-| style="" |6
+| style="" |[[06. Development RACI - Budget spend and projections|6]]
 | style="" |
 | style="" |Check in on budget needs and spend versus projections
@@ Line 70: / Line 69: @@
 | style="" |
 |-
-| style="" |7
+| style="" |[[07. Development RACI - Maintain and update the Creative Brief|7]]
 | style="" |
 | style="" |[https://docs.google.com/document/d/19LeUuvkva-KuzDyiRdRDC8WzkgGMoqRfnRhkocG4Jao/edit?usp=sharing Maintain and update the Creative Brief for the product]
@@ Line 94: / Line 93: @@
 | style="" |
 |-
-| style="" |10
+| style="" |[[10. Development RACI - Recruit external assets|10]]
 | style="" |
 | style="" |Recruit External Assets, (Secure Contract, Cost Report template links in rows 5 & 6) - e.g. Graphic Designer, Editor, Rules Writer
@@ Line 102: / Line 101: @@
 | style="" |
 |-
-| style="" |11
+| style="" |[[11. Development RACI - Progress and Progress Meetings|11]]
 | style="" |
 | style="" |Keep AEG informed on progress timelines through 6 and 12 weekly progress meetings.
@@ Line 110: / Line 109: @@
 | style="" |
 |-
-| style="" |12
+| style="" |[[12-14, Development RACI - Create and Test a Physical Prototype|12]]
 | style="" |'''Playtesting'''
 | style="" |Create physical prototype
@@ Line 118: / Line 117: @@
 | style="" |
 |-
-| style="" |13
+| style="" |[[12-14, Development RACI - Create and Test a Physical Prototype|13]]
 | style="" |
 | style="" |Organise playtest sessions
@@ Line 126: / Line 125: @@
 | style="" |
 |-
-| style="" |14
+| style="" |[[12-14, Development RACI - Create and Test a Physical Prototype|14]]
 | style="" |
 | style="" |Communicate feedback and co-ordinate discussions with the designer(s).
@@ Line 134: / Line 133: @@
 | style="" |
 |-
-| style="" |15
+| style="" |[[15-16, Development RACI - Online Testing|15]]
 | style="" |'''Online Testing'''
 | style="" |Put together & Maintain a TTS mod (can use external asset to do this)
@@ Line 142: / Line 141: @@
 | style="" |Josh/Mark
 |-
-| style="" |16
+| style="" |[[15-16, Development RACI - Online Testing|16]]
 | style="" |
 | style="" |Organise times to playtest and receive feedback from AEG assets on design
@@ Line 150: / Line 149: @@
 | style="" |Josh/Mark
 |-
-| style="" |17
+| style="" |[[17. Development RACI - Receive and Respond to Play-test Feedback with Mechanical Updates|17]]
 | style="" |'''Mechanics'''
 | style="" |Receive and respond to playtest feedback with mechanical updates
@@ Line 158: / Line 157: @@
 | style="" |Josh/Kirk
 |-
-| style="" |18
+| style="" |[[18. Development RACI - Keep a Templating and Style Guide|18]]
 | style="" |
 | style="" |Keep a templating and style guide (game terminology).
@@ Line 166: / Line 165: @@
 | style="" |Josh/Kirk
 |-
-| style="" |19
+| style="" |[[19. Development RACI - Maintain outline up-to-date Rules|19]]
 | style="" |
 | style="" |Maintain outline up to date rules.
@@ Line 174: / Line 173: @@
 | style="" |Josh/Kirk
 |-
-| style="" |20
+| style="" |[[20. Development RACI - Write Marketing Text for the Back of the Box|20]]
 | style="" |'''Marketing engagement'''
 | style="" |Write marketing text for the back of the box