Building a Great Product Through Communication - Joe Stump

458 views

Published on

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

  • Be the first to like this

No Downloads
Views
Total views
458
On SlideShare
0
From Embeds
0
Number of Embeds
25
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Building a Great Product Through Communication - Joe Stump

  1. 1. Building a Great Product Through Communication Joe Stump, CEO of Sprint.lyFriday, February 8, 13
  2. 2. About Joe Stump • Early employee at three startups ranging from bootstrapped to venture funded. • Angel investor in three startups. • Advisor to seven venture funded startups. • Cofounder of three venture funded startups (SimpleGeo, attachments.me, & Sprint.ly). • @joestump or joe@stu.mpFriday, February 8, 13
  3. 3. Warring FactionsFriday, February 8, 13
  4. 4. Business PMs Makers Stakeholders Faction A Mediators Faction BFriday, February 8, 13
  5. 5. Meetings :( Meetings :( Business PMs Makers Stakeholders Faction A Mediators Faction BFriday, February 8, 13
  6. 6. Check Your EgoFriday, February 8, 13
  7. 7. EVERYONE IN YOUR COMPANY IS CAPABLE OF HAVING A GREAT IDEA.Friday, February 8, 13
  8. 8. Quickly Correctly CheaplyFriday, February 8, 13
  9. 9. YOU CAN’T HAVE YOUR CAKE AND EAT IT TOO.Friday, February 8, 13
  10. 10. “Want to increase innovation? Lower the cost of failure.” Joi ItoFriday, February 8, 13
  11. 11. ALLOW ENGINEERS TO INVEST IN AUTOMATION & TESTING.Friday, February 8, 13
  12. 12. Why? • Iterating on your product is all about shortening feedback loops • Continuous deployment allows you to ship on code commit • Automated testing allows for aggressive refactoring with confidenceFriday, February 8, 13
  13. 13. Product is Trench WarfareFriday, February 8, 13
  14. 14. PRODUCTS ARE EITHER DATE- DRIVEN OR FEATURE-DRIVEN.Friday, February 8, 13
  15. 15. Non-Blocking Development (NBD) 1. No sprints, milestones, or dates are tracked by engineering 2. Items are scored, velocity is tracked 3. Each developer works on an item to completion in a feature branch 4. Pull request via GitHub for review 5. Feature deployed immediately upon approval via continuous deploymentFriday, February 8, 13
  16. 16. Why is this better? • Shares reactive qualities of Kanban • Velocity metrics allow you to do reasonable capacity planning • Features ship in real-time as they’re completedFriday, February 8, 13
  17. 17. Friday, February 8, 13
  18. 18. Our tools are broken • Used as enforcers of messy human process • Require humans / data entry to ensure it “represents reality” • Tools often paradigm-specific; everyone is a little differentFriday, February 8, 13
  19. 19. WE NEED TO MOVE TO 100% ASYNCHRONOUS COMMUNICATIONFriday, February 8, 13
  20. 20. Why? • Look at production operations management approach of monitor/react over push/plan • Hard to be agile when only 10% of the business is agile • Globalization is real, workers spread across regionsFriday, February 8, 13
  21. 21. “You can’t ship process.” VP of Product, Live Nation LabsFriday, February 8, 13
  22. 22. @joestumpFriday, February 8, 13

×