Agile for game_development


Published on

Agile for Game Development
because white knuckle delivery is not fun

  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Why Agile? That’s why we are gather here…Rhythm – In agile rhythm is everythingGame development – There are a few specifics that apply to agile in a game development contextTeam – a few slides on who does whatAgile planning – a short exercise on planningRubber… meet road – the flavors of agile in our world, the studioNext steps – what happens after these few hours we spend together
  • Story – is a lighter form of a requirement but stated in a way that everyone can understand. It has a basic syntax or form that focuses on who, what and why.Plan – planning is key to agile but mostly in the short range sense. Long term planning is what feeds the project it’s stories. The project focuses on a plan that delivers value early and often to narrow the “expectation gap”. The expectation gap happens when the stakeholder of a product has expects something that is not what is delivered – closing the gap is key reducing effort what is NOT needed.Sprint – a short range plan that selects the most important stories for delivery in a release.Story point – is a relative estimate of effort to complete a story... Humans are generally bad at absolute estimation exact things but they are pretty good a “relative” estimation.Task – is the work needed to complete a story, there can and usually is more that one task per story. Tasks are usually estimated using hours – absolute estimation by consensus (group thinking). However, it is after all and estimate and if things go south then the estimate is updated to hours remaining.
  • Agile – visit for the details… looking at from out perspective it’s a focus on quality and to anticipate change as opposed to react to itScrum – it’s origins are from Rugby… a brief huddle to determine a plan (daily) and allow for adjustments to be madeLean – Agile is a general process. For some areas, like content creation for game development, the stages and tasks are fairly well defined. Lean attempts to marry this with a typical agile engineering process. Retrospective – Helps to improve process and to clean up the funk!
  • Life wasted or lean machine?Life wasted – ever create a set of art only to find that at some point while you were working the “focus” of the project changed… wasted time.Lean machine – find yourself waiting on another artist, sound guy, engineer for something… too much fat.
  • Time for a 5 minute musical interlude…
  • A few examples… some with value, some not so much.The first one: a story we can implement? Not reallyThe second one: some basic functionality that every game should have, maybe too generalThe third one: a specific game feature, getting closerThe forth one: about the same level as the previous, closer againThe point here is that stories are like requirements – if they are vague, non-specific and wide open to interpretation the end product will be too.Good stories are a key driver to a successful project – regardless of the process.
  • Let’s break the second story down to take a closer look at the syntax of a story.
  • Okay, now a quick run at a task breakdown for the story. Can these be hour estimated? I think so but the quality of the estimate will more than likely be too vague.
  • Drill down to another level… say buttons and symbols.Now we have a quantity of buttons and symbols… better task hour estimates are probably found here.A quick survey:How long does it take to create content for a dynamic button?Static:With animation:How long does it take to create a symbol?Static:With animation:In this case since we, as a group, have made slot games before the jump from the story to the tasking was easier. I would almost say that this can apply to any game with buttons and symbols. So imagine, getting lean on this part of the game content creation process and having more time to work on new content that will set the game apart from others.
  • So, what happens when a story is too vague – turn to the product owner for guidance.
  • My Uncle Bob Martin always says, “Planning is a good thing, taken in moderation.” Getting into the agile rhythm is where the plans are executed.
  • Everyone on the team does this in less than 15 minutes. Do the math, 7 person team minus 1 minute for overhead and that’s 2 minutes per person.Key to this:Summarize yesterday – I finished x,y,zTask for today – I’m working on x,yBriefly state the blocking condition – communicate the details later on (or before and have a plan ready)Do this to avoid rat holes and keep the meeting short.Oh, and show up on time. Those who are late need to put a $1 in the tip jar.Do this everyday for the life of the sprint…There is a bit of accounting that has to happen before or right after the meeting so the project manager and product owner can measure progress… more on that later.
  • What happens at the end of the sprint?A demo – to the team, product owner and interested stakeholdersHere is where the anyone has input with regard to the quality of the content in the demo. Pass acceptance tests?Visually appealing?Fun to play?Sounds good?So, does a demo sound like too much effort for an every few weeks event? At first blush the answer may be yes. However, take this situation into consideration: A stakeholder (VP, product manager, etc.) gets wind of this great new game the studio is working on and wants a demo. In the current environment a mad scramble ensues, assets need to be located, the engineer has to build the game and put on hardware, meetings are scheduled, etc. Sounds like a fairly large disruption to me. Even bigger if source control and CI are not being used by the team. A better answer is: okay we have a demo scheduled on Friday (end of sprint) come on by OR have the last demo up and running and send out and open invitation. The team keeps working and the show and tell is a minor bump in the sprint.
  • Agile for game_development

    1. 1. Agile for Game Development<br />because white knuckle delivery is not fun<br />
    2. 2. Overview<br />Why Agile?<br />Rhythm<br />Game development<br />Team<br />
    3. 3. Terminology<br />A storydescribes a capability that adds value to the product<br />A team plans a sprint using stories as input<br />A sprintis the time period in which the plan is executed<br />A story pointis a relative estimate of effort of a story<br />A taskis work that is done to complete a story<br />
    4. 4. Terminology<br />Agile is a lightweight process, to produce a quality product, that accommodates change<br />Scrumis an agile story driven process that delivers value at the of each sprint<br />Leanin game development formalizes the phases of content production in and around scrum<br />Retrospectivean end of sprint activity by the team to determine how well things are going<br />
    5. 5. Synonyms<br />Daily Scrum: Stand-Up<br />Story: User Story, Feature<br />Sprint: Iteration (but not the in the waterfall sense)<br />Stack Order: Priority<br />Story Points: Feature Points<br />Retrospective: post-mortem<br />
    6. 6. Why Agile?<br />to smooth out the development pipeline<br />
    7. 7.
    8. 8.
    9. 9. themes<br />stories<br />planning<br />stages<br />releases<br />epics<br />
    10. 10. Exploration<br />Production<br />
    11. 11.
    12. 12.
    13. 13.
    14. 14.
    15. 15.
    16. 16. It’s not me, it’s you<br />Agile is not…<br />A silver bullet<br />Guaranteed on-time delivery<br />Culture change<br />Dysfunction junction<br />FUD<br />Endless development<br />Management fad<br />Pass/Fail<br />Meeting Hell<br />
    17. 17. Tikl time<br />
    18. 18. Planning<br />
    19. 19. Stacking wilds<br />animated symbols<br />20 symbols<br />5x5 100 lines<br />I want my game features!<br />buttons<br />top glass<br />meters<br />movies<br />
    20. 20. User Story<br />As a <type of user><br />I want <some goal><br />so that <some reason><br />
    21. 21. Let me tell you a story...<br />As a player I want games to be fun so that I can win lots of money<br />As a player I want to bet on a game in order to play it<br />As a player I want stacked wilds in a game because visual anticipation is exciting to me<br />As a player I want to view the see pays screen in order to understand the game odds<br />
    22. 22. Are you tasking that story?<br />Take a look at the story: As a player I want to bet on a game in order to play it<br />Breakdown:<br />player: user type<br />bet on a game: goal<br />play it: reason<br />
    23. 23. Are you tasking that story?<br />Task breakdown - for art<br />Button<br />Symbols<br />Reels & pay lines<br />Meters: bet, credit & win<br />
    24. 24. Are you tasking that story?<br />Button<br />10 bet buttons<br />1 bet max<br />1 repeat bet<br />Symbols<br />10 static<br />2 animating<br />Is a task for each button appropriate?<br />Was this story written with an appropriate level of detail?<br />
    25. 25. What you don’t know<br />Product Owner role<br />will clarify the content of a story<br />will prioritize stories in order of what should be done first<br />will serve as the interface to product management, stakeholders, etc.<br />make decisions<br />keep the team fed and happy - or at least caffeinated <br />
    26. 26. Rhythm<br />In a sprint rhythm is everything<br />
    27. 27. Scrum<br />Questions:<br />What did I do yesterday?<br />What am I doing today?<br />Any impediments to progress?<br />The majority of the sprint is dedicated to these questions<br />
    28. 28. For my final trick<br />Can I get a witness?<br />Always show your work at the end of the sprint<br />Product owner, stakeholders, team, etc.<br />No, that’s not quite right<br />Expectations change over time<br />Stories/tasks for the next iteration<br />
    29. 29. In retrospect<br />That felt good, but next time...<br />Team discusses the Good, the Bad and the Ugly<br />Keep the Good<br />Action plan to improve the Bad<br />The Ugly is usually rolls uphill (and back down again)<br />
    30. 30. Process Review<br />Always Demo!<br />Game Demo<br />
    31. 31. Tikl time<br />
    32. 32. Game Development<br />
    33. 33. Game Development<br />Finding fun<br />Expecting a delivery<br />“need it for the show”<br />Stage this<br />Concept<br />Pre-production<br />Production<br />User Alpha, Beta<br />
    34. 34. Game Development<br />Release me<br />Releases enable “review early and often” habit<br />You are in debt<br />A release demo combined with sprint retrospective will help free the project of creative debt<br />Certainly lean<br />Lean game development augments scrum with stages<br />Time in a box<br />Timeboxing is a lean technique to facilitate creative work on a time budget (task hours)<br />
    35. 35. Series of Releases<br />Stories<br />
    36. 36. Team<br />
    37. 37. Scrum Personas<br />direction<br />process<br />monitor<br />work happens here<br />
    38. 38. Team<br />Scrum is not team building<br />You are what you eat<br />Play the release, look and feel right?<br />Four points inward<br />Cross-discipline, self-managing, self-organizing, mentoring<br />Distributed fragmentation<br />Build in Las Vegas, ship from Reno<br />
    39. 39. Review<br />Why Agile?<br />Scrum<br />Planning<br />Game Development on Scrum<br />
    40. 40. Credits<br />Sound Credit: Mixtikl by Intermorphic<br />Art Credit: 365 Strange Attractors by Joe Chavez<br />