Game Development Reference
In-Depth Information
Agile Design Development/Client Approval Cycle
Agile Cycle
for Client
Approval
Client response to current
design iteration
Design goes back for
more development
Creation/
Rest/Test
Viable Design
Approved by Client
Agile Cycle
Global Work Force
on the job 24/7
Viable Design NOT
Approved by Client
Creation/
Rest/Test
Client response to current
design iteration
Design Heads to
Next Phase
Agile Cycle
for Client
Approval
FIGURE 3.9
Chart showing the agile design development/client approval cycle. Note how this cycle is dependant
on the client's own approval process. This process should be taken into account when developing a “Build It Once”
methodology for your design group.
by excessive layers of management, unproductive meetings, and bureaucratic ofice procedures. Figure 3.10
shows a basic ofice structure for a large virtual environment design ofice. Again, this is a conceptual rep-
resentation of the structure; your ofice may need to include additional group modules like an educational
planning department, a human interface testing department, or a mobile media integration department. The
structure of the team should be lexible enough so it can add group modules as may be required by new
