1 / 18

How we build Redfin

How we build Redfin.com. Matt Goyer Lead Product Manager. What We’ll Chat About. Who Am I? How We Do It At Redfin Who does what Team structure What next? Offsite Focus group Survey Spec it, Code it, Try it, Test it Release it Feedback Conclusion. Who Am I?.

bmcclure
Download Presentation

How we build Redfin

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. How we build Redfin.com Matt Goyer Lead Product Manager

  2. What We’ll Chat About • Who Am I? • How We Do It At Redfin • Who does what • Team structure • What next? • Offsite • Focus group • Survey • Spec it, Code it, Try it, Test it • Release it • Feedback • Conclusion

  3. Who Am I? • University of Waterloo • B.Math (Computer Science) • Distracted by startups • Microsoft • Program Manager on Windows Media Center • Redfin • Lead Product Manager for Search

  4. Who Does What? • Program/Product Manager (PM) • Customer representative • Co-ordinates design, development and QA • Designer • Makes it pretty • Software Development Engineer (SDE) • Writes the code • Software Development Engineer in Test (SDET or QA) • Tests the code by writing more code

  5. Team Structure • “Feature Teams” • Commerce • Data • Query and Statistics • Search • Made up of: • 1 PM • 1 QA • 3 Developers

  6. What Do We Do Next? • Listen to Customers • Surveys • Emails from customers • Forums • Blogs • Watch Competitors • Watch Related Companies

  7. Offsite • What happens: • Presentations • Brainstorm • Think outside the box • What is produced: • Vision • Goals • Tentative feature plan

  8. Focus Group • Invite 10 customers • Two hours • Talk about what they like • Talk about what they don’t like • Summarize that night • Send out plan

  9. From Idea to Booked Work • Survey • Confirm plan • Tools • Zoomerang • Survey Monkey • Communicate plan • Present to leadership team • Present to company

  10. Functional Specification • Problems and Opportunities • Feature Breakdown and Priorities • User Scenarios • Success Metrics • User Interface Design • Requirements & Dependencies • Reporting & Analytics • Performance

  11. Schedule • Why? • A commitment • Tool to track progress • Rule of thirds • Plan • Code • Test

  12. Code It • Design spec • What did we forget? • Track against schedule • Have fun!

  13. User Test It • How? • Hallway usability • Usability test • What? • Recruit participants • Draw up a plan • Don’t lead the witness

  14. Quality Assurance • Bugs? • No one is perfect • Bugs not all equal • Priority/Severity • Database • Finding them • Test Plan • Test Pass • Bug Bash • Triage

  15. Release • What’s driving you? • Quality vs. Date • Get to zero bugs • Release Candidates (RC0, RC1,…) • Release to operations (RTO) • Release to web (RTW) • Get the word out • Press release • Engage bloggers • Social network

  16. Feedback • Numbers • Analytics • Metrics • People • Tech support • Forums • Blogs

  17. Recommended Reading • Joel On Software • By Joel Spolsky • Also a blog: http://www.joelonsoftware.com • The Art of Project Management • By Scott Berkun

  18. Questions? • mail@mattgoyer.com • http://blog.mattgoyer.com

More Related