How Tweaky Scopes, Builds, and Validates Ideas

  • 137 views
Uploaded on

A presentation for Angel Cube 2013. …

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.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
137
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
0
Comments
0
Likes
1

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. IT Department of OneHow Tweaky.com scopes, builds, and validates featuresPJ MurrayCofounder and CTO - Tweakypj@tweaky.comFriday, 7 June 13
  • 2. IT Department of OneWhat I’m going to cover- How I got here- Scoping-Building-ValidatingFriday, 7 June 13
  • 3. My StoryIT Department of OneFriday, 7 June 13
  • 4. IT Department of OneFriday, 7 June 13
  • 5. IT Department of OneFriday, 7 June 13
  • 6. IT Department of OneFriday, 7 June 13
  • 7. IT Department of OneFriday, 7 June 13
  • 8. KickoffIT Department of OneFriday, 7 June 13
  • 9. Scoping FeaturesIT Department of OneFriday, 7 June 13
  • 10. Capture IdeasIT Department of OneFriday, 7 June 13
  • 11. EXAMPLE -Purchase CreditsIT Department of OneFriday, 7 June 13
  • 12. IT Department of OneFriday, 7 June 13
  • 13. IT Department of OnePurchaseFriday, 7 June 13
  • 14. IT Department of OnePurchaseViewInvoiceMul2pleCreditOp2onsViewBalanceRequestRefundCredits  ExpireUseCredits  Transfer  CreditsFriday, 7 June 13
  • 15. DON’TIT Department of One- Get stuck in technical implementation- Get distracted by shiny “cool” things- Overcomplicate thingsFriday, 7 June 13
  • 16. IT Department of OneMVPFriday, 7 June 13
  • 17. IT Department of OneMoSCoWFriday, 7 June 13
  • 18. IT Department of OneMoSCoWMust Have Should HaveCould Have Wont HaveFriday, 7 June 13
  • 19. IT Department of OneMust Have Should Have Nice to HaveFriday, 7 June 13
  • 20. IT Department of OneMust Have Should Have Nice to HaveDOFriday, 7 June 13
  • 21. How do I know what a “Must Have” is?IT Department of OneFriday, 7 June 13
  • 22. Understand the ValueIT Department of One- What assumption is the feature based on?- Will it still work without x, y or z?- Question everythingFriday, 7 June 13
  • 23. IT Department of OnePurchaseViewInvoiceMul2pleCreditOp2onsViewBalanceRequestRefundCredits  ExpireUseCredits  Transfer  CreditsFriday, 7 June 13
  • 24. IT Department of OnePurchaseViewInvoiceMul2pleCreditOp2onsViewBalanceRequestRefundCredits  ExpireUseCredits  Transfer  CreditsFriday, 7 June 13
  • 25. IT Department of OnePurchaseViewInvoiceMul2pleCreditOp2onsViewBalanceRequestRefundCredits  ExpireUseCredits  Transfer  CreditsFriday, 7 June 13
  • 26. IT Department of OneValue is still only an assumptionFriday, 7 June 13
  • 27. IT Department of OneMust Have Should Have Nice to HaveDOFriday, 7 June 13
  • 28. IT Department of OneMust Have Should Have Nice to HaveDON’TFriday, 7 June 13
  • 29. IT Department of OneDefine a Success MetricFriday, 7 June 13
  • 30. IT Department of OneHow do we know thatthe 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- SessionsFriday, 7 June 13
  • 32. IT Department of OnePick OneFriday, 7 June 13
  • 33. IT Department of OneDiscovery and ValidationFriday, 7 June 13
  • 34. IT Department of OneFriday, 7 June 13
  • 35. Building FeaturesIT Department of OneFriday, 7 June 13
  • 36. It’s never “just” a form fieldIT Department of OneFriday, 7 June 13
  • 37. IT Department of OneCode you don’t write is:1. Code you don’t have to test2. Code you don’t have to maintainFriday, 7 June 13
  • 38. Don’t Build Any Of ItIT Department of One(if you don’t have to)Friday, 7 June 13
  • 39. IT Department of OneFriday, 7 June 13
  • 40. EXAMPLE -Tweaky Success CallsIT Department of OneFriday, 7 June 13
  • 41. Don’t Build All of ItIT Department of OneFriday, 7 June 13
  • 42. Leverage Existing ToolsIT Department of OneFriday, 7 June 13
  • 43. IT Department of OneFriday, 7 June 13
  • 44. Reuse Existing CodeIT Department of OneFriday, 7 June 13
  • 45. EXAMPLE -Tweaky Credits and CouponsIT Department of OneFriday, 7 June 13
  • 46. EXAMPLE -Social Share and AffiliatesIT Department of OneFriday, 7 June 13
  • 47. KISSIT Department of One(keep it simple stupid)Friday, 7 June 13
  • 48. No Software WankIT Department of OneFriday, 7 June 13
  • 49. IT Department of OneTestingFriday, 7 June 13
  • 50. IT Department of OneWhen It’s High RiskFriday, 7 June 13
  • 51. IT Department of OneWhen Things FailFriday, 7 June 13
  • 52. IT Department of OneSome SafetyFriday, 7 June 13
  • 53. Ship Broken CodeIT Department of OneFriday, 7 June 13
  • 54. IT Department of OneA un-deployed feature with100% test coverage is100% worthlessFriday, 7 June 13
  • 55. IT Department of OneBake in MetricsFriday, 7 June 13
  • 56. Technical DebtIT Department of OneFriday, 7 June 13
  • 57. IT Department of OneValidatingFriday, 7 June 13
  • 58. IT Department of OneUnderstand the QuestionFriday, 7 June 13
  • 59. IT Department of OneDon’t be TrickyFriday, 7 June 13
  • 60. IT Department of OneMake it VisibleFriday, 7 June 13
  • 61. IT Department of OneReview, Learn and IterateFriday, 7 June 13
  • 62. IT Department of OneHow Tweaky.com scopes, builds, and validates featuresPJ MurrayCofounder and CTO - Tweakypj@tweaky.comFriday, 7 June 13