Lecture 14: Product Management

Preview:

DESCRIPTION

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

Citation preview

Duke ECE 490L: How to Start New Ventures in Electrical and Computer Engineering

Poornima Vijayashankerpoornima@femgineer.com

Jeff Glass jeff.glass@duke.edu

Akshay Rautar118@duke.edu

1

Review

Duke ECE 490L

• Collect Feedback from Customers

• Create Team Alignment

• How to Create Product Roadmap

• How to Pick Features for a MVP

2

Announcements

Duke ECE 490L

• Lab 3 is out!

• No office hours next Wednesday.

3

Agenda

Duke ECE 490L

• Breaking down stories into features

• Prioritizing product development

• Process for shipping consistently

• Exercise

5

Duke ECE 490L

Process.

Customer Discovery

Release.

Build.Measure

Rework Usability TestingProduct Roadmap

Feasibility given resources.

Feedback

6

Sept 2011 Oct 2011 Nov 2011 Dec 2011 Jan 2012 Feb 2012

ProductDevelopment

Optimize Attendance

Monthly Email Summary

Payment Gateway Integration

Reporting for Tax time

Integrate with QuickBooks

Customize reminder emails for member retention

Multiple Login Scheduling Integrated with Online Store

Business Benefit

• retention• re-engagement

• new customers• new source of

revenue based on % transaction

• retention• new customers

• retention• new customers

• retention• new customers

• new customers• larger studios• increase 

revenue

1. Infrastructure 2. New Features 3. Customer Requests

Business Goal of Feature

ANATOMY OF A PRODUCT ROADMAP

7

Duke ECE 490L

Business Goal

Feature

Story

Mental Models

8

Mental Models

Duke ECE 490L

• Interview user segments

• Collect feedback

• Comb for tasks

• Looks for patterns

• Match personas to tasks

• Tasks become stories

9

Duke ECE 490L

Yoga Instructor Teaches yoga.

Takes attendance.

Asks for payment.

Yoga Studio Owner Teaches at one studio.

Travels to teach yoga.

Tasks

10

Duke ECE 490L

We want people to sign up!Business goal: user acquisition

11

Duke ECE 490L

Sign up formFeature:

12

Duke ECE 490L

Persona (mental model):

Yoga studio owner

13

Duke ECE 490L

Tell me a story.

14

Duke ECE 490L

As a yoga studio owner, I’d like to sign up for site that let’s me take attendance.

High Level Story:

15

Duke ECE 490L

Need to get a little more granular.

16

Duke ECE 490L

As a yoga studio owner, to sign up the sign up form needs to ask me for valid email and strong password.

Story:

17

Duke ECE 490L

1 story becomes multiple stories.

18

Duke ECE 490L

As a yoga studio owner, to sign up the sign up form needs to ask me for valid email and strong password.

Story 1:

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.

19

Duke ECE 490L

We need to prioritize.

20

Duke ECE 490L

To prioritize need to factor complexity.

21

Duke ECE 490L

What is complexity?

22

Duke ECE 490L

Complexity is the relative difficulty of building.

23

Duke ECE 490L

Shipping consistently is about putting a process in place.

24

Duke ECE 490L

Storytime: process.

25

Duke ECE 490L

Your process will evolve.

26

Duke ECE 490L

Expect it to!

27

“You have to be agile in your approach to agile.”

John QuinnVP of Engineering at Gilt Group

28

Duke ECE 490L

Scope creep.

29

Duke ECE 490L

AGILE MANIFESTO

overCUSTOMER COLLABORATION

CONTRACTNEGOTIATION

overINDIVIDUALS AND INTERACTIONS

PROCESSESAND TOOLS

overRESPONDING TO CHANGE

FOLLOWING APLAN

overWORKING SOFTWARE

FULLDOCUMENTATION

INVEST INAUTOMATION

ANDASYNCHRONOUS

over

over

over

30

Duke ECE 490L

3 user story buckets

SomedayBacklogCurrent

31

Duke ECE 490L

Tools

32

Prioritizing Stories

Duke ECE 490L

• Building the basics.• Breading down stories into basic components.• Handling scope creep• Re-prioritizing stories.• Test (internally) + Ship + Test (early adopters)

33

Duke ECE 490L

Someday: unsorted storiesBacklog: prioritized stories

Current: started stories

34

Duke ECE 490L

Demo.

35

PRODUCT DEVELOPMENT 36

36

Duke ECE 490L

Bugs.

37

Duke ECE 490L

Process.

Customer Discovery

Release.

Build.Measure

Rework Usability TestingProduct Roadmap

Feasibility given resources.

Feedback(Improvements and Enhancements)

38

Duke ECE 490L

Understand your speed.

39

Duke ECE 490L

Understand your team’s speed.

40

Duke ECE 490L

Ship Product

Fundraising

Scale Customer Acquisition

Grow a TeamBuilding a Sustainable Business

Iterate on Product

41

Duke ECE 490L

Break it down to the most basic value proposition.

42

KEY OBJECTIVE(S) AGENDA

RESOURCESDELIVERABLE

EXERCISE

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!

Stories for one feature. Sprint.ly

43

Review

Duke ECE 490L

• Breaking down stories into features

• Prioritizing product development

• Process for shipping consistently

• Exercise

44

Recommended