This session describes how Lean Production and Kanban has been applied to game development. Lean principles and Kanban tools have been used by a number of developers, including the presenter, to slash production costs by over 50%. As a complement, or replacement, to Scrum, Lean/Kanban provides predictability, transparency and optimization for complex game production.
6 comments:
"As a complement, or replacement, to Scrum, Lean/Kanban provides predictability, transparency and optimization for complex game production."
What, concretely, does "predictability", "transparency", and "optimization" refer to here? Does Scrum provide any of these?
Many developers abandon Scrum for waterfall practices in production for the reasons outlined in the video. Kanban practices are an alternative, which allows them to maintain a focus on continual improvement.
As far as I can tell the video doesn't make the claim about "predictability", "transparency", and "optimization" nor does it explain the terms. So again, could you please explain them in concrete terms?
I think the video clearly outlines these:
Predictability - Takt/cycle time.
Transparency - Kanban board, updated daily.
Optimization - Improved cycle time through workflow improvements (e.g. reducing concept handoffs).
Not perfect, but a big improvement over waterfall approaches. As the presentation shows, that after preproduction, when the flow is more predictable and less exploratory, there are some issues with long chains of work fitting into a sprint.
You can also read the Gamasutra article
http://www.gamasutra.com/view/feature/3847/beyond_scrum_lean_and_kanban_for_.php
or the corresponding chapter in my book.
Thanks,
Clint
Hi Clinton, great presentation. These are exactly the issues we are facing at the moment..
I'm very interested in the process of Asset Streams and will look into this further with my 2D/3D departments.
One of the hardest challenges we face at the moment is control and management, we have development and QA using Rally Software, which assists us no end in the Dev cycle. Moving stories across our none Agile Departments proves to be a huge bottleneck at the moment.
We purchased two copies of your book which are doing the rounds as I type...
Speak soon!
Thanks Richard,
It does take a while for the principles to expand out. This reminds me of one of the main lessons from lean manufacturers: they need to influence their suppliers to be lean as well.
Post a Comment