A presentation for Angel Cube 2013. How does Tweaky.com survive with a single developer? This presentation is about how we take an idea to production, and validate that it works.

1. IT Department of One
How Tweaky.com scopes, builds, and validates features
PJ Murray
Cofounder and CTO - Tweaky
pj@tweaky.com
Friday, 7 June 13

2. IT Department of One
What I’m going to cover
- How I got here
- Scoping
-Building
-Validating
Friday, 7 June 13

3. My Story
IT Department of One
Friday, 7 June 13

4. IT Department of One
Friday, 7 June 13

5. IT Department of One
Friday, 7 June 13

6. IT Department of One
Friday, 7 June 13

7. IT Department of One
Friday, 7 June 13

8. Kickoff
IT Department of One
Friday, 7 June 13

9. Scoping Features
IT Department of One
Friday, 7 June 13

10. Capture Ideas
IT Department of One
Friday, 7 June 13

11. EXAMPLE -
Purchase Credits
IT Department of One
Friday, 7 June 13

12. IT Department of One
Friday, 7 June 13

13. IT Department of One
Purchase
Friday, 7 June 13

14. IT Department of One
Purchase
View
Invoice
Mul2ple
Credit
Op2ons
View
Balance
Request
Refund
Credits
Expire
Use
Credits
Transfer
Credits
Friday, 7 June 13

15. DON’T
IT Department of One
- Get stuck in technical implementation
- Get distracted by shiny “cool” things
- Overcomplicate things
Friday, 7 June 13

16. IT Department of One
MVP
Friday, 7 June 13

17. IT Department of One
MoSCoW
Friday, 7 June 13

18. IT Department of One
MoSCoW
Must Have Should Have
Could Have Wont Have
Friday, 7 June 13

19. IT Department of One
Must Have Should Have Nice to Have
Friday, 7 June 13

20. IT Department of One
Must Have Should Have Nice to Have
DO
Friday, 7 June 13

21. How do I know what a “Must Have” is?
IT Department of One
Friday, 7 June 13

22. Understand the Value
IT Department of One
- What assumption is the feature based on?
- Will it still work without x, y or z?
- Question everything
Friday, 7 June 13

23. IT Department of One
Purchase
View
Invoice
Mul2ple
Credit
Op2ons
View
Balance
Request
Refund
Credits
Expire
Use
Credits
Transfer
Credits
Friday, 7 June 13

24. IT Department of One
Purchase
View
Invoice
Mul2ple
Credit
Op2ons
View
Balance
Request
Refund
Credits
Expire
Use
Credits
Transfer
Credits
Friday, 7 June 13

25. IT Department of One
Purchase
View
Invoice
Mul2ple
Credit
Op2ons
View
Balance
Request
Refund
Credits
Expire
Use
Credits
Transfer
Credits
Friday, 7 June 13

26. IT Department of One
Value is still only an assumption
Friday, 7 June 13

27. IT Department of One
Must Have Should Have Nice to Have
DO
Friday, 7 June 13

28. IT Department of One
Must Have Should Have Nice to Have
DON’T
Friday, 7 June 13

29. IT Department of One
Define a Success Metric
Friday, 7 June 13

30. IT Department of One
How do we know that
the feature works?
Friday, 7 June 13

31. IT Department of One
- Conversion Rate
- Customer Acquisition Cost
- Customer Satisfaction
- Lifetime Value
- Traffic
- Page Views
- New Users
- Sessions
Friday, 7 June 13

32. IT Department of One
Pick One
Friday, 7 June 13

33. IT Department of One
Discovery and Validation
Friday, 7 June 13

34. IT Department of One
Friday, 7 June 13

35. Building Features
IT Department of One
Friday, 7 June 13

36. It’s never “just” a form field
IT Department of One
Friday, 7 June 13

37. IT Department of One
Code you don’t write is:
1. Code you don’t have to test
2. Code you don’t have to maintain
Friday, 7 June 13

38. Don’t Build Any Of It
IT Department of One
(if you don’t have to)
Friday, 7 June 13

39. IT Department of One
Friday, 7 June 13

40. EXAMPLE -
Tweaky Success Calls
IT Department of One
Friday, 7 June 13

41. Don’t Build All of It
IT Department of One
Friday, 7 June 13

42. Leverage Existing Tools
IT Department of One
Friday, 7 June 13

43. IT Department of One
Friday, 7 June 13

44. Reuse Existing Code
IT Department of One
Friday, 7 June 13

45. EXAMPLE -
Tweaky Credits and Coupons
IT Department of One
Friday, 7 June 13

46. EXAMPLE -
Social Share and Affiliates
IT Department of One
Friday, 7 June 13

47. KISS
IT Department of One
(keep it simple stupid)
Friday, 7 June 13

48. No Software Wank
IT Department of One
Friday, 7 June 13

49. IT Department of One
Testing
Friday, 7 June 13

50. IT Department of One
When It’s High Risk
Friday, 7 June 13

51. IT Department of One
When Things Fail
Friday, 7 June 13

52. IT Department of One
Some Safety
Friday, 7 June 13

53. Ship Broken Code
IT Department of One
Friday, 7 June 13

54. IT Department of One
A un-deployed feature with
100% test coverage is
100% worthless
Friday, 7 June 13

55. IT Department of One
Bake in Metrics
Friday, 7 June 13

56. Technical Debt
IT Department of One
Friday, 7 June 13

57. IT Department of One
Validating
Friday, 7 June 13

58. IT Department of One
Understand the Question
Friday, 7 June 13

59. IT Department of One
Don’t be Tricky
Friday, 7 June 13

60. IT Department of One
Make it Visible
Friday, 7 June 13

61. IT Department of One
Review, Learn and Iterate
Friday, 7 June 13

62. IT Department of One
How Tweaky.com scopes, builds, and validates features
PJ Murray
Cofounder and CTO - Tweaky
pj@tweaky.com
Friday, 7 June 13