Introduction to managing small teams when developing games the agile way.

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

17. Scrum Roles
Product
Owner
Scrum
Master
Team

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)

25. Sprint Structure
DEMO

26. Team Learnings
DEMO

27. Thank you!
http://www.npruehs.de
https://github.com/npruehs
@npruehs
dev@npruehs.de