SlideShare a Scribd company logo
1 of 46
Download to read offline
Beyond Agile
Pitfalls and misconceptions
when working with SCRUM & Co
in video game development
Ralf C. Adam
This lecture was first held in April 2015 at the Quo Vadis Game Developer
Conference in Berlin/GERMANY. The presentation may not include all
original materials shown during this speech (pictures, videos etc.) and is
solely meant as a summary and handout. All copyrights of presented
materials belong to their respective owners.
DISCLAIMER
• Ralf C. Adam
• Executive Producer at flaregames
• >20 years in the games industry
• Contributed to >80 games
• Tutor at Games Academy in Berlin & Frankfurt
• Hobbys: Movies, Games, Gadgets, Soccer, Karaoke
ABOUT MYSELF
• This talk is about agile project management
methods and concepts and how to apply them
to game development
• I will give examples of what to avoid – as well
as some best practices
ABOUT THIS TALK
WHAT IS AGILE?
There‘s no such
thing as doing Agile!
WHAT IS AGILE?
• Correct Wording:
o Agile development practices or methods
o Agile development teams
o Develop software with agility
• Agile is an adjective not a noun
• It‘s an attribute to something we do…
• …not THE something
• Right now big hype around it
• Everybody talks about „being agile“
• Often feels like buzzword bingo
• Also lots of money involved
(Trainings, expensive certifications etc.)
• Originally comes from traditional IT
• Question: Is it really 100% adaptable
for video game development?
WHAT IS AGILE?
[agile]: Relating to or denoting a method of project
management, used especially for software development,
that is characterized by the division of tasks into short
phases of work and frequent reassessment and adaption
of plans: agile methods replace high-level design with
frequent redesign. Contrasted with waterfall (adjective).
SOURCE: oxforddictionairies.com
WHAT IS AGILE?
• By the way: It is not a new invention!
• Game developement has always
been an agile processof Missile Command (1980) and Tempest
»Pick an idea. Write up a game proposal. Get
it OK'd by management. Take a couple of
weeks to bring up a playable simple version.
Management reviews that and OKs it or axes
it. If OK'd, continue with the whole game.
Regular reviews by management to make sure
still fun. Kill the game if not.«
Dave Theurer (1980)
Designer of Tempest and
Missile Command
WHAT IS AGILE?
BEFORE AGILE THERE WAS RAD
• In 1991 James Martin wrote „Rapid Application
Development“ (RAD)
• Princicples described in there:
o Risk reduction
o Early prototyping
o Finding problems earlier in life-cycle (cheaper to fix)
o Emphasizes necessity of adjusting requirements
throughout development
o Also emphasize a flexible process and planning
• See also: Rapid Development – Steve McConnell (1996)
THE AGILE MANIFESTO
Lean FDD DSDM
Crystal XP (Extr. Prog.) SCRUM
The Agile Manifesto (2001)
AGILE METHODS
Lean
• Father = Taiichi Ono (1988), Production Lead Toyota
• Comes from Lean Manufacturing. Set of principles for
achieving quality, speed & customer alignment
• No set of fixed Rules or Methods
• It‘s a Philosophy/Company Culture
• Lean Company e.g. can use SCRUM as specific method
• Princicples:
o Eliminate Waste
o Improve Quality
o Reduce Costs
o Deliver Fast
o Respect People
o Constantly improve Skills & Production Processes
• Feature Driven Development
• High Level Method
• Allows for other methods on lower level
• Purely focusses on the Delivery of Features
AGILE METHODS
FDD
• Advancement of RAD
• Rather strict set of Rules
• Acknowledges cooperation with
e.g PRINCE2 & PMI
• Focus on Timeboxing and MoSCoW
prioritization (Must have, Should have,
Could have, Won’t have)
AGILE METHODS
DSDM
• Developed in 1990’ies by Cockburn
• Focused on people, iteration, community,
skills, talents, communications
• More framework than rule set
• Creed: People above process
• Very tolerant
AGILE METHODS
Crystal
• Focus on Programming
• Emphasizes Team-Work
• Focus on changing customer
requirements
• More open to change (than e.g. SCRUM)
• Focus on certain coding practices such
as Testing, Feedback, Pair Programming,
Simplicity, Test Driven Development etc.
AGILE METHODS
XP (Extr. Prog.)
AGILE METHODS
SCRUM
30 days
24 hours
Product Backlog
As prioritized by PRODUCT OWNER
Sprint Backlog
Backlog tasks
expanded
by TEAM
Potentially Shippable
Product Increment
Daily
Scrum
Meeting
Source: Adapted from Agile Software
Development with Scrum by Ken Schwaber
and Mike Beedle
KANBAN
• Method for Steering Production
• Once Again: Toyota/Taichi Ono
(Part of the Lean Process)
• Japanese: word Kan means "signal" and "ban“
means "card"
• Therefore Kanban refers to "signal cards“
• Starbucks is a Kanban-System -> the cup is the Kanban
• The cup-ban acts as an order form that can encode
most combinations that a barista should expect
• SCRUM-Boards are often traditional Kanban-Boards
PITFALLS
So… what is
the problem?
PITFALLS
• What are potential problems/pitfalls of agile methods?
• Mostly by the example of SCRUM (as it‘s the most used one)
• BTW: I do not know any game development studio that
uses SCRUM 100% by the Book
• Most teams just use parts of it – the once that work for them
• SCRUM Purists call this approach SCRUMBut
• They blame wrong usage when it‘s not working out
• Which I personally think is at least questionable…
THE IT vs GAMES DILEMMA
• Software Development Processes = traditional IT
• We are not IT Development
• We are not making SAP Databases
• We are making Games
• There are fundamental differences between the two
THE IT vs GAMES DILEMMA (CONT.)
• The Customer (Publisher) does not make the Design/Specification
doc (compared to traditional IT)
• The user (player) does not give feedback until Game is out or
focus group tests with Closed Alpha/Beta
• No Design in the World can „describe“ fun
• True: that‘s why an iterative approach for „Making it fun“ is a
good concept (Prototypes/Pre-Production)
• But: if you treat game development solely with methods that
were meant for creating a database – you easily end up creating
just a database, but not a game!
THE DEADLINE PARADOXON
• Working with a Publisher ALWAYS means: There are Deadlines
• Good reasons for that: Planning for Marketing, QA slots,
Console/Apple Submission etc.
• Not committing to deadlines does not work with Publishers
• SCRUM Purist argue the product is potentially shippable after
every Sprint – in theory that would mean:
o Just stop developing at the deadline and release the game, no
matter what
o In whatever state it is at the end of the last Sprint
o The goal of game development is not "to finish a game" but
"to finish a good game"
THE FEATURE PROBLEM
• A feature may take longer than just one sprint
• Many larger features don't work with the concept of being
'potentially shippable' after every Sprint.
• Sometimes there are features you either do entirely in one
go or not at all, and that may just take the time it needs and
can not be squeezed into a sprint
• Other problem: a large feature may only work together
reasonably with another feature linked to it
• Both have to be there to make it meaningful. Half a feature-set
might be just a broken game
THE SUM OF ALL FEATURES
• A game is more than the sum of ist features
• SCRUM encourages for divding devlopement into little chunks
• This often ends up in a gathering of working features – without
any soul or meaning
• It takes a vision and an overall plan how these features shall work
together
• I‘ve seen many SCRUM teams that were just thinking about the
current sprint
• It was even kind of „forbidden“ to them to think about the next
sprint or upcoming features
THE SUM OF ALL FEATURES (CONT.)
• Product backlog: not a good tool to transport an overall vision
(nor a good vision for features itself)
• This does not work for Game Development
• It‘s like shooting a movie and on the set you start writing the
script, scene by scene while you shoot
• 1st rule of Hollywood Script-Writing: You start developing a script
with the end in your mind (= the vision)
THE DAILY STAND-UP CHARADE
• Generally: Daily Standup is a good thing
• But can easily go wrong and derail
• Lot of people don‘t want to talk there, others talk too much
(usually always the same ones)
• SCRUM Stand-Ups can create an interrogation atmosphere
• What if people are not in the same location?
• Question most teams forget in Stand-Up: What‘s the status
for the Outsourcing teams/partners?
THE VISION-KEEPER COMPLICATION
• Who owns the Game Vision?
• Problem in many SCRUM teams: missing or unclear Vision Keeper
• Or: Vision Keeper is NOT the Product Owner
• Or: Product Owner is NOT the Game Designer but a „Suit“
• SCRUM Team = all team members have the same saying
• Does hardly work in Game Development (or similar creative
processes/media)
• Again: Try to imagine SCRUM on a movie set
• US TV series: Showrunner Princicple in combination with
Writer‘s Room
THE SCALING NIGHTMARE
SCRUM
Team
SCRUM
Team
SCRUM
Team
SCRUM
Team
SCRUM of
SCRUMS
Game Project
Physics
Team
AI
Team
Online-Team
UI/UX-TeamProduct
Owner
Product
Owner
Lead
Product
Owner
THE SCALING NIGHTMARE (CONT.)
• SCRUM recommends team has size of 7 to 9
• Less you don‘t need this structure
• More you can not let it run „self managed“
• But what‘s with bigger Game Teams/Studios?
• Then suddenly SCRUM gets very hierarchical very fast
(see slide before)
THE SCALING NIGHTMARE (CONT.)
• SCRUM of SCRUMS (somebody in a blog called it „the old idea of
communists‘ cells (Russian Bolsheviks organized themselves in
“cells” of about 10 to hide from the management of the day)
• Results in LOTS of meetings, makes decision making super-slow
• To quote another blog: “In a nutshell Scrum can add unnecessary
overhead & can encourage product management anti-patterns
that lead to bad decisions, frustration and a deceiving sense of
control.”
THE CUSTOMER QUESTION
• Most agile methods preach user & customer involvement
throughout the whole development cycle
• Who’s the user and who’s the customer in Game Development?
• Unlike e.g. SAP we can’t put UI framework/mask out and ask
users (=gamers) to give feedback
• Does hardly work for games without context
• Publisher also can’t be involved like traditional
Product Owners
• Publisher usually has no time for such an involvement, nor
the expertise (the publisher producer might have, but not all
other stakeholders)
THE BURNDOWN CHART COMPLICATION
• Goal of Burn-down Chart: To measure Velocity during Sprint
• But…
o Premise: always the same people
o Premise: that always work the same speed
• So Question is: What do you actually measure?
• How good/fast the people work?
• Or how good their estimates were?
• My Experience: Burn-Down Chart one of the first things
most teams start to not update anymore once they are
running out of time
THE „INDIVIDUALS OVER PROCESSES“ LIE
»Individuals and
interactions over
processes & tools«
1st core from the Manifesto for
Agile Software Development (2001)
»ScrumButs are reasons why teams
can’t take full advantage of Scrum to
solve their problems and realize the
full benefits of product development
using Scrum. Every Scrum role, rule,
and timebox is designed to provide
the desired benefits and address
predictable recurring problems.«
SCRUM.ORG
vs
THE „INDIVIDUALS OVER PROCESSES“ LIE (CONT.)
• Typical SCRUM statement:
• “You don’t see good results with Scrum
because you don’t do enough of it/don‘t
use it right!”
• Such statements encourage the opposite
of the (very pragmatic) principles of the
original Agile manifesto (see slide before)
• Reason: It‘s all about certificates (=MONEY!)
• Every two years you have to renew your
SCRUM Master/Product Owner etc.
BEST PRACTICE
Some Best
Practices…
VISION STATEMENT
• Vision Statement is fundamental…
• …even when using agile methods
• If you do not know the goal you will not find the way
o What is it that you want to build?
o What will be the core gameloop the player will
constantly face & play?
o What are the primary and secondary gameplay
elements?
• It‘s hard to „iterate“ towards a vision – how do you know
when you‘re there?
THE „HITCHCOCK APPROACH“
• Always go from the big Picture into smaller pieces (like Hitchcock)
• Don’t start creating a Backlog without clear a Vision Document
• Don’t start creating small feature implementations if you do not
know the big picture
• Actually the basic idea of starting with “Epics” and then breaking
them down into User Stories is pretty good and exactly the right
approach in that context
• Just make sure you have the big Picture first, before you start
writing User Stories (potential downside of “Agile methods as they
come from IT: you start with implementation of stuff that you
think is clearly enough defined already)
PRE-PRODUCTION
• Never start without a proper Pre-Production
• Topic big enough for another talk in iteself
• Briefly: spend rather too much time in Pre-Prod than
too little (upstream vs downstream cost)
• One of the many advantages: Team is smaller
• Pre-Production itself well suited for agile methods
as it is per definition about prototyping and
iteration
VERTICAL-SLICE
• Final Proof of production quality and fun
• Important when working with a Publisher
• Final alignment on what it is that the Publisher
(and ultimately the player) gets in the end in
terms of quality level and fun
FEATURE-CREEP
• American Game Design vs. German Game Design:
o US-Design: Feature is not fun? It gets kicked out…
o German-Design: Feature is not fun? Add two additional
features to support the feature that is not workin
• Create a small feature set that is deeply polished – not the
other way round
• Once again: potantial trap of Agile-Methods as they preach
„Delivery of Features“
• I‘ve seen too many teams (and publishers!) that were only
focussed on creating features rather than fun
CANBAN-BOARDS
• Kanban Boards (e.g. Trello) are great and can be used and adapted
for project management in multiple ways
• Next Slides show how we used it at Virgin Lands for instance to
plan an entire Movie Production
• In this example: Texturing Workflow of all Movie Assets
• Kanban generally is very helpful especially for creation and
tracking of graphic Assets
• Most Movie Production use a tool called „Shotgun“
CANBAN-BOARDS
CANBAN-BOARDS
THERE IS NO „TOO SIMPLE“
• With regards to Project Management Methods…
• …listen to Albert Einstein: Make it as simple as
possible but not simpler!
• It’s not about creating a Leviathan-Process!
• Trust your instincts – if you think your method
sucks, than it most certainly does!
TEAM ACCEPTANCE
• Last but not least: acceptance of the methods used is more
important than their potential efficency or any dogmatic
framework
• Tailoring your process to your situation has always been the
most agile option of all
• The whole team should agree to any process and workflow
• If the team thinks a workflow is stupid – change it!
• They will not follow it otherwise anyway

More Related Content

What's hot

Ppt taller scrum v5 no ejercicios
Ppt taller scrum v5 no ejerciciosPpt taller scrum v5 no ejercicios
Ppt taller scrum v5 no ejerciciosHiberus Tecnologia
 
DevOps Roadshow - continuous delivery and release management
DevOps Roadshow - continuous delivery and release managementDevOps Roadshow - continuous delivery and release management
DevOps Roadshow - continuous delivery and release managementMicrosoft Developer Norway
 
What happens to engineering manager in agile world
What happens to engineering manager in agile worldWhat happens to engineering manager in agile world
What happens to engineering manager in agile worldNaveen Indusekhar
 
Data Science Development Lifecycle - Everyone Talks About it, Nobody Really K...
Data Science Development Lifecycle - Everyone Talks About it, Nobody Really K...Data Science Development Lifecycle - Everyone Talks About it, Nobody Really K...
Data Science Development Lifecycle - Everyone Talks About it, Nobody Really K...Rising Media Ltd.
 
Lean & Agile Performance Measurement: Metrics, Models, & Measures
Lean & Agile Performance Measurement: Metrics, Models, & MeasuresLean & Agile Performance Measurement: Metrics, Models, & Measures
Lean & Agile Performance Measurement: Metrics, Models, & MeasuresDavid Rico
 
How to be a great scrum master
How to be a great scrum masterHow to be a great scrum master
How to be a great scrum masterDaniel Shupp
 
End-to-End CI/CD at scale with Infrastructure-as-Code on AWS
End-to-End CI/CD at scale with Infrastructure-as-Code on AWSEnd-to-End CI/CD at scale with Infrastructure-as-Code on AWS
End-to-End CI/CD at scale with Infrastructure-as-Code on AWSBhuvaneswari Subramani
 
Release Train Engineer - the Master Scrum Master
Release Train Engineer  - the Master Scrum Master Release Train Engineer  - the Master Scrum Master
Release Train Engineer - the Master Scrum Master Mia Horrigan
 
Agile Transformation Strategy
Agile Transformation StrategyAgile Transformation Strategy
Agile Transformation StrategySemen Arslan
 
Lean and Agile SAP
Lean and Agile SAPLean and Agile SAP
Lean and Agile SAPJason Fair
 
SRE 101 (Site Reliability Engineering)
SRE 101 (Site Reliability Engineering)SRE 101 (Site Reliability Engineering)
SRE 101 (Site Reliability Engineering)Hussain Mansoor
 
Rancher 2.0 - Complete Container Management Platform
Rancher 2.0 - Complete Container Management PlatformRancher 2.0 - Complete Container Management Platform
Rancher 2.0 - Complete Container Management PlatformSebastiaan van Steenis
 
The Power of Azure DevOps
The Power of Azure DevOpsThe Power of Azure DevOps
The Power of Azure DevOpsJeff Bramwell
 
Scrum vs Kanban | What are the differences between Scrum and Kanban | Edureka
Scrum vs Kanban | What are the differences between Scrum and Kanban | EdurekaScrum vs Kanban | What are the differences between Scrum and Kanban | Edureka
Scrum vs Kanban | What are the differences between Scrum and Kanban | EdurekaEdureka!
 
Why Limit WIP?
Why Limit WIP?  Why Limit WIP?
Why Limit WIP? LeanKit
 

What's hot (20)

Ppt taller scrum v5 no ejercicios
Ppt taller scrum v5 no ejerciciosPpt taller scrum v5 no ejercicios
Ppt taller scrum v5 no ejercicios
 
CANARY DEPLOYMENT
CANARY DEPLOYMENTCANARY DEPLOYMENT
CANARY DEPLOYMENT
 
DevOps Roadshow - continuous delivery and release management
DevOps Roadshow - continuous delivery and release managementDevOps Roadshow - continuous delivery and release management
DevOps Roadshow - continuous delivery and release management
 
What happens to engineering manager in agile world
What happens to engineering manager in agile worldWhat happens to engineering manager in agile world
What happens to engineering manager in agile world
 
Data Science Development Lifecycle - Everyone Talks About it, Nobody Really K...
Data Science Development Lifecycle - Everyone Talks About it, Nobody Really K...Data Science Development Lifecycle - Everyone Talks About it, Nobody Really K...
Data Science Development Lifecycle - Everyone Talks About it, Nobody Really K...
 
Lean & Agile Performance Measurement: Metrics, Models, & Measures
Lean & Agile Performance Measurement: Metrics, Models, & MeasuresLean & Agile Performance Measurement: Metrics, Models, & Measures
Lean & Agile Performance Measurement: Metrics, Models, & Measures
 
How to be a great scrum master
How to be a great scrum masterHow to be a great scrum master
How to be a great scrum master
 
Kanban VS Scrum
Kanban VS ScrumKanban VS Scrum
Kanban VS Scrum
 
Agile Scrum Methodology
Agile Scrum MethodologyAgile Scrum Methodology
Agile Scrum Methodology
 
TDD and BDD and ATDD
TDD and BDD and ATDDTDD and BDD and ATDD
TDD and BDD and ATDD
 
End-to-End CI/CD at scale with Infrastructure-as-Code on AWS
End-to-End CI/CD at scale with Infrastructure-as-Code on AWSEnd-to-End CI/CD at scale with Infrastructure-as-Code on AWS
End-to-End CI/CD at scale with Infrastructure-as-Code on AWS
 
Release Train Engineer - the Master Scrum Master
Release Train Engineer  - the Master Scrum Master Release Train Engineer  - the Master Scrum Master
Release Train Engineer - the Master Scrum Master
 
Scrum - Agile a brief history
Scrum - Agile a brief historyScrum - Agile a brief history
Scrum - Agile a brief history
 
Agile Transformation Strategy
Agile Transformation StrategyAgile Transformation Strategy
Agile Transformation Strategy
 
Lean and Agile SAP
Lean and Agile SAPLean and Agile SAP
Lean and Agile SAP
 
SRE 101 (Site Reliability Engineering)
SRE 101 (Site Reliability Engineering)SRE 101 (Site Reliability Engineering)
SRE 101 (Site Reliability Engineering)
 
Rancher 2.0 - Complete Container Management Platform
Rancher 2.0 - Complete Container Management PlatformRancher 2.0 - Complete Container Management Platform
Rancher 2.0 - Complete Container Management Platform
 
The Power of Azure DevOps
The Power of Azure DevOpsThe Power of Azure DevOps
The Power of Azure DevOps
 
Scrum vs Kanban | What are the differences between Scrum and Kanban | Edureka
Scrum vs Kanban | What are the differences between Scrum and Kanban | EdurekaScrum vs Kanban | What are the differences between Scrum and Kanban | Edureka
Scrum vs Kanban | What are the differences between Scrum and Kanban | Edureka
 
Why Limit WIP?
Why Limit WIP?  Why Limit WIP?
Why Limit WIP?
 

Viewers also liked

Getting_Started_with_Alfresco_Records_Management_Enterprise.pdf
Getting_Started_with_Alfresco_Records_Management_Enterprise.pdfGetting_Started_with_Alfresco_Records_Management_Enterprise.pdf
Getting_Started_with_Alfresco_Records_Management_Enterprise.pdftechecm
 
Getting_Started_with_Alfresco_Records_Management_Enterprise.pdf
Getting_Started_with_Alfresco_Records_Management_Enterprise.pdfGetting_Started_with_Alfresco_Records_Management_Enterprise.pdf
Getting_Started_with_Alfresco_Records_Management_Enterprise.pdftechecm
 
Rayong real estate attractions : Hin Suay Nam Sai resort estate
Rayong real estate attractions : Hin Suay Nam Sai resort estateRayong real estate attractions : Hin Suay Nam Sai resort estate
Rayong real estate attractions : Hin Suay Nam Sai resort estateSunrise Property Thailand
 
Comunicazione obblighi normativi
Comunicazione obblighi normativiComunicazione obblighi normativi
Comunicazione obblighi normativiLuciano Minerva
 
CHinh phục mục tiêu
CHinh phục mục tiêuCHinh phục mục tiêu
CHinh phục mục tiêuSon Nguyen
 
Fundraising 101 for the Game Sector
Fundraising 101 for the Game SectorFundraising 101 for the Game Sector
Fundraising 101 for the Game SectorPaul Heydon
 
Canyon Ranch | Health Spa & Resort
Canyon Ranch | Health Spa & ResortCanyon Ranch | Health Spa & Resort
Canyon Ranch | Health Spa & ResortKashyap Shah
 
[ETUDE] Labellisation et santé connectée (IPSOS)
[ETUDE] Labellisation et santé connectée (IPSOS) [ETUDE] Labellisation et santé connectée (IPSOS)
[ETUDE] Labellisation et santé connectée (IPSOS) AG2R LA MONDIALE
 

Viewers also liked (15)

Act 4-encuesta (1)
Act 4-encuesta (1)Act 4-encuesta (1)
Act 4-encuesta (1)
 
Getting_Started_with_Alfresco_Records_Management_Enterprise.pdf
Getting_Started_with_Alfresco_Records_Management_Enterprise.pdfGetting_Started_with_Alfresco_Records_Management_Enterprise.pdf
Getting_Started_with_Alfresco_Records_Management_Enterprise.pdf
 
Getting_Started_with_Alfresco_Records_Management_Enterprise.pdf
Getting_Started_with_Alfresco_Records_Management_Enterprise.pdfGetting_Started_with_Alfresco_Records_Management_Enterprise.pdf
Getting_Started_with_Alfresco_Records_Management_Enterprise.pdf
 
калейдоскоп февраль 2016
калейдоскоп февраль 2016калейдоскоп февраль 2016
калейдоскоп февраль 2016
 
3- NIC Teaming
3- NIC Teaming3- NIC Teaming
3- NIC Teaming
 
презентация
презентацияпрезентация
презентация
 
Images
ImagesImages
Images
 
Trump DEF(2)
Trump DEF(2)Trump DEF(2)
Trump DEF(2)
 
Rayong real estate attractions : Hin Suay Nam Sai resort estate
Rayong real estate attractions : Hin Suay Nam Sai resort estateRayong real estate attractions : Hin Suay Nam Sai resort estate
Rayong real estate attractions : Hin Suay Nam Sai resort estate
 
Comunicazione obblighi normativi
Comunicazione obblighi normativiComunicazione obblighi normativi
Comunicazione obblighi normativi
 
Tday programme 040416
Tday programme 040416Tday programme 040416
Tday programme 040416
 
CHinh phục mục tiêu
CHinh phục mục tiêuCHinh phục mục tiêu
CHinh phục mục tiêu
 
Fundraising 101 for the Game Sector
Fundraising 101 for the Game SectorFundraising 101 for the Game Sector
Fundraising 101 for the Game Sector
 
Canyon Ranch | Health Spa & Resort
Canyon Ranch | Health Spa & ResortCanyon Ranch | Health Spa & Resort
Canyon Ranch | Health Spa & Resort
 
[ETUDE] Labellisation et santé connectée (IPSOS)
[ETUDE] Labellisation et santé connectée (IPSOS) [ETUDE] Labellisation et santé connectée (IPSOS)
[ETUDE] Labellisation et santé connectée (IPSOS)
 

Similar to Beyond agile - Pitfalls & misconceptions when working with SCRUM & Co | Ralf C. Adam

2019-CertiFUNcation-Hacking-Agile-not-a-tech-talk
2019-CertiFUNcation-Hacking-Agile-not-a-tech-talk2019-CertiFUNcation-Hacking-Agile-not-a-tech-talk
2019-CertiFUNcation-Hacking-Agile-not-a-tech-talkTYPO3 CertiFUNcation
 
Agile, not just for software
Agile, not just for softwareAgile, not just for software
Agile, not just for softwareJohn Paz
 
Morph your mindset for Continuous Delivery, Agile Roots 2014
Morph your mindset for Continuous Delivery,  Agile Roots 2014Morph your mindset for Continuous Delivery,  Agile Roots 2014
Morph your mindset for Continuous Delivery, Agile Roots 2014lisacrispin
 
TDD - Seriously, try it! (updated '22)
TDD - Seriously, try it! (updated '22)TDD - Seriously, try it! (updated '22)
TDD - Seriously, try it! (updated '22)Nacho Cougil
 
Agile Scrum Training Process
Agile Scrum Training ProcessAgile Scrum Training Process
Agile Scrum Training ProcessClarion Marketing
 
22-AnOverviewOfScrum.pptx
22-AnOverviewOfScrum.pptx22-AnOverviewOfScrum.pptx
22-AnOverviewOfScrum.pptxHelenCandy2
 
Scrum levels danny_kovatch_agile_sparks
Scrum levels danny_kovatch_agile_sparksScrum levels danny_kovatch_agile_sparks
Scrum levels danny_kovatch_agile_sparksAgileSparks
 
It's XP Stupid (2019)
It's XP Stupid (2019)It's XP Stupid (2019)
It's XP Stupid (2019)Mike Harris
 
Introduction to agile and scrum
Introduction to agile and scrumIntroduction to agile and scrum
Introduction to agile and scrumAnat (Alon) Salhov
 
TDD - Seriously, try it! - Bucarest Tech Week
TDD - Seriously, try it! - Bucarest Tech WeekTDD - Seriously, try it! - Bucarest Tech Week
TDD - Seriously, try it! - Bucarest Tech WeekNacho Cougil
 
Vladimirs Ivanovs IPMA GYCW2013 Agile - traditional or balanced mix
Vladimirs Ivanovs IPMA GYCW2013 Agile - traditional or balanced mixVladimirs Ivanovs IPMA GYCW2013 Agile - traditional or balanced mix
Vladimirs Ivanovs IPMA GYCW2013 Agile - traditional or balanced mixVladimirs Ivanovs
 
Agile in Action - Agile Overview for Developers
Agile in Action - Agile Overview for DevelopersAgile in Action - Agile Overview for Developers
Agile in Action - Agile Overview for DevelopersMatt Cowell
 
TDD - Seriously, try it! - Trójmiasto Java User Group (17th May '23)
TDD - Seriously, try it! - Trójmiasto Java User Group (17th May '23)TDD - Seriously, try it! - Trójmiasto Java User Group (17th May '23)
TDD - Seriously, try it! - Trójmiasto Java User Group (17th May '23)ssusercaf6c1
 
TDD - Seriously, try it! - Trjjmiasto JUG (17th May '23)
TDD - Seriously, try it! - Trjjmiasto JUG (17th May '23)TDD - Seriously, try it! - Trjjmiasto JUG (17th May '23)
TDD - Seriously, try it! - Trjjmiasto JUG (17th May '23)Nacho Cougil
 
Couples Counseling for Product Development
Couples Counseling for Product DevelopmentCouples Counseling for Product Development
Couples Counseling for Product DevelopmentJoe Stump
 

Similar to Beyond agile - Pitfalls & misconceptions when working with SCRUM & Co | Ralf C. Adam (20)

2019-CertiFUNcation-Hacking-Agile-not-a-tech-talk
2019-CertiFUNcation-Hacking-Agile-not-a-tech-talk2019-CertiFUNcation-Hacking-Agile-not-a-tech-talk
2019-CertiFUNcation-Hacking-Agile-not-a-tech-talk
 
Secrets of Scrum
Secrets of ScrumSecrets of Scrum
Secrets of Scrum
 
Agile, not just for software
Agile, not just for softwareAgile, not just for software
Agile, not just for software
 
Morph your mindset for Continuous Delivery, Agile Roots 2014
Morph your mindset for Continuous Delivery,  Agile Roots 2014Morph your mindset for Continuous Delivery,  Agile Roots 2014
Morph your mindset for Continuous Delivery, Agile Roots 2014
 
Scrumban
Scrumban Scrumban
Scrumban
 
TDD - Seriously, try it! (updated '22)
TDD - Seriously, try it! (updated '22)TDD - Seriously, try it! (updated '22)
TDD - Seriously, try it! (updated '22)
 
Agile Scrum Training Process
Agile Scrum Training ProcessAgile Scrum Training Process
Agile Scrum Training Process
 
22-AnOverviewOfScrum.pptx
22-AnOverviewOfScrum.pptx22-AnOverviewOfScrum.pptx
22-AnOverviewOfScrum.pptx
 
Scrum levels danny_kovatch_agile_sparks
Scrum levels danny_kovatch_agile_sparksScrum levels danny_kovatch_agile_sparks
Scrum levels danny_kovatch_agile_sparks
 
Scrum
ScrumScrum
Scrum
 
It's XP Stupid (2019)
It's XP Stupid (2019)It's XP Stupid (2019)
It's XP Stupid (2019)
 
Scrum for high performance teams
Scrum for high performance teams Scrum for high performance teams
Scrum for high performance teams
 
Introduction to agile and scrum
Introduction to agile and scrumIntroduction to agile and scrum
Introduction to agile and scrum
 
TDD - Seriously, try it! - Bucarest Tech Week
TDD - Seriously, try it! - Bucarest Tech WeekTDD - Seriously, try it! - Bucarest Tech Week
TDD - Seriously, try it! - Bucarest Tech Week
 
Vladimirs Ivanovs IPMA GYCW2013 Agile - traditional or balanced mix
Vladimirs Ivanovs IPMA GYCW2013 Agile - traditional or balanced mixVladimirs Ivanovs IPMA GYCW2013 Agile - traditional or balanced mix
Vladimirs Ivanovs IPMA GYCW2013 Agile - traditional or balanced mix
 
Agile in Action - Agile Overview for Developers
Agile in Action - Agile Overview for DevelopersAgile in Action - Agile Overview for Developers
Agile in Action - Agile Overview for Developers
 
TDD - Seriously, try it! - Trójmiasto Java User Group (17th May '23)
TDD - Seriously, try it! - Trójmiasto Java User Group (17th May '23)TDD - Seriously, try it! - Trójmiasto Java User Group (17th May '23)
TDD - Seriously, try it! - Trójmiasto Java User Group (17th May '23)
 
TDD - Seriously, try it! - Trjjmiasto JUG (17th May '23)
TDD - Seriously, try it! - Trjjmiasto JUG (17th May '23)TDD - Seriously, try it! - Trjjmiasto JUG (17th May '23)
TDD - Seriously, try it! - Trjjmiasto JUG (17th May '23)
 
Introducing SCRUM
Introducing SCRUM Introducing SCRUM
Introducing SCRUM
 
Couples Counseling for Product Development
Couples Counseling for Product DevelopmentCouples Counseling for Product Development
Couples Counseling for Product Development
 

More from Ralf C. Adam

2019 - Getting the right partner for your game
2019 - Getting the right partner for your game2019 - Getting the right partner for your game
2019 - Getting the right partner for your gameRalf C. Adam
 
10 surefire ways to screw up your studio
10 surefire ways to screw up your studio10 surefire ways to screw up your studio
10 surefire ways to screw up your studioRalf C. Adam
 
Was tun wenn's brennt - Hand-out
Was tun wenn's brennt - Hand-outWas tun wenn's brennt - Hand-out
Was tun wenn's brennt - Hand-outRalf C. Adam
 
When shit hits the fan you need a plan
When shit hits the fan you need a planWhen shit hits the fan you need a plan
When shit hits the fan you need a planRalf C. Adam
 
Anatomy of a Modern Game design Document - Ralf Adam, Vera Frisch - 4C:Kyiv
Anatomy of a Modern Game design Document - Ralf Adam, Vera Frisch - 4C:KyivAnatomy of a Modern Game design Document - Ralf Adam, Vera Frisch - 4C:Kyiv
Anatomy of a Modern Game design Document - Ralf Adam, Vera Frisch - 4C:KyivRalf C. Adam
 
MS-Project - Unleash the Force | Ralf C. Adam
MS-Project - Unleash the Force | Ralf C. AdamMS-Project - Unleash the Force | Ralf C. Adam
MS-Project - Unleash the Force | Ralf C. AdamRalf C. Adam
 
Building the right team | Ralf C. Adam
Building the right team | Ralf C. AdamBuilding the right team | Ralf C. Adam
Building the right team | Ralf C. AdamRalf C. Adam
 
The ten Commandments of Project Management | Ralf C. Adam
The ten Commandments of Project Management | Ralf C. AdamThe ten Commandments of Project Management | Ralf C. Adam
The ten Commandments of Project Management | Ralf C. AdamRalf C. Adam
 
10 Projekt-Management Gebote | Ralf C. Adam
10 Projekt-Management Gebote | Ralf C. Adam10 Projekt-Management Gebote | Ralf C. Adam
10 Projekt-Management Gebote | Ralf C. AdamRalf C. Adam
 
Typische Lügen im Projektmanagement | Ralf C. Adam
Typische Lügen im Projektmanagement | Ralf C. AdamTypische Lügen im Projektmanagement | Ralf C. Adam
Typische Lügen im Projektmanagement | Ralf C. AdamRalf C. Adam
 
Seven Lies my Project Manager told me | Ralf C. Adam
Seven Lies my Project Manager told me | Ralf C. AdamSeven Lies my Project Manager told me | Ralf C. Adam
Seven Lies my Project Manager told me | Ralf C. AdamRalf C. Adam
 
Pitching Workshop for Game Developers | Ralf C. Adam
Pitching Workshop for Game Developers | Ralf C. AdamPitching Workshop for Game Developers | Ralf C. Adam
Pitching Workshop for Game Developers | Ralf C. AdamRalf C. Adam
 
German Game Development Post Mortems | Ralf C. Adam
German Game Development Post Mortems | Ralf C. AdamGerman Game Development Post Mortems | Ralf C. Adam
German Game Development Post Mortems | Ralf C. AdamRalf C. Adam
 
Outlook on the (potential) Future of the German Games Industry | Ralf C. Adam
Outlook on the (potential) Future of the German Games Industry | Ralf C. AdamOutlook on the (potential) Future of the German Games Industry | Ralf C. Adam
Outlook on the (potential) Future of the German Games Industry | Ralf C. AdamRalf C. Adam
 
Moving from boxed title Game Development to F2P | Ralf C. Adam
Moving from boxed title Game Development to F2P | Ralf C. AdamMoving from boxed title Game Development to F2P | Ralf C. Adam
Moving from boxed title Game Development to F2P | Ralf C. AdamRalf C. Adam
 
100 of the most influential German Videogames | Ralf C. Adam
100 of the most influential German Videogames | Ralf C. Adam100 of the most influential German Videogames | Ralf C. Adam
100 of the most influential German Videogames | Ralf C. AdamRalf C. Adam
 
Outsourcing a Game Trailer/TV-Spot | Ralf C. Adam
Outsourcing a Game Trailer/TV-Spot | Ralf C. AdamOutsourcing a Game Trailer/TV-Spot | Ralf C. Adam
Outsourcing a Game Trailer/TV-Spot | Ralf C. AdamRalf C. Adam
 

More from Ralf C. Adam (17)

2019 - Getting the right partner for your game
2019 - Getting the right partner for your game2019 - Getting the right partner for your game
2019 - Getting the right partner for your game
 
10 surefire ways to screw up your studio
10 surefire ways to screw up your studio10 surefire ways to screw up your studio
10 surefire ways to screw up your studio
 
Was tun wenn's brennt - Hand-out
Was tun wenn's brennt - Hand-outWas tun wenn's brennt - Hand-out
Was tun wenn's brennt - Hand-out
 
When shit hits the fan you need a plan
When shit hits the fan you need a planWhen shit hits the fan you need a plan
When shit hits the fan you need a plan
 
Anatomy of a Modern Game design Document - Ralf Adam, Vera Frisch - 4C:Kyiv
Anatomy of a Modern Game design Document - Ralf Adam, Vera Frisch - 4C:KyivAnatomy of a Modern Game design Document - Ralf Adam, Vera Frisch - 4C:Kyiv
Anatomy of a Modern Game design Document - Ralf Adam, Vera Frisch - 4C:Kyiv
 
MS-Project - Unleash the Force | Ralf C. Adam
MS-Project - Unleash the Force | Ralf C. AdamMS-Project - Unleash the Force | Ralf C. Adam
MS-Project - Unleash the Force | Ralf C. Adam
 
Building the right team | Ralf C. Adam
Building the right team | Ralf C. AdamBuilding the right team | Ralf C. Adam
Building the right team | Ralf C. Adam
 
The ten Commandments of Project Management | Ralf C. Adam
The ten Commandments of Project Management | Ralf C. AdamThe ten Commandments of Project Management | Ralf C. Adam
The ten Commandments of Project Management | Ralf C. Adam
 
10 Projekt-Management Gebote | Ralf C. Adam
10 Projekt-Management Gebote | Ralf C. Adam10 Projekt-Management Gebote | Ralf C. Adam
10 Projekt-Management Gebote | Ralf C. Adam
 
Typische Lügen im Projektmanagement | Ralf C. Adam
Typische Lügen im Projektmanagement | Ralf C. AdamTypische Lügen im Projektmanagement | Ralf C. Adam
Typische Lügen im Projektmanagement | Ralf C. Adam
 
Seven Lies my Project Manager told me | Ralf C. Adam
Seven Lies my Project Manager told me | Ralf C. AdamSeven Lies my Project Manager told me | Ralf C. Adam
Seven Lies my Project Manager told me | Ralf C. Adam
 
Pitching Workshop for Game Developers | Ralf C. Adam
Pitching Workshop for Game Developers | Ralf C. AdamPitching Workshop for Game Developers | Ralf C. Adam
Pitching Workshop for Game Developers | Ralf C. Adam
 
German Game Development Post Mortems | Ralf C. Adam
German Game Development Post Mortems | Ralf C. AdamGerman Game Development Post Mortems | Ralf C. Adam
German Game Development Post Mortems | Ralf C. Adam
 
Outlook on the (potential) Future of the German Games Industry | Ralf C. Adam
Outlook on the (potential) Future of the German Games Industry | Ralf C. AdamOutlook on the (potential) Future of the German Games Industry | Ralf C. Adam
Outlook on the (potential) Future of the German Games Industry | Ralf C. Adam
 
Moving from boxed title Game Development to F2P | Ralf C. Adam
Moving from boxed title Game Development to F2P | Ralf C. AdamMoving from boxed title Game Development to F2P | Ralf C. Adam
Moving from boxed title Game Development to F2P | Ralf C. Adam
 
100 of the most influential German Videogames | Ralf C. Adam
100 of the most influential German Videogames | Ralf C. Adam100 of the most influential German Videogames | Ralf C. Adam
100 of the most influential German Videogames | Ralf C. Adam
 
Outsourcing a Game Trailer/TV-Spot | Ralf C. Adam
Outsourcing a Game Trailer/TV-Spot | Ralf C. AdamOutsourcing a Game Trailer/TV-Spot | Ralf C. Adam
Outsourcing a Game Trailer/TV-Spot | Ralf C. Adam
 

Recently uploaded

Green minimalist professional Business Proposal Presentation.pdf
Green minimalist professional Business Proposal Presentation.pdfGreen minimalist professional Business Proposal Presentation.pdf
Green minimalist professional Business Proposal Presentation.pdfrudkiaman0001
 
Transform Your Space with Poster Memorabilia's Collection
Transform Your Space with Poster Memorabilia's CollectionTransform Your Space with Poster Memorabilia's Collection
Transform Your Space with Poster Memorabilia's CollectionPoster Memorabilia Reviews
 
MAGNET: Storyboard Excerpt Version Three
MAGNET: Storyboard Excerpt Version ThreeMAGNET: Storyboard Excerpt Version Three
MAGNET: Storyboard Excerpt Version Threedcobb11
 
TREE VOLANOES, A STORY FOR ENTERTAINMENT
TREE VOLANOES, A STORY FOR ENTERTAINMENTTREE VOLANOES, A STORY FOR ENTERTAINMENT
TREE VOLANOES, A STORY FOR ENTERTAINMENTazuremorn
 
karaoke songs customise for portable 2.docx
karaoke songs customise for portable  2.docxkaraoke songs customise for portable  2.docx
karaoke songs customise for portable 2.docxPOPCOMTABUKCITY
 
THE MEDIC, A STORY for entertainment.docx
THE MEDIC, A STORY for entertainment.docxTHE MEDIC, A STORY for entertainment.docx
THE MEDIC, A STORY for entertainment.docxazuremorn
 
Mince Pies, a story for entertainment.docx
Mince Pies, a story for entertainment.docxMince Pies, a story for entertainment.docx
Mince Pies, a story for entertainment.docxazuremorn
 
The Old Man and the Earthquake, a story for entertainment
The Old Man and the Earthquake, a story for entertainmentThe Old Man and the Earthquake, a story for entertainment
The Old Man and the Earthquake, a story for entertainmentazuremorn
 
Cabin by the azure lake, the story of a lady and a crocodile
Cabin by the azure lake, the story of a lady and a crocodileCabin by the azure lake, the story of a lady and a crocodile
Cabin by the azure lake, the story of a lady and a crocodileazuremorn
 
Bald Philosopher, a story for entertainment.docx
Bald Philosopher, a story for entertainment.docxBald Philosopher, a story for entertainment.docx
Bald Philosopher, a story for entertainment.docxazuremorn
 
WWW - World Wide Web presentation.pptx
WWW - World Wide Web   presentation.pptxWWW - World Wide Web   presentation.pptx
WWW - World Wide Web presentation.pptxdomainkillerlinux
 
MAGNET: Senior Thesis Storyboard Excerpt
MAGNET: Senior Thesis Storyboard ExcerptMAGNET: Senior Thesis Storyboard Excerpt
MAGNET: Senior Thesis Storyboard Excerptdcobb11
 
The lady in Surtout, an old story that happened in our neighbourhood
The lady in Surtout, an old story  that happened in our neighbourhoodThe lady in Surtout, an old story  that happened in our neighbourhood
The lady in Surtout, an old story that happened in our neighbourhoodazuremorn
 

Recently uploaded (13)

Green minimalist professional Business Proposal Presentation.pdf
Green minimalist professional Business Proposal Presentation.pdfGreen minimalist professional Business Proposal Presentation.pdf
Green minimalist professional Business Proposal Presentation.pdf
 
Transform Your Space with Poster Memorabilia's Collection
Transform Your Space with Poster Memorabilia's CollectionTransform Your Space with Poster Memorabilia's Collection
Transform Your Space with Poster Memorabilia's Collection
 
MAGNET: Storyboard Excerpt Version Three
MAGNET: Storyboard Excerpt Version ThreeMAGNET: Storyboard Excerpt Version Three
MAGNET: Storyboard Excerpt Version Three
 
TREE VOLANOES, A STORY FOR ENTERTAINMENT
TREE VOLANOES, A STORY FOR ENTERTAINMENTTREE VOLANOES, A STORY FOR ENTERTAINMENT
TREE VOLANOES, A STORY FOR ENTERTAINMENT
 
karaoke songs customise for portable 2.docx
karaoke songs customise for portable  2.docxkaraoke songs customise for portable  2.docx
karaoke songs customise for portable 2.docx
 
THE MEDIC, A STORY for entertainment.docx
THE MEDIC, A STORY for entertainment.docxTHE MEDIC, A STORY for entertainment.docx
THE MEDIC, A STORY for entertainment.docx
 
Mince Pies, a story for entertainment.docx
Mince Pies, a story for entertainment.docxMince Pies, a story for entertainment.docx
Mince Pies, a story for entertainment.docx
 
The Old Man and the Earthquake, a story for entertainment
The Old Man and the Earthquake, a story for entertainmentThe Old Man and the Earthquake, a story for entertainment
The Old Man and the Earthquake, a story for entertainment
 
Cabin by the azure lake, the story of a lady and a crocodile
Cabin by the azure lake, the story of a lady and a crocodileCabin by the azure lake, the story of a lady and a crocodile
Cabin by the azure lake, the story of a lady and a crocodile
 
Bald Philosopher, a story for entertainment.docx
Bald Philosopher, a story for entertainment.docxBald Philosopher, a story for entertainment.docx
Bald Philosopher, a story for entertainment.docx
 
WWW - World Wide Web presentation.pptx
WWW - World Wide Web   presentation.pptxWWW - World Wide Web   presentation.pptx
WWW - World Wide Web presentation.pptx
 
MAGNET: Senior Thesis Storyboard Excerpt
MAGNET: Senior Thesis Storyboard ExcerptMAGNET: Senior Thesis Storyboard Excerpt
MAGNET: Senior Thesis Storyboard Excerpt
 
The lady in Surtout, an old story that happened in our neighbourhood
The lady in Surtout, an old story  that happened in our neighbourhoodThe lady in Surtout, an old story  that happened in our neighbourhood
The lady in Surtout, an old story that happened in our neighbourhood
 

Beyond agile - Pitfalls & misconceptions when working with SCRUM & Co | Ralf C. Adam

  • 1. Beyond Agile Pitfalls and misconceptions when working with SCRUM & Co in video game development Ralf C. Adam
  • 2. This lecture was first held in April 2015 at the Quo Vadis Game Developer Conference in Berlin/GERMANY. The presentation may not include all original materials shown during this speech (pictures, videos etc.) and is solely meant as a summary and handout. All copyrights of presented materials belong to their respective owners. DISCLAIMER
  • 3. • Ralf C. Adam • Executive Producer at flaregames • >20 years in the games industry • Contributed to >80 games • Tutor at Games Academy in Berlin & Frankfurt • Hobbys: Movies, Games, Gadgets, Soccer, Karaoke ABOUT MYSELF
  • 4. • This talk is about agile project management methods and concepts and how to apply them to game development • I will give examples of what to avoid – as well as some best practices ABOUT THIS TALK
  • 5. WHAT IS AGILE? There‘s no such thing as doing Agile!
  • 6. WHAT IS AGILE? • Correct Wording: o Agile development practices or methods o Agile development teams o Develop software with agility • Agile is an adjective not a noun • It‘s an attribute to something we do… • …not THE something
  • 7. • Right now big hype around it • Everybody talks about „being agile“ • Often feels like buzzword bingo • Also lots of money involved (Trainings, expensive certifications etc.) • Originally comes from traditional IT • Question: Is it really 100% adaptable for video game development? WHAT IS AGILE?
  • 8. [agile]: Relating to or denoting a method of project management, used especially for software development, that is characterized by the division of tasks into short phases of work and frequent reassessment and adaption of plans: agile methods replace high-level design with frequent redesign. Contrasted with waterfall (adjective). SOURCE: oxforddictionairies.com WHAT IS AGILE?
  • 9. • By the way: It is not a new invention! • Game developement has always been an agile processof Missile Command (1980) and Tempest »Pick an idea. Write up a game proposal. Get it OK'd by management. Take a couple of weeks to bring up a playable simple version. Management reviews that and OKs it or axes it. If OK'd, continue with the whole game. Regular reviews by management to make sure still fun. Kill the game if not.« Dave Theurer (1980) Designer of Tempest and Missile Command WHAT IS AGILE?
  • 10. BEFORE AGILE THERE WAS RAD • In 1991 James Martin wrote „Rapid Application Development“ (RAD) • Princicples described in there: o Risk reduction o Early prototyping o Finding problems earlier in life-cycle (cheaper to fix) o Emphasizes necessity of adjusting requirements throughout development o Also emphasize a flexible process and planning • See also: Rapid Development – Steve McConnell (1996)
  • 11. THE AGILE MANIFESTO Lean FDD DSDM Crystal XP (Extr. Prog.) SCRUM The Agile Manifesto (2001)
  • 12. AGILE METHODS Lean • Father = Taiichi Ono (1988), Production Lead Toyota • Comes from Lean Manufacturing. Set of principles for achieving quality, speed & customer alignment • No set of fixed Rules or Methods • It‘s a Philosophy/Company Culture • Lean Company e.g. can use SCRUM as specific method • Princicples: o Eliminate Waste o Improve Quality o Reduce Costs o Deliver Fast o Respect People o Constantly improve Skills & Production Processes
  • 13. • Feature Driven Development • High Level Method • Allows for other methods on lower level • Purely focusses on the Delivery of Features AGILE METHODS FDD
  • 14. • Advancement of RAD • Rather strict set of Rules • Acknowledges cooperation with e.g PRINCE2 & PMI • Focus on Timeboxing and MoSCoW prioritization (Must have, Should have, Could have, Won’t have) AGILE METHODS DSDM
  • 15. • Developed in 1990’ies by Cockburn • Focused on people, iteration, community, skills, talents, communications • More framework than rule set • Creed: People above process • Very tolerant AGILE METHODS Crystal
  • 16. • Focus on Programming • Emphasizes Team-Work • Focus on changing customer requirements • More open to change (than e.g. SCRUM) • Focus on certain coding practices such as Testing, Feedback, Pair Programming, Simplicity, Test Driven Development etc. AGILE METHODS XP (Extr. Prog.)
  • 17. AGILE METHODS SCRUM 30 days 24 hours Product Backlog As prioritized by PRODUCT OWNER Sprint Backlog Backlog tasks expanded by TEAM Potentially Shippable Product Increment Daily Scrum Meeting Source: Adapted from Agile Software Development with Scrum by Ken Schwaber and Mike Beedle
  • 18. KANBAN • Method for Steering Production • Once Again: Toyota/Taichi Ono (Part of the Lean Process) • Japanese: word Kan means "signal" and "ban“ means "card" • Therefore Kanban refers to "signal cards“ • Starbucks is a Kanban-System -> the cup is the Kanban • The cup-ban acts as an order form that can encode most combinations that a barista should expect • SCRUM-Boards are often traditional Kanban-Boards
  • 20. PITFALLS • What are potential problems/pitfalls of agile methods? • Mostly by the example of SCRUM (as it‘s the most used one) • BTW: I do not know any game development studio that uses SCRUM 100% by the Book • Most teams just use parts of it – the once that work for them • SCRUM Purists call this approach SCRUMBut • They blame wrong usage when it‘s not working out • Which I personally think is at least questionable…
  • 21. THE IT vs GAMES DILEMMA • Software Development Processes = traditional IT • We are not IT Development • We are not making SAP Databases • We are making Games • There are fundamental differences between the two
  • 22. THE IT vs GAMES DILEMMA (CONT.) • The Customer (Publisher) does not make the Design/Specification doc (compared to traditional IT) • The user (player) does not give feedback until Game is out or focus group tests with Closed Alpha/Beta • No Design in the World can „describe“ fun • True: that‘s why an iterative approach for „Making it fun“ is a good concept (Prototypes/Pre-Production) • But: if you treat game development solely with methods that were meant for creating a database – you easily end up creating just a database, but not a game!
  • 23. THE DEADLINE PARADOXON • Working with a Publisher ALWAYS means: There are Deadlines • Good reasons for that: Planning for Marketing, QA slots, Console/Apple Submission etc. • Not committing to deadlines does not work with Publishers • SCRUM Purist argue the product is potentially shippable after every Sprint – in theory that would mean: o Just stop developing at the deadline and release the game, no matter what o In whatever state it is at the end of the last Sprint o The goal of game development is not "to finish a game" but "to finish a good game"
  • 24. THE FEATURE PROBLEM • A feature may take longer than just one sprint • Many larger features don't work with the concept of being 'potentially shippable' after every Sprint. • Sometimes there are features you either do entirely in one go or not at all, and that may just take the time it needs and can not be squeezed into a sprint • Other problem: a large feature may only work together reasonably with another feature linked to it • Both have to be there to make it meaningful. Half a feature-set might be just a broken game
  • 25. THE SUM OF ALL FEATURES • A game is more than the sum of ist features • SCRUM encourages for divding devlopement into little chunks • This often ends up in a gathering of working features – without any soul or meaning • It takes a vision and an overall plan how these features shall work together • I‘ve seen many SCRUM teams that were just thinking about the current sprint • It was even kind of „forbidden“ to them to think about the next sprint or upcoming features
  • 26. THE SUM OF ALL FEATURES (CONT.) • Product backlog: not a good tool to transport an overall vision (nor a good vision for features itself) • This does not work for Game Development • It‘s like shooting a movie and on the set you start writing the script, scene by scene while you shoot • 1st rule of Hollywood Script-Writing: You start developing a script with the end in your mind (= the vision)
  • 27. THE DAILY STAND-UP CHARADE • Generally: Daily Standup is a good thing • But can easily go wrong and derail • Lot of people don‘t want to talk there, others talk too much (usually always the same ones) • SCRUM Stand-Ups can create an interrogation atmosphere • What if people are not in the same location? • Question most teams forget in Stand-Up: What‘s the status for the Outsourcing teams/partners?
  • 28. THE VISION-KEEPER COMPLICATION • Who owns the Game Vision? • Problem in many SCRUM teams: missing or unclear Vision Keeper • Or: Vision Keeper is NOT the Product Owner • Or: Product Owner is NOT the Game Designer but a „Suit“ • SCRUM Team = all team members have the same saying • Does hardly work in Game Development (or similar creative processes/media) • Again: Try to imagine SCRUM on a movie set • US TV series: Showrunner Princicple in combination with Writer‘s Room
  • 29. THE SCALING NIGHTMARE SCRUM Team SCRUM Team SCRUM Team SCRUM Team SCRUM of SCRUMS Game Project Physics Team AI Team Online-Team UI/UX-TeamProduct Owner Product Owner Lead Product Owner
  • 30. THE SCALING NIGHTMARE (CONT.) • SCRUM recommends team has size of 7 to 9 • Less you don‘t need this structure • More you can not let it run „self managed“ • But what‘s with bigger Game Teams/Studios? • Then suddenly SCRUM gets very hierarchical very fast (see slide before)
  • 31. THE SCALING NIGHTMARE (CONT.) • SCRUM of SCRUMS (somebody in a blog called it „the old idea of communists‘ cells (Russian Bolsheviks organized themselves in “cells” of about 10 to hide from the management of the day) • Results in LOTS of meetings, makes decision making super-slow • To quote another blog: “In a nutshell Scrum can add unnecessary overhead & can encourage product management anti-patterns that lead to bad decisions, frustration and a deceiving sense of control.”
  • 32. THE CUSTOMER QUESTION • Most agile methods preach user & customer involvement throughout the whole development cycle • Who’s the user and who’s the customer in Game Development? • Unlike e.g. SAP we can’t put UI framework/mask out and ask users (=gamers) to give feedback • Does hardly work for games without context • Publisher also can’t be involved like traditional Product Owners • Publisher usually has no time for such an involvement, nor the expertise (the publisher producer might have, but not all other stakeholders)
  • 33. THE BURNDOWN CHART COMPLICATION • Goal of Burn-down Chart: To measure Velocity during Sprint • But… o Premise: always the same people o Premise: that always work the same speed • So Question is: What do you actually measure? • How good/fast the people work? • Or how good their estimates were? • My Experience: Burn-Down Chart one of the first things most teams start to not update anymore once they are running out of time
  • 34. THE „INDIVIDUALS OVER PROCESSES“ LIE »Individuals and interactions over processes & tools« 1st core from the Manifesto for Agile Software Development (2001) »ScrumButs are reasons why teams can’t take full advantage of Scrum to solve their problems and realize the full benefits of product development using Scrum. Every Scrum role, rule, and timebox is designed to provide the desired benefits and address predictable recurring problems.« SCRUM.ORG vs
  • 35. THE „INDIVIDUALS OVER PROCESSES“ LIE (CONT.) • Typical SCRUM statement: • “You don’t see good results with Scrum because you don’t do enough of it/don‘t use it right!” • Such statements encourage the opposite of the (very pragmatic) principles of the original Agile manifesto (see slide before) • Reason: It‘s all about certificates (=MONEY!) • Every two years you have to renew your SCRUM Master/Product Owner etc.
  • 37. VISION STATEMENT • Vision Statement is fundamental… • …even when using agile methods • If you do not know the goal you will not find the way o What is it that you want to build? o What will be the core gameloop the player will constantly face & play? o What are the primary and secondary gameplay elements? • It‘s hard to „iterate“ towards a vision – how do you know when you‘re there?
  • 38. THE „HITCHCOCK APPROACH“ • Always go from the big Picture into smaller pieces (like Hitchcock) • Don’t start creating a Backlog without clear a Vision Document • Don’t start creating small feature implementations if you do not know the big picture • Actually the basic idea of starting with “Epics” and then breaking them down into User Stories is pretty good and exactly the right approach in that context • Just make sure you have the big Picture first, before you start writing User Stories (potential downside of “Agile methods as they come from IT: you start with implementation of stuff that you think is clearly enough defined already)
  • 39. PRE-PRODUCTION • Never start without a proper Pre-Production • Topic big enough for another talk in iteself • Briefly: spend rather too much time in Pre-Prod than too little (upstream vs downstream cost) • One of the many advantages: Team is smaller • Pre-Production itself well suited for agile methods as it is per definition about prototyping and iteration
  • 40. VERTICAL-SLICE • Final Proof of production quality and fun • Important when working with a Publisher • Final alignment on what it is that the Publisher (and ultimately the player) gets in the end in terms of quality level and fun
  • 41. FEATURE-CREEP • American Game Design vs. German Game Design: o US-Design: Feature is not fun? It gets kicked out… o German-Design: Feature is not fun? Add two additional features to support the feature that is not workin • Create a small feature set that is deeply polished – not the other way round • Once again: potantial trap of Agile-Methods as they preach „Delivery of Features“ • I‘ve seen too many teams (and publishers!) that were only focussed on creating features rather than fun
  • 42. CANBAN-BOARDS • Kanban Boards (e.g. Trello) are great and can be used and adapted for project management in multiple ways • Next Slides show how we used it at Virgin Lands for instance to plan an entire Movie Production • In this example: Texturing Workflow of all Movie Assets • Kanban generally is very helpful especially for creation and tracking of graphic Assets • Most Movie Production use a tool called „Shotgun“
  • 45. THERE IS NO „TOO SIMPLE“ • With regards to Project Management Methods… • …listen to Albert Einstein: Make it as simple as possible but not simpler! • It’s not about creating a Leviathan-Process! • Trust your instincts – if you think your method sucks, than it most certainly does!
  • 46. TEAM ACCEPTANCE • Last but not least: acceptance of the methods used is more important than their potential efficency or any dogmatic framework • Tailoring your process to your situation has always been the most agile option of all • The whole team should agree to any process and workflow • If the team thinks a workflow is stupid – change it! • They will not follow it otherwise anyway