Scrum Games Industry Hannover 2009

1,532 views
1,421 views

Published on

Games Focus 2009, Hannover, I talk about the reason for professionalism in the games industry, and I show that Scrum might be the answer for studios to deal with the problems that occur when the need is to grow.

Published in: Education

Scrum Games Industry Hannover 2009

  1. 1. Professionalization of the Games Industry presented by Hannover, January 2009
  2. 2. Who is this no-name in YOUR industry?
  3. 3. before Scrum ...
  4. 4. Philosophy and Soziology
  5. 5. EDS | BroadVision | ONE |
  6. 6. I knew how to make projects work the traditional way
  7. 7. 2002
  8. 8. and then the challenge
  9. 9. build it faster and more reliable again!
  10. 10. traditional way would not work ... No Way!
  11. 11. First Scrum
  12. 12. 2003
  13. 13. Certified ScrumMas ter
  14. 14. 2004
  15. 15. 1st Certified ScrumTrainer
  16. 16. ... your expectation is to learn something about Scrum ... so...
  17. 17. Lets start with some findings ...
  18. 18. I found a lot of bashing from Games People about Scrum ....
  19. 19. I found a lot of bashing from Games People about Scrum .... and .... I found ... this:
  20. 20. Scrum and other agile methodologies are changing for the better the way people in the gamesindustry work. YOUR GAMES CAREER: How scrum can help newcomers Paul Keast, by Juice Games -- http:// www.developmag.com/interviews/154/First-scrum-first-served
  21. 21. There is a greater emphasis on knowledge sharing and in ensuring every member of a team has an understanding of how their work fits into the context of the project as a whole. YOUR GAMES CAREER: How scrum can help newcomers by Paul Keast, Juice Games -- http://www.developmag.com/interviews/154/First-scrum-first-served
  22. 22. Not only will new entrants to the industry find they have a greater involvement in shaping the production of a game but they will also learn and progress much quicker than in more traditional development environments. YOUR GAMES CAREER: How scrum can help newcomers by Paul Keast, Juice Games -- http://www.developmag.com/interviews/154/First-scrum-first-served
  23. 23. before we talk about Scrum ...
  24. 24. Why do we need to professionalize?
  25. 25. Features Delivered per Team from a presentation of salesforce.com Scrum Gathering Stockholm 2008
  26. 26. Features Delivered per Team 2000 2001 2002 2003 2004 2005 2006 from a presentation of salesforce.com Scrum Gathering Stockholm 2008
  27. 27. Days between Major Releases Features Delivered per Team 2000 2001 2002 2003 2004 2005 2006 from a presentation of salesforce.com Scrum Gathering Stockholm 2008
  28. 28. Lack of visibility from a presentation of salesforce.com Scrum Gathering Stockholm 2008
  29. 29. Resource Bottlenecks from a presentation of salesforce.com Scrum Gathering Stockholm 2008
  30. 30. Unpredictable release dates from a presentation of salesforce.com Scrum Gathering Stockholm 2008
  31. 31. Lack of responsiveness, lack of team alignment on priorities from a presentation of salesforce.com Scrum Gathering Stockholm 2008
  32. 32. Unhappy customers from a presentation of salesforce.com Scrum Gathering Stockholm 2008
  33. 33. Gradual productivity decline as the team grew from a presentation of salesforce.com Scrum Gathering Stockholm 2008
  34. 34. The claim of most manager and business people is a reflex. They say ....
  35. 35. The claim of most manager and business people is a reflex they say .... We need to structure and organize more .... We need better processes, we need better tools, we need better people. Ok - We need professionalization ...........!?
  36. 36. but ... professionalization of ... what? ....
  37. 37. Organization? Team? Individual?
  38. 38. traditional answer ... team and line management project management portfolio managment going LARGE - going process!
  39. 39. in other words ....
  40. 40. centralistic in other words ....
  41. 41. centralistic hierarchy in other words ....
  42. 42. centralistic hierarchy dominant in other words ....
  43. 43. centralistic hierarchy dominant in other words .... slow
  44. 44. centralistic hierarchy dominant in other words .... slow process driven
  45. 45. centralistic hierarchy dominant in other words .... slow process driven non agile
  46. 46. from a presentation of salesforce.com Scrum Gathering Stockholm 2008
  47. 47. Or you go another path .... and stay:
  48. 48. human-centric Or you go another path .... and stay:
  49. 49. human-centric flat Or you go another path .... and stay:
  50. 50. human-centric flat federalistic Or you go another path .... and stay:
  51. 51. human-centric flat federalistic distributed Or you go another path .... and stay:
  52. 52. human-centric flat federalistic distributed Or you go another path .... and stay: innovative
  53. 53. human-centric flat federalistic distributed Or you go another path .... and stay: innovative agile
  54. 54. human-centric flat federalistic distributed Or you go another path .... and stay: innovative agile re-inventing
  55. 55. human-centric flat federalistic distributed Or you go another path .... and stay: innovative agile re-inventing fast
  56. 56. +568% from a presentation of salesforce.com Scrum Gathering Stockholm 2008
  57. 57. How?
  58. 58. agile answer ... stolen from Pixar (Ed Cutmill)
  59. 59. Empower your creatives
  60. 60. create a peer culture
  61. 61. free up communi- cation
  62. 62. craft a learning environment
  63. 63. get more out of post mortems
  64. 64. is there a path or a guideline can help you ...?
  65. 65. SCRUM
  66. 66. 52 Scrum is not a ....
  67. 67. emphasis in on the team
  68. 68. “Scrum is faster, better, cooler! It’s the way we first built software at Yahoo, yet is scalable to large, distributed, and outsourced teams.” Yahoo Chief Product Owner “It looks like the way we build software here at Rockstar Vienna in the beginning, now we use it in a large organization.”
  69. 69. CHECK it - Daily Scrum HOW to do - Sprint Planning 2 WHAT to do - Sprint Planning 1 The Scrum Analyse PB Flow Tactical © 2009 Level Sprint # 1 Sprint # 2 Sprint # 3 Sprint # 4 9:00 ....... ....... ....... ....... Sprint Planning 1 Sprint Planning 1 Sprint Planning 1 Sprint Planning 1 CU STO MER Do your Daily Scrum every day! Do your Daily Scrum every day! Do your Daily Scrum every day! M ANAGER Product Idea Estimation Meeting 12:00 Review Review Review Sprint Sprint Sprint Sprint Sprint Planning 2 Sprint Planning 2 Sprint Planning 2 Sprint Planning 2 VISION spective spective spective Retro- Retro- Retro- Retro- PR ER Sprint Sprint Sprint Sprint O N DU CT OW SC R E R Version 1.2 T UM MAS 18:00 TEAM Day 1 Release Product Backlog Estimation Estimation Estimation Estimation Estimation Estimation Estimation Estimation prioritized Meeting Meeting Meeting Meeting Meeting Meeting Meeting Meeting PB PB PB PB PB PB PB 1 Under 100 20 stand ? 52 Strategic Planning Poker Play! CU CU 13 30 8 40 M M STO MER STO MER ANAGER ANAGER USER USER Level 3 Releaseplan Releaseplan Update 5 20 8 8 13 version 0.0 version 1.0 version 1.3 version 2.0 version 0.0 version 1.0 version 1.2 version 2.0 5 TEAM SIZE it - Estimation Meeting
  70. 70. The Scrum Analyse PB Flow Vision © 2009 Product Backlog Sprint # 1 Sprint # 2 9:00 ....... ....... Sprint Planning 1 Sprint Planning 1 Prioritization Strategic CU STO MER Do your Daily Scrum every day! Do your Daily Scrum every day! M ANAGER Product Idea Estimation Planning 12:00 Review Review Velocity Process Sprint Sprint Sprint Planning 2 Sprint Planning 2 VISION spective spective Estimation Retro- Retro- PR ER Sprint Sprint O N DU CT OW SC R E R T UM MAS 18:00 TEAM Releaseplanning Day 1 Product Backlog Estimation Estimation Estimation Estimation Estimation prioritized Meeting Meeting Meeting Meeting Meeting PB PB PB PB CU CU M M STO MER STO MER ANAGER ANAGER USER USER
  71. 71. 2009 Sprint # 1 Sprint # 2 9:00 ....... Sprint Planning 1 Sprint Planning 1 CU STO MER Do your Daily Scrum every day! Do your Daily Scrum e M ANAGER Product Idea 12:00 Review Sprint Sprint Planning 2 Sprint Planning 2 VISION spective Retro- PR ER Sprint O N DU CT OW SC R E R T UM MAS 18:00 TEAM Day 1 Product Backlog imation imation imation imation imation prioritized ting ting ting ting PB PB PB
  72. 72. Estimation 9:00 12:00 Meeting 18:00 PB Day 1 M Sprint Planning 2 Sprint Planning 1 ANAGER Estimation Meeting CU STO MER PB Sprint # 1 Estimation Meeting ....... Sprint USER Do your Daily Scrum every day! Retro- Sprint spective Review PB Sprint Planning 2 Sprint Planning 1 CU Estimation STO MER Meeting M Sprint # 2 Estimation ANAGER Meeting ....... Sprint Do your Daily Scrum every day! Retro- Sprint spective Review PB USER Sprint Planning 2 Sprint Planning 1 Estimation Meeting Estimation Meeting PB Sprint # 3 Estimation Meeting ....... Sprint stand Under Do your Daily Scrum every day! Retro- Sprint spective Review PB Poker Planning 3 Play! Sprint Planning 2 Sprint Planning 1 Release Level Level Tactical Sprint # 4 Version 1.2 Strategic
  73. 73. he crum Analyse PB low Tactical 2009 Level Sprint # 1 Sprint # 2 Sprint # 3 Sprint # 4 9:00 ....... ....... ....... ....... Sprint Planning 1 Sprint Planning 1 Sprint Planning 1 Sprint Planning 1 CU ER STO M Do your Daily Scrum every day! Do your Daily Scrum every day! Do your Daily Scrum every day! M ANAGER Product Idea Estimation Meeting 12:00 Review Review Review Sprint Sprint Sprint Sprint Sprint Planning 2 Sprint Planning 2 Sprint Planning 2 Sprint Planning 2 VISION spective spective spective Retro- Retro- Retro- Retro- PR ER Sprint Sprint Sprint Sprint O N DU CT OW SC R E R Version 1.2 T UM MAS 18:00 TEAM Day 1 Release Product Backlog Estimation Estimation Estimation Estimation Estimation Estimation Estimation Estimation prioritized Meeting Meeting Meeting Meeting Meeting Meeting Meeting Meeting PB PB PB PB PB PB PB Under stand Strategic Planning Poker Play! CU CU M M ER ER ANAGER ANAGER STO M STO M USER USER Level 3 Releaseplan Releaseplan Update 5 20 8 8 13 version 0.0 version 1.0 version 1.3 version 2.0 version 0.0 version 1.0 version 1.2 version 2.0 5 TEAM SIZE it - Estimation Meeting
  74. 74. ....... ....... ....... Sprint Planning 1 Sprint Planning 1 Sprint Planning 1 CU STO MER Do your Daily Scrum every day! Do your Daily Scrum every day! Do your Daily Scrum every day! M ANAGER Product Idea Estimation Meeting 12:00 Review Review Review Sprint Sprint Sprint Sprint Planning 2 Sprint Planning 2 Sprint Planning 2 Sprint Planning 2 VISION spective spective spective Retro- Retro- Retro- Retro- PR ER Sprint Sprint Sprint Sprint O N DU CT OW SC R E R Version 1.2 T UM MAS 18:00 TEAM Day 1 Release Product Backlog Estimation Estimation Estimation Estimation Estimation Estimation Estimation Estimation prioritized Meeting Meeting Meeting Meeting Meeting Meeting Meeting Meeting PB PB PB PB PB PB PB 1 Under 100 20 stand ? 52 Strategic Planning Poker Play! CU CU 13 30 8 40 M M STO MER STO MER ANAGER ANAGER USER USER Level 3 Releaseplan Releaseplan Update 5 20 8 8 13 version 0.0 version 1.0 version 1.3 version 2.0 version 0.0 version 1.0 version 1.2 version 2.0 5 TEAM SIZE it - Estimation Meeting

×