This talk focuses on both the process improvements (short sprints, how to capture requirements) and technical (testing, continuous integration).

1. HOW TO KEEP CALM
AND SHIP IT

2. hello
my name is
@JUOKAZ

4. IF SOMETHING BIG HAPPENS,
HOW QUICKLY CANYOU
REACT?

5. MVP

6. WHY DOESTHIS MATTER?

7. ANY DAY NOT IN
PRODUCTION IS LOST
POTENTIAL

8. HOWTO GO FROM AN IDEA
TO IMPLEMENTATION IN DAYS

9. MOVE FAST AND BREAK THINGS
- Mark Zuckerberg, Facebook

10. REQUIREMENTS

11. UNCLEAR ORIGINAL
SPECIFICATIONS

13. CYCLES OF CHANGES AND
TESTING

14. LACK OF UNDERSTANDING
WHY KILLS PROJECTS

15. “YOU SHOULD ADD A
BUTTON/CHECKBOX”

16. IMPACT MAPPING
http://www.impactmapping.org/

17. 1. why are we doing this
2. who is affected by this
3. how should the behavior change
4. what can we do as an organization

18. ALWAYS HAVE A PLAN

19. IDENTIFY WHATYOU
CANNOT BREAK

20. FEATURE-CREEP KILLS
PROJECTS

21. AGILE?

22. IF IT'S HARD, CUT SCOPE
- Wiggins' Law

23. PROTOTYPING

24. FAMILIARTOOLSET

25. TOOLBOX
• Bootstrap for all frontend work
• Web framework of choice
• Database of choice
• ect.

26. FLASK-SKELETON
https://github.com/juokaz/flask-skeleton

27. BUILD DELIVERABLE
PRODUCTS

28. EVERY SUB-FEATURE SHOULD
WORK

29. “WE CAN ALWAYS FIX IT
LATER”

30. PRETTY APPS > WORKING APPS

31. FAKE/HACK IRRELEVANT PARTS

32. CONTINUOUS DELIVERY

33. 12-FACTOR APP
http://12factor.net/

34. 1. Codebase - One codebase tracked in revision control
2. Dependencies - Explicitly declare and isolate
dependencies
3. Config - Store config in the environment
4. Backing Services -Treat backing services as attached
resources
5. Build, release, run - Strictly separate build and run
stages
6. Processes - Execute the app as one or more stateless
processes
7. Port binding - Export services via port binding
8. Concurrency - Scale out via the process model
9. Disposability - Maximize robustness with fast
startup and graceful shutdown
10. Dev/prod parity - Keep development, staging,
and production as similar as possible
11. Logs -Treat logs as event streams
12. Admin processes - Run admin/management
tasks as one-off processes
12-FACTOR APP

35. TDD?

36. VERIFICATION

37. DOCKER
http://docker.com/

38. CHECKLIST
• Push to master
• Build a Docker container containing the app
• Runs tests, code formatting checks, database
migrations validation
• If all is ok, the Docker container is a stable build
• Then deploy to staging and/or production

39. FEEDBACK LOOP

40. DEVELOPERS ROLE
• Owners of a project/feature/system
• Responsible for fixing if it’s broken
• Slack operations room

41. METRICS

42. STATSD/GRAPHITE
https://github.com/etsy/statsd

43. “NO ONE NOTICES A WEBSITE
BROKEN FOR 2 MINUTES”

44. USERS

45. IN SHORT
• Collect requirements and make aTODO list even
for small projects
• Prototype using familiar tools and frameworks
• Continuos delivery
• Feedback loop

46. THANKS!
Juozas Kaziukėnas
@juokaz