The document discusses principles for effective story generation, including keeping stories small and focused, avoiding epics, and being careful about assumptions. It advocates identifying the absolute minimum functionality needed and building incrementally from there. Continuous delivery is possible without continuous integration if integration needs are limited. Stories should provide immediate value and have clear completion criteria.

1. STORY GENERATION
@protolous

2. 2
3 THINGS

3. 3
3 THINGS
EPICS CONSIDERED HARMFUL

4. 4
3 THINGS
EPICS CONSIDERED HARMFUL
GOING TO PRODUCTION AS THE 1STTHING YOU DO

5. 5
3 THINGS
EPICS CONSIDERED HARMFUL
GOING TO PRODUCTION AS THE 1STTHING YOU DO
YOUR STORIES ARE TOO BIG

6. 6
EPICS CONSIDERED HARMFUL

7. EPICS ARE USELESS *
7
* Unless you realize a story is too big after the fact and call it an “epic”. Then it’s fine.

8. EPICS ARE USELESS *
8
DON’T ADD PREVISIBILITY
Can’t be used for estimation
Hides complexity

9. 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

10. EPICS ARE USELESS *
10
USE “WRONG TYPE” OF CREATIVITY
Creativity is driven by constraints
Epics are “tabula rasa”

11. 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”

12. 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.

13. “SCIENTIFIC” METHOD
13
PURPOSE
RESEARCH
HYPOTHESIS
EXPERIMENT
ANALYSIS

14. “SCIENTIFIC” METHOD
14
PURPOSE
RESEARCH
HYPOTHESIS
EXPERIMENT
ANALYSIS

15. 15
GOING TO PRODUCTION AS THE 1ST THING YOU DO

16. 16
STOP WORRYING…
ROBOTS.TXT
HTTP AUTH
FEATURE TOGGLES
CANARY RELEASES
DARK LAUNCHING
BLUE/GREEN DEPLOYMENT

17. PLAYBOOK FOR PRODUCTION FIRST
17

18. PLAYBOOK FOR PRODUCTION FIRST
18
1.Identifying the ABSOLUTELY MINIMALthat could be valuable to a user

19. PLAYBOOK FOR PRODUCTION FIRST
19
1. Identifying the ABSOLUTELY MINIMALthat could be valuable to a user
2. Build a ‘walking skeleton’. MAKE AS MANY COMPROMISES AS POSSIBLE

20. PLAYBOOK FOR PRODUCTION FIRST
20
1. Identifying the ABSOLUTELY MINIMALthat 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. 21

22. TIME FOR REFLECTION
22
Can I have Continuous Delivery without Continuous Integration?

23. 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?

24. JUST SHIP IT
24
Have small increments to receive valid feedback earlier

25. 25
YOUR STORIES ARE TOO BIG

26. HOW LITTLE IS ENOUGH?
26

27. HOW LITTLE IS ENOUGH?
27
true story

28. HOW LITTLE IS ENOUGH?
28
true story

29. SMALL INCREMENTS @ LASTMINUTE.COM
Provide a mobile landing page in French
29

30. 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…

31. SMALL INCREMENTS @ LASTMINUTE.COM
One story to add pictures
One story to add price
31

32. 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 attributes
32

33. A GOOD STORY
33
REALIZES ITS VALUE IMMEDIATELY
YOU KNOW WHEN IT IS DONE
YOU KNOW WHY YOU ARE DOING IT

34. I WRITE SMALL STORIES BECAUSE…
34

35. COMMENTS..? DOUBTS..?
COMPLAINTS..?
Please follow @protolous on to
continue this conversation