Scrum - but... Agile Game Development in Small Teams
1 like712 views
The document discusses Scrum, an agile framework for managing product development. It describes Scrum roles like the Product Owner, Development Team, and Scrum Master. The Scrum process involves sprints, daily stand-ups, sprint planning and reviews. It also introduces an example game development team called Astro City working with Scrum.
1 of 27
Downloaded 10 times
![Scrum
“It defines a flexible, […] development strategy
where a development team works as a unit to reach
a common goal, challenges assumptions of the
traditional, sequential approach […], and enables
teams to self-organize by encouraging physical co-
location […] as well as daily face-to-face
communication […].”
wikipedia.org](https://image.slidesharecdn.com/scrum-but-160429111659/85/Scrum-but-Agile-Game-Development-in-Small-Teams-11-320.jpg)
![Scrum
“A key principle of scrum is its recognition that during
production processes, the customers can change
their minds about what they want and need (often
called requirements volatility) […].”
wikipedia.org](https://image.slidesharecdn.com/scrum-but-160429111659/85/Scrum-but-Agile-Game-Development-in-Small-Teams-12-320.jpg)
Ad
Recommended
Game Development Challenges
Game Development ChallengesNick Pruehs This document discusses challenges in game development based on Nick Prühs' experience. It covers the diversity of game types and roles involved in development. It also discusses art pipelines, game engines, physics examples, and lessons learned from developing the "Campus Buddies" social game. Key lessons include expecting API changes, using existing solutions, making testing and deployment easy, mocking network interactions, standardizing code style, using a feature-based project structure, prioritizing collaboration, listening to players, implementing tutorials, considering 2D animation, and addressing challenges with localization.
Game Programming 05 - Development Tools
Game Programming 05 - Development ToolsNick Pruehs The document outlines essential tools and workflows for game programming, emphasizing the importance of automated builds, API documentation generation, and game analytics. It discusses tools like Jenkins for automated builds, Javadoc and Doxygen for documentation, and StyleCop for maintaining code consistency. Additionally, it highlights how to track player engagement and performance metrics while providing insights on crash dump analysis techniques.
Eight Rules for Making Your First Great Game
Eight Rules for Making Your First Great GameNick Pruehs The document outlines eight essential rules for making a great video game, emphasizing the importance of easy testing, frequent deployment, a structured project layout, player feedback, immediate bug fixing, a focus on gameplay, learning from others, and a commitment to quality. Key strategies include setting up debugging tools early, creating a bullet-proof project structure, and prioritizing player experience from the start. The advice is backed by industry examples and emphasizes the complexity of game development.
Game Programming 13 - Debugging & Performance Optimization
Game Programming 13 - Debugging & Performance OptimizationNick Pruehs The document discusses techniques for debugging and performance optimization in game programming, emphasizing the need to start debugging immediately and avoid premature optimization. It covers various tools and strategies for tracking down and fixing bugs, as well as identifying performance bottlenecks related to GPU, CPU, and memory. Additionally, it highlights the importance of profiling before optimization and offers advice on managing memory leaks.
What Would Blizzard Do
What Would Blizzard DoNick Pruehs The document discusses Nick Prühs's background, highlighting his education and roles in game development, including work with Daedalic Entertainment and Slash Games. It emphasizes Blizzard's game development philosophies, particularly the importance of making games playable early and committing to quality despite challenges in testing and tool usage. Additionally, it touches on various technical aspects of Blizzard games, including file formats, data structures, and examples from titles like Hearthstone and Starcraft II.
Component-Based Entity Systems (Demo)
Component-Based Entity Systems (Demo)Nick Pruehs The document discusses game programming methodologies, specifically contrasting inheritance-based models with aggregation-based models, emphasizing the shortcomings of the former in terms of complexity and maintenance. It advocates for component-based entity systems, where game entities function as IDs managed by independent systems operating on components, enhancing extensibility and simplifying architecture. The author highlights the benefits of this approach, including better performance and ease of debugging, ultimately promoting a shift towards more adaptable game development frameworks.
Game Programming 01 - Introduction
Game Programming 01 - IntroductionNick Pruehs The document outlines key objectives for game programming, including learning from existing sources, effective project planning, and the importance of rapid iterations. It emphasizes the need for structured milestones in development, the significance of prototyping, and avoiding the reinvention of the wheel by utilizing existing resources. Additionally, it encourages critique and reflection through post-mortem analysis to enhance future projects.
School For Games 2015 - Unity Engine Basics
School For Games 2015 - Unity Engine BasicsNick Pruehs The document outlines a tutorial on game development using the Unity engine, focusing on essential concepts like game lifecycles, script creation, and asset management. It provides a step-by-step guide to building a simple game, including camera movement, player actions, and handling collisions. Additionally, it emphasizes the importance of learning from existing projects and encourages developers to experiment with their code.
Style & Design Principles 03 - Component-Based Entity Systems
Style & Design Principles 03 - Component-Based Entity SystemsNick Pruehs This document discusses component-based entity systems for game development. It describes the disadvantages of inheritance-based models, including deep class hierarchies that are difficult to develop, maintain and extend. It then introduces an aggregation-based approach using entities composed of independent components. This approach favors composition over inheritance and improves extensibility. Finally, it describes entity system architectures where components contain data and systems contain logic, improving performance, serialization and other capabilities. Overall it advocates for entity systems as an easier way to build, maintain and extend game object models.
Game Programming 08 - Tool Development
Game Programming 08 - Tool DevelopmentNick Pruehs The document outlines key concepts and guidelines related to game programming tool development, emphasizing the importance of UI/UX design and file formats such as XML, JSON, and YAML. It discusses architectural patterns like MVC and MVVM, alongside implementing features like undo/redo functionality in applications. Additionally, it covers design patterns, object-oriented design principles, and includes examples of memento patterns used for state restoration.
Maximize Your Production Effort (English)
Maximize Your Production Effort (English)slantsixgames This document discusses how to maximize production efficiency through efficient content authoring tools and pipelines for inter-studio asset development. It covers topics like infrastructure, content authoring, data conversion, game runtime considerations, and asset sharing. The key recommendations are to identify and reduce latency throughout the production pipeline, automate processes as much as possible, prioritize tool and workflow improvements, and treat outsourcing partners like internal team members to maximize output.
Y1 gd engine_terminology ig2 game engines
Y1 gd engine_terminology ig2 game enginesLewis Brierley The document is a glossary created by a student for a games design course. It contains definitions for 12 terms related to video game development that the student researched online. For each term, the student provided the definition they found, the relevant URL source, and whether and how they utilized the term in their own game production work. The glossary covers terms such as alpha/beta testing, game engines, debugging, physics, and anti-aliasing among others.
Y1 gd engine_terminology ig2 game engines
Y1 gd engine_terminology ig2 game enginesLewis Brierley The document is a glossary created by a student for a games design course. It contains definitions for 12 terms related to video game development that the student researched online. For each term, the student provided the definition they found, the relevant URL source, and whether and how they utilized the term in their own game production work. The glossary covers terms such as alpha/beta testing, game engines, lighting, and anti-aliasing among others.
Beyond TDD: Enabling Your Team to Continuously Deliver Software
Beyond TDD: Enabling Your Team to Continuously Deliver SoftwareChris Weldon The document discusses advanced practices for software development beyond Test-Driven Development (TDD), emphasizing continuous integration and delivery to enhance the software release process. It highlights the importance of rapid feedback, collaboration among all team members, and strategies like Minimum Viable Product and feature toggles to manage incomplete features. The overall goal is to eliminate barriers to release, facilitate regular deployments, and improve the team's efficiency and confidence in delivering software.
Game Programming 04 - Style & Design Principles
Game Programming 04 - Style & Design PrinciplesNick Pruehs The document outlines key principles and best practices for game programming style and design, emphasizing the importance of good code structure, naming conventions, and the use of consistent coding practices. It also discusses the design and use of types and members, the handling of exceptions, and guidelines for collections in programming. To achieve 'good code', methods such as pair programming, code reviews, and static code analysis are recommended.
Options for Entity interaction - Unite Copenhagen 2019
Options for Entity interaction - Unite Copenhagen 2019Unity Technologies The document discusses creating a first-person shooter (FPS) game in Unity, led by programmer Peter Andreasen. It highlights the challenges of implementing multiplayer features and the structure of the FPS sample code, emphasizing the use of samples for coding foundations. Additionally, it provides links to resources such as the FPS sample landing page and upcoming talks on netcode.
Confrontation Pipeline and SCons
Confrontation Pipeline and SConsslantsixgames Slant Six Games uses SCons as their data build system for games like SOCOM: Confrontation. SCons is a Python-based build tool that provides fast, correct, and extensible builds. It supports features like dependency tracking and shared caching that help optimize their large data builds. While SCons works well overall, challenges include slow initial dependency scanning for large asset trees and bottlenecks introduced by tools like Maya. Staged building and selective dependency analysis help address these issues.
How to Test PowerShell Code Using Pester
How to Test PowerShell Code Using PesterChris Wahl This document provides an overview of how to use Pester to test PowerShell code. Pester allows you to write unit tests for PowerShell scripts and functions. Tests are organized using Describe, Context, and It blocks. Describe blocks group related tests, Context blocks divide tests by scope, and It blocks define individual tests with inputs and expected outputs. The document includes examples of using Should statements to make assertions and leveraging Pester with build systems like AppVeyor for continuous integration. Resources for learning more about Pester and unit testing PowerShell code are also provided.
Drupal Continuous Integration with Jenkins - Deploy
Drupal Continuous Integration with Jenkins - DeployJohn Smith This document describes setting up Jenkins jobs to automate deploying code from a Git repository to different environments. It includes:
1. Creating a simple job that deploys code to a single server/environment using a deployment script.
2. Creating a generic job that deploys code to multiple servers/environments using parameters for the repository, branch, and environment.
3. A sample deployment script that would run on servers to check out the appropriate code from Git based on the job parameters.
Agile game #2 Scrum Card Game
Agile game #2 Scrum Card GameMykola Mytko Документ представляет информацию о предстоящих мероприятиях и мастер-классах от организации grow.org.ua, направленных на обучение технологиям менеджмента и улучшение работы команд с использованием Scrum. В нем перечислены даты, темы и тренеры, а также описаны активности, такие как игра Scrum Card Game. Основная цель заключается в повышении эффективности команд через практические и теоретические занятия.
Game Programming 03 - Git Flow
Game Programming 03 - Git FlowNick Pruehs The document outlines the Git Flow methodology for game programming, emphasizing the management of separate branches for features, releases, and hotfixes to streamline collaborative development. It describes the roles of main branches, such as 'master' and 'develop', and the purpose of supporting branches like feature, release, and hotfix branches. Key practices include merging strategies and maintaining clear workflows to facilitate efficient development and integration.
Game Programming 10 - Localization
Game Programming 10 - LocalizationNick Pruehs The document discusses the importance of game localization for reaching a global audience, highlighting types of game assets that require localization and outlining the localization process. It details best practices for localization, including encoding, handling localization keys, and preparing for localization testing. Additionally, it mentions the challenges of localizing different media types and provides options for packaging languages in games.
Game Programming 07 - Procedural Content Generation
Game Programming 07 - Procedural Content GenerationNick Pruehs The document discusses procedural content generation (PCG) in game development, outlining its objectives, categories, opportunities, and challenges. It provides various algorithms for generating game content, such as context-free grammars, genetic algorithms, and Perlin noise, while highlighting the importance of pseudo-random number generation in creating diverse and compelling levels. Additionally, it covers fundamental concepts like chunks, level layouts, and the implementation of level generation frameworks.
Tool Development A - Git
Tool Development A - GitNick Pruehs The document outlines the objectives of learning Git, covering version control systems, installation of Git and SourceTree, and basic operations like pulling, committing, and merging. It explains Git branching strategies, including main, feature, release, and hotfix branches, along with best practices for merging. References for further reading and contact information are also provided.
Game Programming 09 - AI
Game Programming 09 - AINick Pruehs Game Programming AI
This document discusses behavior trees, an approach to game AI architecture. Behavior trees split AI decision logic from actions and organize them into a directed tree structure. The root node executes logic which reports back as success, running, or failure. This passes control to child nodes. Key nodes include sequences which run children in order until failure, and selectors which run the first successful child. Behavior trees are modular, reusable, and can be data-driven to design AI visually without code. They have been successfully used in many games due to their flexibility and performance.
Game Programming 02 - Component-Based Entity Systems
Game Programming 02 - Component-Based Entity SystemsNick Pruehs The document discusses component-based entity systems for building game object models. It outlines some drawbacks of inheritance-based approaches, such as deep class hierarchies leading to call order issues. It then introduces an aggregation-based approach using entities, components, and systems. Entities are simple IDs, with all data and logic contained in independent, reusable components. Systems operate on components to implement game functionality without coupling. This approach has advantages like easy extensibility and multi-threading. Blueprints and attribute tables are discussed as ways to configure entities using components and data at runtime.
Game Programming 12 - Shaders
Game Programming 12 - ShadersNick Pruehs The document outlines the essential aspects of shader development and the graphics pipeline in modern GPUs. It covers key topics like CPU versus GPU performance, shader languages, and the stages of the graphics pipeline including vertex transformation, rasterization, and fragment processing. Additionally, it discusses lighting models and provides practical shader programming examples using Cg in Unity.
Game Programming 11 - Game Physics
Game Programming 11 - Game PhysicsNick Pruehs This document discusses the fundamentals of physics in game programming, focusing on kinematics, dynamics, rigid body collisions, and numerical integration methods. It covers concepts such as motion, forces, velocity, and the importance of using fixed time steps for accurate physics simulations. The document also elaborates on the properties of rigid bodies, collision response, and the calculations related to center of mass and moments of inertia.
Game Programming 06 - Automated Testing
Game Programming 06 - Automated TestingNick Pruehs The document outlines the essentials of automated testing in game programming, focusing on unit testing frameworks like NUnit for .NET and tooling for Unity. It discusses concepts such as test-driven development (TDD), practical examples of unit tests, and limitations of testing, including integration and embedded system challenges. Additionally, it includes references to testing in C++ with Google Test and Unreal Engine 4's automation testing methods.
Play the Customer Development Game
Play the Customer Development GameAdrian Howard This document discusses the principles of customer development and the lean startup methodology, emphasizing the importance of hypotheses and experimentation in validating business models. It includes references to tools like the Business Model Canvas and examples from companies like Zappos to illustrate these concepts. The document encourages a metric-first approach to development and suggests further reading to explore these ideas in depth.
More Related Content
What's hot (11)
Style & Design Principles 03 - Component-Based Entity Systems
Style & Design Principles 03 - Component-Based Entity SystemsNick Pruehs This document discusses component-based entity systems for game development. It describes the disadvantages of inheritance-based models, including deep class hierarchies that are difficult to develop, maintain and extend. It then introduces an aggregation-based approach using entities composed of independent components. This approach favors composition over inheritance and improves extensibility. Finally, it describes entity system architectures where components contain data and systems contain logic, improving performance, serialization and other capabilities. Overall it advocates for entity systems as an easier way to build, maintain and extend game object models.
Game Programming 08 - Tool Development
Game Programming 08 - Tool DevelopmentNick Pruehs The document outlines key concepts and guidelines related to game programming tool development, emphasizing the importance of UI/UX design and file formats such as XML, JSON, and YAML. It discusses architectural patterns like MVC and MVVM, alongside implementing features like undo/redo functionality in applications. Additionally, it covers design patterns, object-oriented design principles, and includes examples of memento patterns used for state restoration.
Maximize Your Production Effort (English)
Maximize Your Production Effort (English)slantsixgames This document discusses how to maximize production efficiency through efficient content authoring tools and pipelines for inter-studio asset development. It covers topics like infrastructure, content authoring, data conversion, game runtime considerations, and asset sharing. The key recommendations are to identify and reduce latency throughout the production pipeline, automate processes as much as possible, prioritize tool and workflow improvements, and treat outsourcing partners like internal team members to maximize output.
Y1 gd engine_terminology ig2 game engines
Y1 gd engine_terminology ig2 game enginesLewis Brierley The document is a glossary created by a student for a games design course. It contains definitions for 12 terms related to video game development that the student researched online. For each term, the student provided the definition they found, the relevant URL source, and whether and how they utilized the term in their own game production work. The glossary covers terms such as alpha/beta testing, game engines, debugging, physics, and anti-aliasing among others.
Y1 gd engine_terminology ig2 game engines
Y1 gd engine_terminology ig2 game enginesLewis Brierley The document is a glossary created by a student for a games design course. It contains definitions for 12 terms related to video game development that the student researched online. For each term, the student provided the definition they found, the relevant URL source, and whether and how they utilized the term in their own game production work. The glossary covers terms such as alpha/beta testing, game engines, lighting, and anti-aliasing among others.
Beyond TDD: Enabling Your Team to Continuously Deliver Software
Beyond TDD: Enabling Your Team to Continuously Deliver SoftwareChris Weldon The document discusses advanced practices for software development beyond Test-Driven Development (TDD), emphasizing continuous integration and delivery to enhance the software release process. It highlights the importance of rapid feedback, collaboration among all team members, and strategies like Minimum Viable Product and feature toggles to manage incomplete features. The overall goal is to eliminate barriers to release, facilitate regular deployments, and improve the team's efficiency and confidence in delivering software.
Game Programming 04 - Style & Design Principles
Game Programming 04 - Style & Design PrinciplesNick Pruehs The document outlines key principles and best practices for game programming style and design, emphasizing the importance of good code structure, naming conventions, and the use of consistent coding practices. It also discusses the design and use of types and members, the handling of exceptions, and guidelines for collections in programming. To achieve 'good code', methods such as pair programming, code reviews, and static code analysis are recommended.
Options for Entity interaction - Unite Copenhagen 2019
Options for Entity interaction - Unite Copenhagen 2019Unity Technologies The document discusses creating a first-person shooter (FPS) game in Unity, led by programmer Peter Andreasen. It highlights the challenges of implementing multiplayer features and the structure of the FPS sample code, emphasizing the use of samples for coding foundations. Additionally, it provides links to resources such as the FPS sample landing page and upcoming talks on netcode.
Confrontation Pipeline and SCons
Confrontation Pipeline and SConsslantsixgames Slant Six Games uses SCons as their data build system for games like SOCOM: Confrontation. SCons is a Python-based build tool that provides fast, correct, and extensible builds. It supports features like dependency tracking and shared caching that help optimize their large data builds. While SCons works well overall, challenges include slow initial dependency scanning for large asset trees and bottlenecks introduced by tools like Maya. Staged building and selective dependency analysis help address these issues.
How to Test PowerShell Code Using Pester
How to Test PowerShell Code Using PesterChris Wahl This document provides an overview of how to use Pester to test PowerShell code. Pester allows you to write unit tests for PowerShell scripts and functions. Tests are organized using Describe, Context, and It blocks. Describe blocks group related tests, Context blocks divide tests by scope, and It blocks define individual tests with inputs and expected outputs. The document includes examples of using Should statements to make assertions and leveraging Pester with build systems like AppVeyor for continuous integration. Resources for learning more about Pester and unit testing PowerShell code are also provided.
Drupal Continuous Integration with Jenkins - Deploy
Drupal Continuous Integration with Jenkins - DeployJohn Smith This document describes setting up Jenkins jobs to automate deploying code from a Git repository to different environments. It includes:
1. Creating a simple job that deploys code to a single server/environment using a deployment script.
2. Creating a generic job that deploys code to multiple servers/environments using parameters for the repository, branch, and environment.
3. A sample deployment script that would run on servers to check out the appropriate code from Git based on the job parameters.
Viewers also liked (19)
Agile game #2 Scrum Card Game
Agile game #2 Scrum Card GameMykola Mytko Документ представляет информацию о предстоящих мероприятиях и мастер-классах от организации grow.org.ua, направленных на обучение технологиям менеджмента и улучшение работы команд с использованием Scrum. В нем перечислены даты, темы и тренеры, а также описаны активности, такие как игра Scrum Card Game. Основная цель заключается в повышении эффективности команд через практические и теоретические занятия.
Game Programming 03 - Git Flow
Game Programming 03 - Git FlowNick Pruehs The document outlines the Git Flow methodology for game programming, emphasizing the management of separate branches for features, releases, and hotfixes to streamline collaborative development. It describes the roles of main branches, such as 'master' and 'develop', and the purpose of supporting branches like feature, release, and hotfix branches. Key practices include merging strategies and maintaining clear workflows to facilitate efficient development and integration.
Game Programming 10 - Localization
Game Programming 10 - LocalizationNick Pruehs The document discusses the importance of game localization for reaching a global audience, highlighting types of game assets that require localization and outlining the localization process. It details best practices for localization, including encoding, handling localization keys, and preparing for localization testing. Additionally, it mentions the challenges of localizing different media types and provides options for packaging languages in games.
Game Programming 07 - Procedural Content Generation
Game Programming 07 - Procedural Content GenerationNick Pruehs The document discusses procedural content generation (PCG) in game development, outlining its objectives, categories, opportunities, and challenges. It provides various algorithms for generating game content, such as context-free grammars, genetic algorithms, and Perlin noise, while highlighting the importance of pseudo-random number generation in creating diverse and compelling levels. Additionally, it covers fundamental concepts like chunks, level layouts, and the implementation of level generation frameworks.
Tool Development A - Git
Tool Development A - GitNick Pruehs The document outlines the objectives of learning Git, covering version control systems, installation of Git and SourceTree, and basic operations like pulling, committing, and merging. It explains Git branching strategies, including main, feature, release, and hotfix branches, along with best practices for merging. References for further reading and contact information are also provided.
Game Programming 09 - AI
Game Programming 09 - AINick Pruehs Game Programming AI
This document discusses behavior trees, an approach to game AI architecture. Behavior trees split AI decision logic from actions and organize them into a directed tree structure. The root node executes logic which reports back as success, running, or failure. This passes control to child nodes. Key nodes include sequences which run children in order until failure, and selectors which run the first successful child. Behavior trees are modular, reusable, and can be data-driven to design AI visually without code. They have been successfully used in many games due to their flexibility and performance.
Game Programming 02 - Component-Based Entity Systems
Game Programming 02 - Component-Based Entity SystemsNick Pruehs The document discusses component-based entity systems for building game object models. It outlines some drawbacks of inheritance-based approaches, such as deep class hierarchies leading to call order issues. It then introduces an aggregation-based approach using entities, components, and systems. Entities are simple IDs, with all data and logic contained in independent, reusable components. Systems operate on components to implement game functionality without coupling. This approach has advantages like easy extensibility and multi-threading. Blueprints and attribute tables are discussed as ways to configure entities using components and data at runtime.
Game Programming 12 - Shaders
Game Programming 12 - ShadersNick Pruehs The document outlines the essential aspects of shader development and the graphics pipeline in modern GPUs. It covers key topics like CPU versus GPU performance, shader languages, and the stages of the graphics pipeline including vertex transformation, rasterization, and fragment processing. Additionally, it discusses lighting models and provides practical shader programming examples using Cg in Unity.
Game Programming 11 - Game Physics
Game Programming 11 - Game PhysicsNick Pruehs This document discusses the fundamentals of physics in game programming, focusing on kinematics, dynamics, rigid body collisions, and numerical integration methods. It covers concepts such as motion, forces, velocity, and the importance of using fixed time steps for accurate physics simulations. The document also elaborates on the properties of rigid bodies, collision response, and the calculations related to center of mass and moments of inertia.
Game Programming 06 - Automated Testing
Game Programming 06 - Automated TestingNick Pruehs The document outlines the essentials of automated testing in game programming, focusing on unit testing frameworks like NUnit for .NET and tooling for Unity. It discusses concepts such as test-driven development (TDD), practical examples of unit tests, and limitations of testing, including integration and embedded system challenges. Additionally, it includes references to testing in C++ with Google Test and Unreal Engine 4's automation testing methods.
Play the Customer Development Game
Play the Customer Development GameAdrian Howard This document discusses the principles of customer development and the lean startup methodology, emphasizing the importance of hypotheses and experimentation in validating business models. It includes references to tools like the Business Model Canvas and examples from companies like Zappos to illustrate these concepts. The document encourages a metric-first approach to development and suggests further reading to explore these ideas in depth.
Agile for game_development
Agile for game_developmentJoe Chavez This document discusses using agile methodologies like Scrum for game development. It provides an overview of key agile terms like stories, sprints, and retrospectives. It explains that agile aims to smooth out the development process and accommodate change. Scrum is presented as a common agile framework that uses short iterations to deliver working software frequently for feedback. The document also covers how lean principles can be applied to formalize content production phases in game development.
Starting agile game_testing
Starting agile game_testingUlas Karademir This document discusses agile game development. It addresses challenges like test automation management, process tool centralization and control, and visibility/traceability for compliance efforts. It also discusses defining "Done" to include testing, having nightly/continuous builds, and ensuring needed tools like Bugzilla and build robots are available. Quality is discussed in terms of completeness, correctness, and functionality/engineering/adaptability qualities. Black-box and white-box testing techniques are mentioned. The document advises QA managers to tell developers what is working and assume the rest is not, rather than telling them what is not working.
Game Models - A Different Approach
Game Models - A Different ApproachNick Pruehs The document discusses game object systems, highlighting the limitations of inheritance-based models and the advantages of aggregation-based models instead. It advocates for entity systems where game entities are simplified to just IDs, promoting ease of maintenance and extensibility. Additionally, it covers implementation aspects within Unity3D, future prospects, and reference materials for further reading.
Sacled agile a game-changer - Rahul Gawale
Sacled agile a game-changer - Rahul GawaleGirdharee Saran The document outlines BMC's transformation journey from traditional methodologies to a scaled agile framework (SAFe) to enhance productivity and responsiveness. It highlights the challenges faced during this transition, including system integration issues, and showcases the benefits achieved such as increased team productivity and quicker delivery. BMC emphasizes the importance of adopting agile practices on a larger scale to meet fast-changing customer needs.
Instructions slides for the GetKanban.com Kanban Board Game
Instructions slides for the GetKanban.com Kanban Board GameYuval Yeret This document describes how to play the Kanban game to learn Kanban concepts. It lists the story, story types, daily steps, and control chart as part of the game. It also provides contact information for getting help with Kanban, including an email, phone number, and links to the author's social media and blog where more Kanban information can be found.
Entity System Architecture with Unity - Unite Europe 2015
Entity System Architecture with Unity - Unite Europe 2015Simon Schmid The document discusses the use of the Entitas framework for entity system architecture in Unity, addressing pain points such as testability, code sharing, and querying. It outlines various components, systems, and optimization techniques, including reactive systems and the use of code generation for efficiency. Additionally, it highlights the framework's advantages, such as determinism and improved simulation speed.
Designing an actor model game architecture with Pony
Designing an actor model game architecture with PonyNick Pruehs The document discusses the design of an actor model game architecture using Pony, emphasizing its object-oriented, capabilities-secure features. It explains the asynchronous nature of actors and provides examples of actor behaviors, such as eating in an aardvark actor. Additionally, it highlights the type safety, memory safety, and other safety features of Pony while offering resources for further learning.
Agile ones game
Agile ones gameSeb Rose The document describes how to play an Agile game in teams. Each team has a backlog of story cards that must progress from backlog to done. Team members take turns working on stories by rolling dice, with each roll of 1 representing a unit of work. The game involves iterations where teams work through stories, have retrospectives, and implement additional mechanics like swarming, defects, work in progress limits, and buffers.
Ad
Similar to Scrum - but... Agile Game Development in Small Teams (20)
Introduction into Scrum
Introduction into Scrummsorin The document provides an introduction to Scrum, an agile framework designed to enhance product development by enabling rapid iteration and delivery of software. It outlines the roles within a Scrum team, the significance of sprints, and the importance of self-organized teams that prioritize business value. Additionally, it references Scrum's historical context, its adoption across various enterprises, and describes key practices such as sprint planning, daily scrums, and retrospective meetings.
scrum
scrumNoman sial This document provides an overview of scrum, an agile project management framework. It defines key scrum roles like the product owner, scrum master, and scrum team. It also outlines the scrum process which involves sprint planning meetings, daily stand-up meetings, and working in 2-4 week sprints to develop incremental deliverables. The document notes major companies that use scrum and the advantages of increased flexibility, quality, and clear project status, while also acknowledging potential disadvantages like lack of a final plan and challenges in change management.
Black Marble Introduction To Scrum
Black Marble Introduction To ScrumBusinessQuests The document provides an introduction to the Scrum framework, its origins in Agile development, and its implementation across various industries for product development. It outlines key components such as roles (Product Owner, Scrum Master, Team), processes (sprints, daily scrums, retrospective), and artifacts (product backlog, sprint backlog). The emphasis is on self-organizing teams that prioritize delivering high-value software in short iterations to adapt to changing requirements.
Introduction to Scrum
Introduction to Scrumtimmcowan This document provides an introduction and overview of Scrum, an agile framework for managing product development projects. It discusses the origins and principles of Scrum, key roles like the Product Owner and Scrum Master, ceremonies such as sprint planning and retrospectives, artifacts like the product and sprint backlogs, and how Scrum has been implemented successfully in organizations like Salesforce.com. The document also notes characteristics of Scrum projects and how it compares to traditional sequential development models.
Agile scrum training
Agile scrum trainingRajakrishnan S, MCA,MBA,MA Phil,PMP,CSM,ISTQB-Test Mgr,ITIL This document provides an introduction to Agile and Scrum. It discusses the principles of Agile, including the Agile Manifesto. Scrum is presented as an Agile framework consisting of roles, ceremonies, and artifacts. The roles of Product Owner, Scrum Master, and Engineering Team are defined. Ceremonies like Sprint Planning, Daily Scrum, Sprint Review and Retrospective are explained. Artifacts such as Product Backlog, Sprint Backlog and Burn Down Chart are also summarized. User stories, estimation techniques, and definitions of done are covered as part of requirements and planning in Scrum.
The Scrum Model
The Scrum ModelDamian T. Gordon The document provides an overview of the Scrum model for agile software development. Scrum divides projects into short sprints of 2-4 weeks to focus development. It utilizes daily stand-up meetings, sprint planning and reviews, and retrospectives. Key roles include the product owner who prioritizes the backlog, the scrum master who facilitates the process, and the cross-functional development team. Scrum aims to provide structure while allowing for flexibility, feedback and adapting to changes.
Redistributable Intro To Scrum
Redistributable Intro To ScrumErwin Verweij Scrum is an agile framework for managing product development that focuses on iterative delivery of working software in short cycles called sprints. It involves self-organizing cross-functional teams, prioritized backlogs to track requirements, and daily stand-up meetings. The goal is to rapidly and repeatedly deliver the highest business value in the shortest time through a flexible, holistic and collaborative approach.
Introduction To Scrum Presentation for beginners
Introduction To Scrum Presentation for beginnersssuser92ac1f This document provides an introduction to the Scrum framework, emphasizing its agile process that prioritizes delivering high business value quickly through iterative work cycles called 'sprints.' It describes key roles within Scrum, including the Product Owner and Scrum Master, and outlines the purpose and structure of various ceremonies and artifacts involved in the process. Additionally, it highlights Scrum's application across a range of industries and projects, showcasing its effectiveness in promoting collaboration and adapting to change.
Scrum workshop - September 7, 2012
Scrum workshop - September 7, 2012MrAlexRosales The document outlines the fundamentals of Agile methodology, focusing on Scrum as a framework for iterative project management. Key elements include the roles of product owner, scrum master, and team, as well as ceremonies such as sprint planning, reviews, and retrospectives. The emphasis is on fostering collaboration, adaptability, and delivering business value through frequent, incremental software releases.
Seminar On Scrum
Seminar On ScrumAbhishek Kumar Singh The document provides an overview of Scrum, an agile software development framework. It defines Scrum, discusses its history and introduction. It describes the Scrum framework, including roles like Product Owner and Scrum Master, events like sprint planning and review, and artifacts like product and sprint backlogs. It outlines the Scrum process and provides examples of Scrum applications. It discusses advantages like adaptability and faster delivery, and disadvantages like lack of documentation. It concludes that Scrum is popular for experienced teams that can self-organize, but requires strict adherence to be effective.
Seminar on Scrum
Seminar on ScrumAbhishek Kumar Singh The document provides an overview of Scrum, an agile software development framework. It defines Scrum, discusses its history and introduction. It describes the Scrum framework, including roles like Product Owner and Scrum Master, events like sprint planning and review, and artifacts like product and sprint backlogs. It outlines the Scrum process and discusses applications of Scrum as well as its advantages and disadvantages. The document concludes that Scrum is an effective framework but requires experience and strict adherence to be successful.
Agile Scrum Mastery: Learn How To Bring Complex Projects To life!
Agile Scrum Mastery: Learn How To Bring Complex Projects To life!Mindbowser Inc The document outlines the principles and practices of Scrum, a framework for developing software through self-organizing teams. It details Scrum roles, artifacts, and events, as well as the structure and importance of various sprints, including Sprint 0 for project initiation. Challenges and exceptions in the Scrum process are also discussed, emphasizing the collaborative nature and flexibility necessary for successful project management.
An Introduction to Scrum: presented at PyTexas 2012
An Introduction to Scrum: presented at PyTexas 2012Tomo Popovic This document provides an introduction to Scrum, an agile framework for project management. It defines key Scrum roles like the Product Owner and Scrum Master. Scrum uses short iterations called sprints to incrementally develop working software. Teams self-organize during daily stand-up meetings and track progress using artifacts like the product backlog and sprint backlog. Scrum aims to deliver business value continuously through inspection and adaptation at the end of each sprint.
An Introduction to Scrum
An Introduction to Scrummbalas2 Scrum is an agile framework for managing product development that focuses on iterative delivery of working software. It involves short development cycles called sprints that typically last 2-4 weeks. Teams are self-organizing and work is planned and tracked using artifacts like a product backlog, sprint backlog, and daily stand-up meetings. The goal is to frequently deliver working, tested software to gain early customer feedback and continuously adapt to changing requirements.
Quick intro to scrum agile
Quick intro to scrum agileRobert Sayegh The document discusses Agile and Scrum frameworks for software development. It defines key aspects of Scrum including roles like Product Owner and Scrum Master, ceremonies like sprint planning and daily standups, and artifacts like product and sprint backlogs. Scrum was designed to address uncertainties in specifications and changing requirements by having self-organizing cross-functional teams work in short sprints to deliver working software.
Intro To Scrum
Intro To Scrumscottycn The document introduces Scrum as an agile methodology focused on delivering high business value through iterative development in 'sprints'. It emphasizes self-organizing teams that prioritize features and adapt to changes, and it outlines key Scrum roles, processes, and ceremonies for effective project management. Scrum has been utilized by major companies for various software development projects, demonstrating its versatility and effectiveness in managing collaborative workflows.
agile-and-scrum-methodology.pptx
agile-and-scrum-methodology.pptxvenkatvemu2 The role of a QA tester on a Scrum team includes:
1) Participating in sprint planning and retrospectives to provide input on testing needs and improvements.
2) Testing software increments throughout the sprint to find issues early.
3) Communicating regularly with developers through daily standups and demos.
4) Ensuring quality by developing test cases, conducting exploratory testing, and automating tests.
5) Helping clarify requirements and identify ambiguities.
PSPO(Scrum Product Owner) Preparation Quick Guide.pdf
PSPO(Scrum Product Owner) Preparation Quick Guide.pdfSwadesh Bhushan, PMP® The document is a comprehensive guide on Scrum, detailing its framework, roles (Product Owner, Scrum Master, Scrum Team), events, and principles like Agile values and the 'inspect and adapt' concept. It emphasizes the Scrum framework's focus on productivity, accountability, and collaboration, providing a structured approach for software development through iterations and cross-functional team dynamics. Additionally, it covers practical aspects such as user stories, effort estimation techniques, the importance of the Definition of Done (DoD), and the collaborative nature of Scrum teams.
technical seminar topic on scrum also called as PSM .
technical seminar topic on scrum also called as PSM .Shanthisri Kothagundla Scrum is an agile project management framework designed to handle complex projects with changing requirements, allowing teams to deliver high-value products iteratively. It consists of defined roles (product owner, scrum master, and development team), events (sprints and meetings), and values promoting self-organization and transparency. Scrum enhances productivity and adaptability in various sectors, including software development and organizational management.
Introduction to Scrum framework
Introduction to Scrum framework Prabhat Kumar Scrum is an agile framework for managing complex projects. It utilizes empirical process control through short development cycles called sprints, where self-organizing cross-functional teams work to deliver a potentially shippable product increment. Key roles include the product owner, scrum master, and development team. Ceremonies like sprint planning, daily stand-ups, sprint reviews, and retrospectives provide transparency and opportunities to inspect and adapt the process as needed.
Ad
More from Nick Pruehs (10)
Unreal Engine Basics 06 - Animation, Audio, Visual Effects
Unreal Engine Basics 06 - Animation, Audio, Visual EffectsNick Pruehs Chapter 6 of Unreal Engine Basics focuses on animation, audio, and visual effects within Unreal Engine, covering key concepts like animation blueprints, blend spaces, and sound cues. The chapter explains how to control character animations, manage sound assets, and utilize particle systems, providing practical examples and methods for implementation. Additionally, it includes an assignment that involves creating various animation and audio settings for a character, along with resources for further learning.
Unreal Engine Basics 05 - User Interface
Unreal Engine Basics 05 - User InterfaceNick Pruehs Chapter 5 of the Unreal Engine Basics covers the user interface, focusing on the differences between the Slate and UMG frameworks, and how to create both basic and complex UI components. It discusses built-in widgets, panel types, and widget properties, providing guidance on creating modular UIs and events. The chapter concludes with practical assignments for implementing a game HUD and main menu, along with references for further learning.
Unreal Engine Basics 04 - Behavior Trees
Unreal Engine Basics 04 - Behavior TreesNick Pruehs This document covers the basics of behavior trees in Unreal Engine, focusing on their setup and use for AI players. It explains tree components, including composites and tasks, and outlines the creation and functionality of AI controllers. Additionally, an assignment is provided to reinforce learning by implementing a behavior tree for AI interactions.
Unreal Engine Basics 03 - Gameplay
Unreal Engine Basics 03 - GameplayNick Pruehs Chapter 3 of Unreal Engine Basics focuses on gameplay programming, specifically exposing class fields and functions to blueprints, and covers concepts like UPROPERTY and UFUNCTION macros for class and function specifications. It explains how to manage components, spawn and destroy actors, handle events and collisions in C++, and implement damage systems within actors. The chapter also includes practical assignments for enhancing gameplay mechanics and references for further reading.
Unreal Engine Basics 02 - Unreal Editor
Unreal Engine Basics 02 - Unreal EditorNick Pruehs Chapter 2 of the Unreal Engine Basics covers the Unreal Editor, focusing on level creation and actor management. It details player input binding, character movement properties, and asset naming conventions, as well as provides practical coding examples for implementing gameplay mechanics. The chapter concludes with an assignment to implement character movement and input handling for a game project.
Unreal Engine Basics 01 - Game Framework
Unreal Engine Basics 01 - Game FrameworkNick Pruehs This document serves as an introduction to the Unreal Engine, detailing its capabilities, components, and the structure of its codebase. It covers essential topics such as UObjects, Actors, Game Modes, and coding standards necessary for developing within the Unreal environment. Additionally, it provides a roadmap for setting up a development environment and creating a basic C++ project with outlined assignments for practice.
Game Programming - Cloud Development
Game Programming - Cloud DevelopmentNick Pruehs The document outlines the principles of developing scalable cloud-based backend architectures for online games, emphasizing the importance of managing load and resources efficiently. It introduces concepts like traditional load balancing, the benefits of cloud services, and the use of virtual actors to enhance game backend responsiveness and scalability. Additionally, it provides references and encourages an interactive review session to reinforce understanding of key terms and concepts.
Game Programming - Git
Game Programming - GitNick Pruehs This document provides an overview of version control systems and how to use Git. It discusses local and centralized version control before focusing on distributed version control with Git. The document then demonstrates how to install Git and SourceTree, create a GitHub account, add and commit files to a repository, pull and push changes, view history and more. It also covers advanced Git topics like branching, merging, and divergent histories.
Game Programming 00 - Exams
Game Programming 00 - ExamsNick Pruehs The document outlines the exam requirements and guidelines for game programming, focusing on creating a reusable code library in a chosen programming language. Students will be evaluated on code quality, reusability, documentation, and project structure, with additional points for unit tests and static analysis. All work must be submitted with proper public API documentation, and earlier commits will be considered for assessment.
Tool Development 10 - MVVM, Tool Chains
Tool Development 10 - MVVM, Tool ChainsNick Pruehs This document discusses the Model-View-ViewModel (MVVM) and Model-View-Controller (MVC) architectural patterns, emphasizing their separation of concerns and advantages in application development. It also covers data binding, validation, conversion, cancelling events in WPF, and the significance of tool chains in the development process. Additionally, it highlights best practices for desktop applications, including UI/UX design and testing methodologies.
Recently uploaded (11)
Upgrade Your Skills with Leadership Coaching in Toronto
Upgrade Your Skills with Leadership Coaching in Torontoimprovacanada Unlock your potential with leadership coaching services in Toronto. Our training programs are designed to enhance your leadership skills and drive success.
1 Samuel 15.1-3 7-13 22-23 Foolish Defiance GPBC 06.15.25.pdf
1 Samuel 15.1-3 7-13 22-23 Foolish Defiance GPBC 06.15.25.pdfLazarou Richard Bible Study lesson on 1 Samuel 15 based on the Gospel Project curriculm.
UNI Concept Proposal UN Green Helmets Ministry of Peace Foundational Security
UNI Concept Proposal UN Green Helmets Ministry of Peace Foundational SecurityLHelferty This concept proposal from UnityNet International introduces a paradigm shift in global peace and security, moving beyond traditional military defense.
It advocates for the creation of "Green Helmets" or "Living Helmets," which are Regenerative Peacekeeping Forces (#RPFs) focused on regenerative development, climate resilience, and foundational human security.
These forces would deploy with resources like green infrastructure and water systems to assist communities, rather than weapons, aiming to prevent conflict by addressing root causes such as resource scarcity and climate instability.
The proposal suggests establishing a Ministry of Peace and Foundational Security within member states to coordinate these efforts and reallocate national budgets to prioritize regenerative, civilian peacekeeping alongside military defense.
Key Topics:
-Regenerative Peacekeeping Forces
-Ministry of Peace
-Green Helmets
-Climate Resilience
-Foundational Security
Steering Excellence in Turbulent Times: A Strategic Governance Toolkit
Steering Excellence in Turbulent Times: A Strategic Governance Toolkitexec7 In today’s volatile, uncertain, complex, and ambiguous (VUCA) world, strategic governance is no longer optional. It's imperative.
This SlideShare from TEXEM, UK equips executives, board members, and business leaders with a practical governance toolkit to navigate turbulence with resilience, clarity, and confidence.
Explore actionable insights on:
- Strengthening governance structures in crisis
- Enabling adaptive leadership in times of disruption
- Enhancing stakeholder trust and boardroom decision-making
- Developing strategic foresight and agile planning capabilities
- Building resilient organisations that thrive—not just survive
Whether you're a C-suite executive, policy leader, or aspiring changemaker, this guide offers tools to drive excellence, accountability, and strategic transformation in a fast-changing world.
Use this toolkit to lead with boldness, agility, and purpose—no matter the storm.
To register for TEXEM’s executive programme that builds boardroom excellence, visit: www.texem.co.uk/strategic-governance-and-leadership-steering-excellence-in-turbulent-times
3 Fedral Enterprise Architecture Framework (Eid Mohammad Ibrahimi).pdf
3 Fedral Enterprise Architecture Framework (Eid Mohammad Ibrahimi).pdfEidMohammad6 The FEAF is a unique & high level management framework.
SpatzAI Micro-Conflict Resolution Toolkit - Fairer Teamwork Globally
SpatzAI Micro-Conflict Resolution Toolkit - Fairer Teamwork GloballyDesmond Sherlock Workplace conflicts don’t always start with blowups—they begin as tiny spats, snide remarks, or ignored frustrations. SpatzAI is a real-time chat app and team review platform that empowers employees to address micro-conflicts before they escalate.
Materi Financial Awareness Accelerate (Helmi Wandara).pptx
Materi Financial Awareness Accelerate (Helmi Wandara).pptxDindaAyu424485 How do you think about money
Scrum - but... Agile Game Development in Small Teams
- 1. Scrum – but... Agile Game Development In Small Teams Nick Prühs
- 2. About Me “Best Bachelor“ Computer Science Kiel University, 2009 Master Games Hamburg University of Applied Sciences, 2011 Lead Programmer Daedalic Entertainment, 2011-2012 Co-Founder slash games, 2013 Microsoft MVP 2015
- 3. Thank you for being here…
- 4. … not here.
- 5. Scrum
- 6. Scrum
- 7. Scrum
- 8. Scrum
- 9. Scrum
- 10. Scrum “Scrum is an iterative and incremental agile software development framework for managing product development.” wikipedia.org
- 11. Scrum “It defines a flexible, […] development strategy where a development team works as a unit to reach a common goal, challenges assumptions of the traditional, sequential approach […], and enables teams to self-organize by encouraging physical co- location […] as well as daily face-to-face communication […].” wikipedia.org
- 12. Scrum “A key principle of scrum is its recognition that during production processes, the customers can change their minds about what they want and need (often called requirements volatility) […].” wikipedia.org
- 13. Scrum “Scrum adopts an empirical approach—accepting that the problem cannot be fully understood or defined, focusing instead on maximizing the team's ability to deliver quickly, to respond to emerging requirements and to adapt to evolving technologies and changes in market conditions.” wikipedia.org
- 14. Scrum Roles Product Owner • Represents stakeholders • Accountable for ensuring that the team delivers • Writes user stories • Prioritizes the product backlog
- 15. Scrum Roles Development Team • Delivers Potentially Shippable Increments (PSIs) • Cross-functional • Self-organizing
- 16. Scrum Roles Scrum Master • Removes obstacles, ensuring team can deliver • Enforces scrum process • Team facilitator
- 18. Scrum Process https://en.wikipedia.org/wiki/Scrum_(software_development)
- 19. Scrum Schedule Termintyp Termin Dauer Beteiligte Sprint Kick Off Mittwoch, 12:00 2 h Alle Sprint Planning Mittwoch, 15:00 2 h Team, Scrum Master Sprint Retrospektive Mittwoch, 17:00 1 h Team, Scrum Master Daily Stand-Up täglich, 11:00 15 min Team, Scrum Master Sprint Pre-Planning Dienstag, 14:00 2 h Product Owner, Scrum Master, Technical Director Sprint Review Mittwoch, 10:00 2h Alle
- 20. Scrum Schedule Termintyp Termin Dauer Beteiligte Sprint Kick Off Mittwoch, 12:00 2 h Alle Sprint Planning Mittwoch, 15:00 2 h Team, Scrum Master Sprint Retrospektive Mittwoch, 17:00 1 h Team, Scrum Master Daily Stand-Up täglich, 11:00 15 min Team, Scrum Master Sprint Pre-Planning Dienstag, 14:00 Freitag, 14:00 2 h Product Owner, Scrum Master, Technical Director Sprint Review Mittwoch, 10:00 2h Alle
- 21. Astro City
- 22. Astro City
- 23. Astro City
- 24. Astro City – Team Julian (Business) Andreas (Game Design) Ibo (Art) Lisa (Art) Ruben (Programming) Christian (Programming) Frank (Programming) Nick (Programming)