Lecture 14: Product Management

431 views
337 views

Published on

In this lecture Poornima covers how to manage product developmen by breaking down features into stories, prioritizing what needs to get built, and the importance of putting a process in place to ship consistently.

You can watch the lecture here: http://youtu.be/kUildbwzdrY

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

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

No notes for slide

Lecture 14: Product Management

  1. 1. Duke ECE 490L: How to Start New Ventures in Electrical and Computer Engineering Poornima Vijayashanker poornima@femgineer.com Jeff Glass jeff.glass@duke.edu Akshay Raut ar118@duke.edu 1
  2. 2. Review • Collect Feedback from Customers • Create Team Alignment • How to Create Product Roadmap • How to Pick Features for a MVP Duke ECE 490L 2
  3. 3. Announcements • Lab 3 is out! • No office hours next Wednesday. Duke ECE 490L 3
  4. 4. Review Session: Wednesday October 23, 2013 DUHatch Idea Summary Sign up for a session here! 4
  5. 5. Agenda • Breaking down stories into features • Prioritizing product development • Process for shipping consistently • Exercise Duke ECE 490L 5
  6. 6. Rework Measure Feedback Customer Discovery Process. Release. Usability Testing Product Roadmap Build. Feasibility given resources. Duke ECE 490L 6
  7. 7. ANATOMY OF A PRODUCT ROADMAP 1. Infrastructure 2. New Features 3. Customer Requests Sept 2011 Product Development Oct 2011 Reporting for Payment Tax time Gateway Integration Integrate with Monthly Email Optimize Attendance • retention • re-engagement Dec 2011 Jan 2012 Feb 2012 • new customers • new source of revenue based on % transaction Customize reminder emails for member retention Multiple Login Scheduling Integrated with Online Store QuickBooks Summary Business Benefit Nov 2011 • retention • new customers • retention • new customers • retention • new customers • new customers • larger studios • increase  revenue Business Goal of Feature 7
  8. 8. Business Goal Feature Story Mental Models Duke ECE 490L 8
  9. 9. Mental Models • Interview user segments • Collect feedback • Comb for tasks • Looks for patterns • Match personas to tasks • Tasks become stories Duke ECE 490L 9
  10. 10. Tasks Travels to teach yoga. Yoga Instructor Teaches yoga. Takes attendance. Asks for payment. Yoga Studio Owner Teaches at one studio. Duke ECE 490L 10
  11. 11. Business goal: user acquisition We want people to sign up! Duke ECE 490L 11
  12. 12. Feature: Sign up form Duke ECE 490L 12
  13. 13. Persona (mental model): Yoga studio owner Duke ECE 490L 13
  14. 14. Tell me a story. Duke ECE 490L 14
  15. 15. High Level Story: As a yoga studio owner, I’d like to sign up for site that let’s me take attendance. Duke ECE 490L 15
  16. 16. Need to get a little more granular. Duke ECE 490L 16
  17. 17. Story: As a yoga studio owner, to sign up the sign up form needs to ask me for valid email and strong password. Duke ECE 490L 17
  18. 18. 1 story becomes multiple stories. Duke ECE 490L 18
  19. 19. Story 1: As a yoga studio owner, to sign up the sign up form needs to ask me for valid email and strong password. Story 2: As a yoga studio owner, if I enter an email address that is already in use I need to receive a warning. Story 3: As a yoga studio owner, if I enter a password that isn’t strong I need to receive a warning. Duke ECE 490L 19
  20. 20. We need to prioritize. Duke ECE 490L 20
  21. 21. To prioritize need to factor complexity. Duke ECE 490L 21
  22. 22. What is complexity? Duke ECE 490L 22
  23. 23. Complexity is the relative difficulty of building. Duke ECE 490L 23
  24. 24. Shipping consistently is about putting a process in place. Duke ECE 490L 24
  25. 25. Storytime: process. Duke ECE 490L 25
  26. 26. Your process will evolve. Duke ECE 490L 26
  27. 27. Expect it to! Duke ECE 490L 27
  28. 28. “You have to be agile in your approach to agile.” John Quinn VP of Engineering at Gilt Group 28
  29. 29. Scope creep. Duke ECE 490L 29
  30. 30. AGILE MANIFESTO CUSTOMER COLLABORATION over CONTRACT NEGOTIATION INDIVIDUALS AND INTERACTIONS over PROCESSES AND TOOLS RESPONDING TO CHANGE over FOLLOWING A PLAN WORKING SOFTWARE over INVEST IN AUTOMATION AND ASYNCHRONOUS FULL DOCUMENTATION Duke ECE 490L 30
  31. 31. 3 user story buckets Someday Backlog Current Duke ECE 490L 31
  32. 32. Tools Duke ECE 490L 32
  33. 33. Prioritizing Stories • Building the basics. • Breading down stories into basic components. • Handling scope creep • Re-prioritizing stories. • Test (internally) + Ship + Test (early adopters) Duke ECE 490L 33
  34. 34. Someday: unsorted stories Backlog: prioritized stories Current: started stories Duke ECE 490L 34
  35. 35. Demo. Duke ECE 490L 35
  36. 36. PRODUCT DEVELOPMENT 36 36
  37. 37. Bugs. Duke ECE 490L 37
  38. 38. Rework Measure Feedback (Improvements and Enhancements) Customer Discovery Process. Release. Usability Testing Product Roadmap Build. Feasibility given resources. Duke ECE 490L 38
  39. 39. Understand your speed. Duke ECE 490L 39
  40. 40. Understand your team’s speed. Duke ECE 490L 40
  41. 41. Building a Sustainable Business Iterate on Product Grow a Team Ship Product Scale Customer Acquisition Fundraising Duke ECE 490L 41
  42. 42. Break it down to the most basic value proposition. Duke ECE 490L 42
  43. 43. EXERCISE KEY OBJECTIVE(S) AGENDA Understand how to build a feature within the context of a business goal, and break it down into stories. 10 minutes 1.Choose a business goal from last week’s product roadmap exercise. 2.Pick one feature. 3.Break the feature down into stories. 4.Highlight scope creep! DELIVERABLE RESOURCES Stories for one feature. Sprint.ly 43
  44. 44. Review • Breaking down stories into features • Prioritizing product development • Process for shipping consistently • Exercise Duke ECE 490L 44

×