Post on 22-Jun-2015
description
Crafting the Product: How the Product Backlog appears
Galina KostetskayaEngineering Manager
01/10/2014
Plan• Plan, Do, Check, Act• Hypothesis• Personas, Scenarios -> Features• Prototyping and prototypes testing• Story mapping• MVP, releases planning
3© Copyright Innovecs 2012
Product owner
4© Copyright Innovecs 2012
5© Copyright Innovecs 2012
Product owner
• responsible for the product success
• has the vision of there to take the product
• cares about user needs and business goals
• team player : dev team and stakeholders
• owns the product on behalf of the company
6© Copyright Innovecs 2012
Plan, Do, Check, and Act
• Develop a hypothesis about your product;Validate it (through user tests, interviews, fast researches); Review the result;If the experiment was unsuccessful, adapt the hypothesis;
•
••
7© Copyright Innovecs 2012
Hypothesis
We believe [TYPE OF USER] has a problem [DOING THING]. We can help them with [OUR SOLUTION]. We'll know we're right if [CHANGE IN METRIC].
8© Copyright Innovecs 2012
Validate: Personas
Personas are your consumers archetypes with names, jobs, skills, interests and anything that is relevant to how they use your product.
9© Copyright Innovecs 2012
Scenarios
that envision their life with your product and without it. Try to answer the question: Are the features you envisioned really necessary? Does your persona get benefit from using your product?
10
© Copyright Innovecs 2012
Interviewing your users
The most important thing is to find people who are representative of target users of your system. The people who are going to be the users of your system.
10© Copyright Innovecs 2012
The main problem
The main problem is that a lot of people think, that there is nothing new to be found – everything is known, everything is discovered.
12© Copyright Innovecs 2012
Solution
13© Copyright Innovecs 2012
Validate it: Prototyping
14© Copyright Innovecs 2012
Prototyping
15© Copyright Innovecs 2012
Testing prototypes• Make an interactive application without writing much code: front-end interface, which is controlled by the wizard.
• Get feedback from users• Makes sense when it is faster/easier/cheaper to make the than the real thing
16© Copyright Innovecs 2012
Testing prototypes
17© Copyright Innovecs 2012
Story mapping
18© Copyright Innovecs 2012
Story mapping
19© Copyright Innovecs 2012
MVP(Minimum viable product)
is the core features that allow the product to be deployed, and no more.
MVP - the least amount of work we can do to validate the hypothesis
20© Copyright Innovecs 2012
MVP
+ release plan
20© Copyright Innovecs 2012
What if hypothesisis proven to be wrong?
22© Copyright Innovecs 2012
Find a new one!
23© Copyright Innovecs 2012
Fail fast - learn fast
24© Copyright Innovecs 2012
Thank you!
Galina KostetskayaEngineering Manager