Kanban & Making Your Production Scream

Size: px

Start display at page:

Download "Kanban & Making Your Production Scream"

Hilary Pierce
6 years ago
Views:

1 Kanban & Making Your Production Scream Presented by Clinton Keith

2 Clinton Keith

to start doing this next week Definition: production means content production

3 Takeaway Provide you with another set of tools for production Demonstrate how Kanban is being used successfully today in game development Give you the ability to start doing this next week Definition: production means content production Agenda Define kanban Setting it up Improving production Planning & kanban Examples Tools

4 Kanban supports agility

5 What is this Kanban thing? Content Time

6 What is kanban? Kanban A tool for managing the flow of assets or information (or whatever) in a process. The name 'Kanban' originates from Japanese, and translates roughly as "signal card"

a plan of how it should be built Reality trumps planning (& management theater)

7 What does kanban mean to you? Visualizing flow of valuable stuff actually being built, rather than relying on a plan of how it should be built Reality trumps planning (& management theater) Planning typically doesn t prioritize quality tradeoffs and account for production problems and improvements What s the difference?

8 Three Basic Rules Visualize Workflow Have physical boards in prominent locations that show everyone what is going on. And have a clear goal for the delivery that everyone can understand Limit Work-in-Progress Get more done by doing less. Reduce multitasking and batching assets to reduce rework and improve quality Measure and Improve Flow Track some simple metrics that show us whether our process is improving. Consistently seek ways to introduce measurable improvements

9 Starbucks Kanban Line Order Buffer Prepare Leave Coffee Mocha Coffee Latte Coffee Americano Frappuccino Latte

10 Scrum vs kanban To do Ongoing Done B C A F D E To do Ongoing (2) Buffer (1) Ongoing (1) Done A B D C F E

11 Setting up Kanban Content Time

12 Starting Kanban Start with what you have and use it to improve incrementally Visualize your process Map it Add metrics Inspect Adapt

13 Visualizing the value stream Concept Approval Low pass geometry High rez geometry Lighting Outsource Props Approval Gameplay tuning Audio layout Test

14 Map it Measure it Concept Approval Low-pass Geometry Hi-Res Geometry Lighting Approval Gameplay Audio Test Deploy Cycle time

15 Improving Production Content Time

16 Limit Work-in-Progress (WiP) On Deck (5) Model Texture Test (2) (5) (4) Done Bug (3) Requirement

17 Buffer for variation On Deck (5) Model Texture Buffer Test (2) (4) (4) Done Bug

18 Overflow On Deck (5) Model Texture Buffer Test (3) (4) (4) Done Bug

19 Underflow On Deck (5) Model Texture Buffer Test (3) (4) (4) Done Bug

20 Emergency lane On Deck (5) Model Texture Buffer Test (3) (5) (4) Done Urgent Request

21 Multiple Teams Product Blue Product Red Shared On Deck (5) Model (3) Texture Buffer Test (4) Done Team Blue (3) Team Red (3)

22 Managing Specialization = Token On Deck Model Texture Buffer Test (5) (3) (5) (4) Requires Specialist Work Done

23 Cadences M T W T F M T W T F Review & retrospective

24 Kanban boards come in all shapes and sizes

25 Planning & Kanban Content Time

26 Relative size / cadence

27 Burn-up Charts 50$ s%deployed% 40$ 30$ 20$ 10$ 0$ 1/1/12$ 1/8/12$ 1/15/12$ 1/22/12$ 1/29/12$ 2/5/12$ 2/12/12$ 2/19/12$ 2/26/12$ 3/4/12$ 3/11/12$ 3/18/12$ 3/25/12$ 4/1/12$ 4/8/12$ 4/15/12$ 4/22/12$!10$

28 Forecasting Date Forecast s%deployed% 50$ 40$ 30$ 20$ Scope Forecast 10$ 0$ 1/1/12$ 1/8/12$ 1/15/12$ 1/22/12$ 1/29/12$ 2/5/12$ 2/12/12$ 2/19/12$ 2/26/12$ 3/4/12$ 3/11/12$ 3/18/12$ 3/25/12$ 4/1/12$ 4/8/12$ 4/15/12$ 4/22/12$!10$

29 Examples Content Time

A lot more visibility and clarity on where things are

Easy to quickly see the overall project schedule and

This helped many times for re-aligning resources to

Planning is actually much easier and straight forward

Kanban got us to realize improvements to our process

30 A lot more visibility and clarity on where things are and what needs to be worked on. Easy to quickly see the overall project schedule and what can and can t get done. This helped many times for re-aligning resources to meet our goals. Planning is actually much easier and straight forward for a kanban team working within the Scrum structure. Kanban got us to realize improvements to our process and pipeline. Specifically, making blocked animations and proxy models to get things in game as quick as possible and keep everything moving. Benefits Reported

Developers have a say in the board and don t have to ask anyone about the state of

31 Benefits Reported Intelligent cross-discipline discussions 20% improvement in outsourced work due to direct discussion on how to improve quality earlier Developers have a say in the board and don t have to ask anyone about the state of an asset Higher investment in the process as well as a better mood about the team and how they work

32 Tools Content Time

33 Time-boxing A time-box is a fixed length of time given to produce results. The results are variable. When forced to work within a strict framework the imagination is taxed to its utmost-and will produce richest ideas. Given total freedom the work is likely to sprawl. -TS Eliot

34 Stop the line

35 Summary Kanban can be started quickly The less change up front, the better WiP limits, buffers, swim lanes, etc. are useful to improve flow But most improvements come from teams Cultural changes are big Improvements > 50% seen...but we should expect production to improve over time as well

More Info White paper coming at http://blog.

the upcoming question to @LeanTL The first correct answer

36 More Info White paper coming at Clinton Keith Traffic Light Contest Tweet the answer to the upcoming question The first correct answer that the traffic light receives will cause it to go solid red. The person who answers it wins the traffic light (must be present)

MTAT Software Engineering Management

MTAT Software Engineering Management MTAT.03.243 Software Engineering Management Lecture 11: Flow-based (KANBAN) Principles and Processes Dietmar Pfahl Spring 2014 email: dietmar.pfahl@ut.ee Structure of Lecture 11 Flow-based agile development