Zhixing

Nov.16, 2009

--Reasons for using agile in game development

Reduce waste

Finding fun first

--Agile manifesto for game development

People & Communication > Process & Tools

Working game > Design document

Customer collaboration > Contract negotiation

Responding to change > Following a plan

--The Scrum project community

Team member, Scrum master, Product Owner

--Sprints

--Releases

--Release Execution

--Scrum master

Adaptive actions

--Sprint planning & execution

Product backlog -> Sprint backlog

--Moving to a "Pull" System

Use tool properly

Self-organized team

Define "done"

--Scalability of Scrum

Mix team to lower the integration effort:

[image]

The matrix team structure:

[image]

--Lean Production

Production is an expensive part of development.

Scrum is not the best choice for production, but we don't want lose the benefits of agile:

Continuous Improvement, Collaboration, Focus on value and reduce the waste.

Pre-production vs. production

Lean Game production (Follow the deming cycle):

[image]

7 Lean Principles:

1.Eliminate waste

2.Amplify learning

3.Decide as late as possible

4.Deliver as fast as possible

5.Empower the team

6.Build integrity in balance discipline

7.See the whole

--Repeatable works (Parallel Production)

[image]

--Tools

Time-boxing Assets:

[image]

Asset Streams:

Try the best to keep the steps in a harmony to eliminate buffers.

--Handoffs

Handoffs create a sense of handing-off responsibility.

--Scum vs. Kanban

Kanban:

[image]