Todays web and app projects are not just pieces of code.Every change a developer creates can affect performance, usability,stability and even the relationship to the customer.In this talk I will discuss the necessity for agile development teams to havea better understanding of what makes their product really great in the endand how recurring conceptual phases can help in this.
Presented at T3Con15 in Amsterdam
2. Who am I?
1990 Pen & Paper
1996 Geocities
2005 TYPO3
2007 Freelancer
2013 Neos CMS
2015 CSM
Love hiking, mountains and baking
3. Chapters
I. Dungeons & Dragons & Conceptual understanding
II. A light through the fog of requirements
III. Evade traps with agile methods
IV. Gain experience and grow your strengths
V. Slay the dragon of Golive and retrieve it’s treasures
14. Parts of a Pen & Paper game
Game master (Storyteller, Visionary, PO)
2-6 Adventurers (Different strengths and personalities)
Space where everyone sits together
Books describing the rules of the game
Motivation
Common goal
Sounds like a project
15. How people play
I. Game master describes the situation
II. Everyone synchronizes their view
III. Player do actions
IV. Game master explains results according to the story and the rules
V. Players evaluate result and adapt
VI. Start again from step I.
Sounds like a Sprint
36. Empathy
Client has bad experience?
Feel the urge to improve it
Find sustainable solutions
Work with the client
Try to understand the client
Get to know the client (he’s not the dragon)
37. As a developer you can
See tasks as challenge
Try to see your work from a different point of view
Involve in shaping a project
Defend your ideas and concepts
Teach others
Cooperate & ask for help
Write down or draw what you know