Your SlideShare is downloading. ×
0
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Agile Business Development
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Agile Business Development

1,216

Published on

JRubyConf, May 2012 …

JRubyConf, May 2012
Test-driven development is mom-and-apple-pie to Rubyists, but knowing that a product will work goes well beyond bug-free code. How do you catch a design flaw early when all your tests are green? We'll look at some techniques for vetting your go-to-market strategy and other things you should be doing *before* you start writing code.

Published in: Business, Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,216
On Slideshare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
14
Comments
0
Likes
2
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. Agile BusinessDevelopment
  • 2. Sarah Allen@ultrasaurus
  • 3. Sarah Allen@ultrasaurus
  • 4. Sarah Allen@ultrasaurus
  • 5. AgileBusiness Development
  • 6. agile is what works 6
  • 7. Individuals and Interactions Responding to Change Customer Collaboration Working Software
  • 8. Individuals and Interactions
  • 9. “Culture eats strategy for breakfast.” — Peter Drucker
  • 10. Diversity Breeds Innovation
  • 11. Responding to Change
  • 12. “Learning is the essential unit of progress for start-ups.” — Eric Ries
  • 13. learn: what do we know? (numbers are good)hypothesis: what do we believe? (numbers are good)test: how can we check against reality?analyze: does the data support our hypothesis?
  • 14. 14
  • 15. Vision 15
  • 16. VisionMeasurable goal 16
  • 17. Vision Measurable goalWhat do we know? 17
  • 18. Vision Measurable goalWhat do we know?What do we believe? 18
  • 19. Vision Measurable goal What do we know? What do we believe?Simplest Thing That Could Possibly Work 19
  • 20. Vision Measurable goal What do we know? What do we believe?Simplest Thing That Could Possibly Work Test 20
  • 21. Vision Measurable goal What do we know? What do we believe?Simplest Thing That Could Possibly Work Test iterate 21
  • 22. Example 22
  • 23. RailsBridgeOpen Workshops 23
  • 24. An Open & Inclusive Tech Communitywhat if the people who make software were representative of the general population? 24
  • 25. Measurable Goal:Increase the number of Women at SFRuby Meetups 25
  • 26. What do we know? 26
  • 27. About 70 attendees 2 women = 3%GoGaRuCo 200 attendees 6 women = 3% 27
  • 28. What do we believe? 28
  • 29. More women programmers than Ruby programmers 29
  • 30. There are women interested inlearning Ruby on Rails who aren’t in the room. 30
  • 31. the simplest thing that could possibly work: teach women Ruby on Rails 31
  • 32. 32
  • 33. Next Step... 33
  • 34. What do we know? 34
  • 35. Demand is not a problem easy to find women who want to learn Ruby on Rails 35
  • 36. Teaching Women RailsIncreases Number of Women 36
  • 37. Beware of the false summit! 37
  • 38. 38 workshops 12 cities spin-offs RailsGirls PyStar Python Ladies Scala Learn the Front EndConfident Coding JS 38
  • 39. Measure Twice Cut Once 39
  • 40. Customer Collaboration 40
  • 41. Customer Collaboration 41
  • 42. 42
  • 43. 43
  • 44. Example 44
  • 45. Mightyverse 45
  • 46. CommunicationAcross Language and Culture using SmartPhones, video and the Internet we can provide an innovative & effective solution 46
  • 47. Measurable Goal? 47
  • 48. Value HypothesisGrowth Hypothesis 48
  • 49. $Value HypothesisGrowth Hypothesis 49
  • 50. $Value HypothesisGrowth Hypothesis 50
  • 51. $ mobile video is usefulfor communicating across language & culture 51
  • 52. 52
  • 53. people are looking for language resources thorough Web search 53
  • 54. “How can you say...” Google Searches in Englishhttp://www.google.com/trends?q=how+do+you+say&ctab=0&geo=all&date=all&sort=0 Google
  • 55. “How can you say...” Google Searches in Spanish Google
  • 56. Increased Web Traffic
  • 57. Working Code 57
  • 58. 58
  • 59. learn: record baseline metrics from real customershypothesis: Pivotal Tracker story with UI change + hypothesistest: deploy the featureanalyze: validate hypothesis based on feature usage metrics
  • 60. BLAZING PATH 60
  • 61. Questions? 61

×