Marionette StudioMarionette StudioMarionette StudioMarionette Studio
  • Features
  • Pricing
  • Learn
    • Video tutorials
    • User guide
    • Videos
    • 2D Animations
  • Blog
  • Demo
  • Login
  • START ANIMATING
  • agile game development - quick overview
  • traditional approach
  • the agile approach
  • agile game development
  • traditional planning
  • traditional planning
  • traditional planning
  • agile planning
  • what is agile
  • agile manifesto to game development
  • why agility for game development
  • finding the fun in your game
  • project noise level
  • project noise level scrum
  • project noise level
  • project noise level scrum
  • reducing waste
  • where scrum comes from
  • what is scrum
  • scrum project community
  • scrum project community game development team
  • scrum game project community scrum master
  • scrum project community product -owner
  • scrum product owner responsabilities
  • scrum master responsabilities
  • scrum game development team responsabilities
  • game development scrum overview
  • game development print goals
  • game development sprint backlog
  • game development sprint length
  • game development daily scrum
  • game development deliver improved game
  • scrum is iterative
  • always deliver in scrum
  • sequantial versus overlapping development
  • sample game product backlog
  • game product backlog iceberg
  • game development user stories
  • game development user stories
  • game development sprint cycle
  • game development sprint planning meeting
  • game development daily scrum meeting
  • game development sprint review meeting
  • game development sprint retrospective meeting
  • game development sprint backlog
  • burndown charts
  • game development burndown chart
  • game development burndown chart
  • board tasks for agile game development
  • game development reciprocical comitment
  • no changes during a sprint
  • abnormal termination for a sprint
  • release planning on long projects
  • scrum of scrums
  • agile game development tools
  • q&a about agile game development
  • agile game development bibliography

Agile Game Development – A Quick Overview

By Raluca | Agile Game Development, Finding FUN in games, Game Development Team, Game Planning, Game Release Planning, Indie Games, Project Management for Games, Theoretical Concepts and Observables, Tutorial | 0 comment | 18 August, 2016 | 3

In this post I would like to share with you an overview of the Agile Game Development.

I was wondering how agile processes would be applicable to game development and I was very happy to find cool stuff over the internet about this subject. In the last part of this post I shared a few links that helped me to build this presentation about Agile Game Development. If you want to know more about this I definitely encourage you to go through bibliography because there are some amazing videos describing how agile is applied to game development.

 

What is Agile Game Development ?

 

Agile is an approach for developing products (in this case: games) using short iterations. The main idea is not making the whole project from start to finish, but making small features for the current project in small periods of time. In this way the results of each iteration are used to adjust the project plan:

  • each iteration is like a short project in itself
  • uses “inspect and adapt” practices to adjust the goals and measure progress
what is agile game development

Figure 1. Traditional approach vs. Agile approach

 

Agile Game Development adopts the agile planning over traditional planning. In Figure 2. a comparison between these two methods is displayed.

 

Rather than doing all of one thing at a time, is better to do a little of everything all the time. :) 

 

Let’s say that we have a great idea of a game and we want to implement it. In traditional planning we should step through those 4 phases above stated: Discover, Design, Develop and Test. Once a phase is completed, then we follow the original plan step by step by starting from one point and plan the directed work since a final goal is achieved. When the game is finished and we are ready to ship it to our users we risk to face a big problem: we have the perfect game played by nobody. At this point, we are forced to change the plans and try to do things that our users want. That’s why our End could not match the initially defined Goal. This means that when we start to make a game we deal with a big “Cone of Uncertainty”. Agile planning comes with small goals set for small periods of time and forces us to step through all those 4 steps each iteration (about 2-4 weeks long). At the end of each iteration we take a breath and look backward and try to conclude the results. Using these results and the users need we can adjust our initial plan and create some new goals. This process iterates until our deadline is achieved.

 

agile planning

Figure 2. Traditional planning vs. Agile planning

 

 

Agile approaches help us respond to unpredictability through incremental, iterative work cadences and empirical feedback from users. When we start to deliver a project we deal with different types of noise level, depending on what we need to do (i.e. game requirements) and how we do it (i.e. technology used). Based on these two dimensions we can classify our project in 4 types of problems:

  • Simple – we can solve the problem by applying a predefined plan
  • Complicated – we can split the problem in smaller simple problems
  • Complex – we can use an empirical approach in order to see if the results are going in the right way
  • Anarchy – totally chaos

 

project noise level - agile game development

Figure 3. When to choose the SCRUM process (source: Strategic Management and Organizational Dynamics by Ralph Stacey in Agile Software Development with Scrum by Ken Schwaber and Mike Beedle)

 

A game is part of the complex class because the output is influenced by so many external factors and we need to inspect ourselves as soon as possible, try to get feedback for our game as early as we can and adapt our plans according to our results. And here comes the SCRUM process to help us.

 

What is SCRUM ?

 

SCRUM is an iterative and incremental Agile process that produces demonstrable working software every 2-4 weeks. Being results- and commitment-oriented it has a long history of success on a wide variety of projects,  including game development.

Based on a product backlog that contains many features, the SCRUM process helps us to establish some goals for small periods of time that are called sprints. Usually sprints are 2-4 weeks long. Once a sprint goal is defined, then a set of tasks can be taken for development in order to achieve that goal. At the end of the sprint, the team is able to ship an incrementally improved game. The result is fully functional and testable by users so that each developed feature can receive that feedback that helps the game development team to find the FUN needed in order to have a successful game on the market.

 

agile game development using scrum

Figure 4. The SCRUM process (agile game development)

SCRUM facilitates feature iteration, allowing teams to deliver polished, tuned and integrated features which can be used to test the creative quality of the game throughout its development, allowing the team to incorporate audience feedback as early as possible in the development process.

 

The SCRUM project community involves 3 roles with different responsibilities:

  • Product Owner

    • Is responsible for the profitability of the product (ROI)
    • Prioritizes features according to market value
    • Can change features and priority every sprint
    • Accepts or rejects work results
    • Defines the features of the product, decides on release date and content
  • Scrum Master

    • Ensures that the team is fully functional and productive
    • Shields the team from external interferences
    • Ensures that the process is followed.
    • Enables close cooperation across all roles and functions and removes barriers
    • Participates in daily scrum, sprint review and planning meetings
  • The Development Team

    • Cross-functional, seven plus/minus two ideally    full-time members
    • Selects the sprint backlog
    • Has the right to do everything within the boundaries of the project guidelines to reach the sprint goal
    • Organizes itself and its work
    • Demos work results to the Product Owner
scrum community in agile game development

Figure 5. SCRUM project community (roles and responsibilities)

 

Meetings, or ceremonies are an important part of agile game development:

Sprint Planning Meeting

  • Product owner describes priorities
  • Team breaks product backlog items (features) into tasks
  • Team commits to some amount of work

Daily Scrum

  • Three questions:
    • What did you do yesterday?
    • What will you do today?
    • What’s in your way?
  • A commitment between peers, not a management status meeting

Sprint Review Meeting

  • Team demonstrates what was accomplished
  • 2-hour prep time rule
  • No PowerPoint!
  • Anyone can attend

Sprint Retrospective

  • Focus on continuous improvement
  • Look back at the last sprint and ask what would we like to:
    • What went well
    • What we need to improve & actions
    • Impediments

 

The sprint cycle

Figure 6. The sprint cycle

Bibliography

  • https://www.frontrowagile.com/courses/introduction-to-agile-game-development/overview
  • https://www.scribd.com/doc/313657474/SCRUM-in-managementul-proiectelor-software
  • http://www.develop-online.net/analysis/the-four-pillars-of-agile-game-development/0117636
  • http://sbgames.org/papers/sbgames10/computing/short/Computing_short19.pdf
  • https://www.frontrowagile.com/courses/introduction-to-agile-game-development/overview
  • https://www.youtube.com/watch?v=DQzrFiMDoko
  • https://www.youtube.com/watch?v=nqPZnzh9680
  • https://www.youtube.com/watch?v=zbb6r9CGSgI
  • https://www.youtube.com/watch?v=P3hYlGp2ago
  • https://www.youtube.com/watch?v=RPwACSngWGI
  • http://uagamedev.blogspot.ro/p/about.html
  • http://blog.agilegamedevelopment.com/2013/02/leading-creative-self-organizing-teams.html
  • http://www.slideshare.net/mikecohn/agile-and-scrum-for-video-game-development-22871287
  • http://stackify.com/what-is-scrum-development-vs-rugby/
  • https://www.youtube.com/watch?v=RPwACSngWGI
  • http://www.brandnewgame.com/2014/11/agile-game-design/
  • http://screenshots.en.sftcdn.net/en/scrn/3332000/3332616/game-downloader-05-535×535.png
  • http://stackify.com/what-is-scrum-development-vs-rugby/
  • http://gifmaker.me/ (helped me to make the GIF images)

Hopefully this article makes sense to you. If you need further details please let me a comment and I will get back to you. Happy game delivery with agile game development!

Agile, Game development, Game planning, Game release, Indie, Indie games, SCRUM
Raluca

Raluca

More posts by Raluca

Related Post

  • skyppy-fox-running-and-falling-animated-video

    Engage your audience with animated videos

    By Sorin | 1 comment
    The best way of expressing your message in the digital world is through animated videos. Animation gives you the freedom to target your audience in a compelling, powerful and exciting way! You can express yourRead more

  • The Marionettes - 2D characters - Marionette Studio

    Meet The Marionettes !

    By Raluca | 0 comment

      We would proudly  like to introduce our newest characters, The Marionettes family. Having the touch of the retro style, our animated family will kick off the animation templates that will be introduced very soon inRead more

  • 3 essential tools to create an animation in 3 minutes

    3 Essentials Tools to create a successful animation in 3 minutes

    By Raluca | 6 comments
    Whenever you are part of marketing, media, advertising, entertainment, gaming or any other industry that requires expressing a message, animated content has become essential in grabbing people's attention. Giving you an answer on how toRead more

  • Pixel art effect in Marionette Studio

    How to easily make a Pixel Art animation

    By Raluca | 0 comment
    Pixel art is a form of digital art, created with the help of software tools, where images are created on the pixel level. Most of graphics for computers (8-bit and 16-bit), video game consoles and graphingRead more

  • animators games

    Essential skills required for an animator

    By Codrina | 1 comment
    Animator skills play an important role in the creation of a video game, a movie or a television show. Animators are artists that create animations, special effects, etc using computer softwares and electronic tools. AnRead more

Leave a Comment

Cancel reply

Your email address will not be published. Required fields are marked *


Related Posts

  • What is cel animation?
    5 March, 2020
    0

    What is Cel Animation?

  • Halloween decor - the witch house - emojer
    26 October, 2018
    0

    3 Best Halloween decors for your stories

  • screen2-v2
    17 July, 2018
    0

    Announcing Emojer – Animated emoji with just one photo

  • skyppy-fox-running-and-falling-animated-video
    26 February, 2018
    1

    Engage your audience with animated videos

Categories

2D Animation 2D animation for games 2016 Trends Advertising Agile Game Development Algorithms Animation Animation for Dummies Animation techniques Animation tips Animation Tools for Marketers Characters Create character Creative work Design Digital Art Digital Design Features Finding FUN in games Freebies Game Development Team Game Planning Game Release Planning How To Indie Games Inktober Marionette Studio Marionette Studio Updates Marketing Project Management for Games Rigging Skeletal animation Sketches The Marionettes Theoretical Concepts and Observables Tutorial Uncategorized

Latest activity

  • Linwood on Animating with Marionette Studio
  • Raluca on 3 Essentials Tools to create a successful animation in 3 minutes
  • jameel on 3 Essentials Tools to create a successful animation in 3 minutes
  • Animation Training surat on Top 5 blogs to learn animation from
  • Ravali Reddy on Engage your audience with animated videos

MARIONETTE STUDIO

+1.408.769.5590
support@marionettestudio.com
3739 Balboa St # 1221
San Francisco, California, USA
94121

2D ANIMATION

Features
Pricing
Request a Demo
Contact Us
Software Change Log
Education Partner Program

LEARNING & DOCS

Showcase
Tutorials
User guide
Blog
Videos

FOLLOW US

Get the latest news & updates!
© 2018 Marionette Studio, Inc. Terms and Conditions | Privacy Policy | Cookies Policy
  • Features
  • Pricing
  • Learn
    • Video tutorials
    • User guide
    • Videos
    • 2D Animations
  • Blog
  • Demo
  • Login
  • START ANIMATING
Marionette Studio
By using this site, you agree to Marionette Studio's use of cookies to improve your experience. Learn more on our Cookie Information page. Accept Read More