Post on 14-Apr-2017
30/01/16 Game Dev conference Lviv 30 Jan 2016 1
Andrew Gurskiy
Agile architecture
2Agile architecture. Game Dev conference Lviv 30 Jan 2016
WATERFALLThe linearly flow.
3
AGILEThe circle flow.
Agile architecture. Game Dev conference Lviv 30 Jan 2016
4
ArchitectureWhat is it?
Agile architecture. Game Dev conference Lviv 30 Jan 2016
5
ArchitectureThis is
Agile architecture. Game Dev conference Lviv 30 Jan 2016
MAINKEY
DECISIONS
6
The level of importanceHow do we measure it?
Agile architecture. Game Dev conference Lviv 30 Jan 2016
ACOORDINGTO
RISK LEVEL
7
RisksCommon types
Agile architecture. Game Dev conference Lviv 30 Jan 2016
INTERNALEXTERNAL
bus factorimplementation
processesinfrastructure
...
3rd party relationshipsglobal states
customer imagination...
8
Point of viewAll sides use architecture, but.....
Agile architecture. Game Dev conference Lviv 30 Jan 2016
9
Big Design Up Front (BDUF)Should include ALL aspects and be perfect completed before implementation
Agile architecture. Game Dev conference Lviv 30 Jan 2016
Small unplanned task
BIG CO$T
10
Simple designOnly requirements nothing more
Agile architecture. Game Dev conference Lviv 30 Jan 2016
All unplanned task
GENERAL CO$T
11
Simple designOnly requirements nothing more
BUT!!!!!!!!!
Agile architecture. Game Dev conference Lviv 30 Jan 2016
simple design ≠code style
patternsresponsibility
unit testingdocumentation
code review
bad code
12Footer
BDUF vs SimpleMake your choice
cost
project phase
frozen
flexible
13
BDUF vs SimpleMake your choice
Agile architecture. Game Dev conference Lviv 30 Jan 2016
FORMALITIES
vs
ARRANGEMENTS
14
My choice is.....
Agile architecture. Game Dev conference Lviv 30 Jan 2016
Agile
15
Implementation way
Agile architecture. Game Dev conference Lviv 30 Jan 2016
1.2.3.
iterative thinkingfrom person to team
retrospective
QUESTIONS
16Agile architecture. Game Dev conference Lviv 30 Jan 2016
THANK YOUAndrew Gurskiy
agurskiy@playtika.com
17Agile architecture. Game Dev conference Lviv 30 Jan 2016