story generation
DESCRIPTION
Where Lourenço describes the generative model of story writing, based on 3 main axis: Epics are bad, Going to production is good, Small increments are good.TRANSCRIPT
STORY GENERATION@protolous
2
3 THINGS
3
3 THINGSEPICS CONSIDERED HARMFUL
4
3 THINGSEPICS CONSIDERED HARMFUL
GOING TO PRODUCTION AS THE 1ST THING YOU DO
5
3 THINGSEPICS CONSIDERED HARMFUL
GOING TO PRODUCTION AS THE 1ST THING YOU DO
YOUR STORIES ARE TOO BIG
6
EPICS CONSIDERED HARMFUL
EPICS ARE USELESS *
7
* Unless you realize a story is too big after the fact and call it an “epic”. Then it’s fine.
EPICS ARE USELESS *
8
DON’T ADD PREVISIBILITY
Can’t be used for estimation
Hides complexity
EPICS ARE USELESS *
9
ASSUME LOTS OF THINGS
Assumes the problem exists
Assumes the solution described solves the problem
Does not tell you about these assumptions
EPICS ARE USELESS *
10
USE “WRONG TYPE” OF
CREATIVITY
Creativity is driven by constraints
Epics are “tabula rasa”
EPICS ARE USELESS *
11
DON’T ADD PREVISIBILITY
Can’t be used for estimation
Hides complexity
ASSUME LOTS OF THINGS
Assumes the problem exists
Assumes the solution described solves the problem
Does not tell you about these assumptions
USE “WRONG TYPE” OF
CREATIVITY
Creativity is driven by constraints
Epics are “tabula rasa”
PARADIGM SHIFT
12
Often (…) discovery is not
quite the one anticipated by
the speculative and tentative
hypothesis. Only as
experiment and tentative
theory are together
articulated to a match does
the discovery emerge and the
theory become a paradigm.
“SCIENTIFIC” METHOD
13
PURPOSE
RESEARCH
HYPOTHESIS
EXPERIMENT
ANALYSIS
“SCIENTIFIC” METHOD
14
PURPOSE
RESEARCH
HYPOTHESIS
EXPERIMENT
ANALYSIS
15
GOING TO PRODUCTION AS THE 1ST THING YOU DO
16
STOP WORRYING…
ROBOTS.TXTHTTP AUTHFEATURE TOGGLESCANARY RELEASESDARK LAUNCHINGBLUE/GREEN DEPLOYMENT
PLAYBOOK FOR PRODUCTION FIRST
17
PLAYBOOK FOR PRODUCTION FIRST
18
1. Identifying the ABSOLUTELY MINIMAL that could be valuable to a user
PLAYBOOK FOR PRODUCTION FIRST
19
1. Identifying the ABSOLUTELY MINIMAL that could be valuable to a user
2. Build a ‘walking skeleton’. MAKE AS
MANY COMPROMISES AS POSSIBLE
PLAYBOOK FOR PRODUCTION FIRST
20
1. Identifying the ABSOLUTELY MINIMAL that could be valuable to a user
2. Build a ‘walking skeleton’. MAKE AS
MANY COMPROMISES AS POSSIBLE
3. Create a production environment for this walking
skeleton. BE FRUGAL IN YOUR AUTOMATION
21
TIME FOR REFLECTION
22
Can I have Continuous Delivery
without Continuous Integration?
ASK YOURSELF
23
How many developers/streams of work?
Will anyone need a staging or testing environment?
Will I be using this code a year from now?
What is the worst thing that could happen?
How else can I know if I can actually do it?
JUST SHIP IT
24
Have small increments to receive valid feedback earlier
25
YOUR STORIES ARE TOO BIG
HOW LITTLE IS ENOUGH?
26
HOW LITTLE IS ENOUGH?
27
t r u e s t o r y
HOW LITTLE IS ENOUGH?
28
t r u e s t o r y
SMALL INCREMENTS @ LASTMINUTE.COM
Provide a mobile landing
page in French
29
SMALL INCREMENTS @ LASTMINUTE.COM
Search by location code
(3 letters, like “LON”) and
for tonight* and return a
list of first 100 hotel
names
30
* Picture was taken a few stories later…
SMALL INCREMENTS @ LASTMINUTE.COM
One story to add pictures
One story to add price
31
SMALL INCREMENTS @ LASTMINUTE.COM
One story for star rating
One story for distance
from you
One story for back button
on this page
One story for collapsing
search attributes32
A GOOD STORY
33
REALIZES ITS VALUE
IMMEDIATELY
YOU KNOW WHEN IT IS
DONE
YOU KNOW WHY YOU ARE
DOING IT
I WRITE SMALL STORIES BECAUSE…
34
COMMENTS..? DOUBTS..? COMPLAINTS..?
Please follow @protolous on to
continue this conversation