Logo Passei Direto
Buscar
Material
páginas com resultados encontrados.
páginas com resultados encontrados.

Escolha uma das opções e acesse esse e outros materiais sem bloqueio. 🤩

Cadastre-se ou realize login

Ao continuar, você aceita os Termos de Uso e Política de Privacidade

Escolha uma das opções e acesse esse e outros materiais sem bloqueio. 🤩

Cadastre-se ou realize login

Ao continuar, você aceita os Termos de Uso e Política de Privacidade

Escolha uma das opções e acesse esse e outros materiais sem bloqueio. 🤩

Cadastre-se ou realize login

Ao continuar, você aceita os Termos de Uso e Política de Privacidade

Prévia do material em texto

Hypothesis-Driven Development 
 
 
 
 
 
 
Rogerio Mendes Ferreira: Creating and Testing a Demand/Value Hypothesis 
Part 1: Formulate a Positioning Statement 
For Simeon who needs to improve your own software called EPA, the RMF Consulting is a group of IT experts that delivery a huge quality in code review and 
people management. Unlike others consulting companies, our product brings what you need and more than you expect. 
 
Part 2: Sketch a Demand/Value Hypothesis 
Assignment Body 
Problem Scenarios/Jobs-to-be-Done Current Alternatives Your Demand/Value Hypothesis 
How to deliver new features with high quality? 1. Basing in business strategy 
2. Implementing code review process 
3. Using Agile Methodologies 
4. Building a code with a based DEV Team 
1. If we works based on business strategy then 
the new features will be aligned on market 
research 
2. If we implement a code review process then 
the code quality will be better 
3. If we start to use Agile Methodologies then the 
DEV Team will be more engaged 
 
 
Hypothesis-Driven Development 
 
 
 
 
 
 
Rogerio Mendes Ferreira: Creating and Testing a Demand/Value Hypothesis 
Part 3: Sketch Three Experiments via MVP 
Experiment Ideas 
 
# What type? How would it work? What observations? 
1 Concierge We’ll find one or two features who needs to be 
proved. Working from the technical and 
functional requirements, we’ll draft a MVP and 
make it available to them Figma (software used 
for prototyping). We’ll watch for customers 
inputs and return the DEV Team grades. 
First off, we’ll look at whether they actually use the 
MVP (prototype) or not. We’ll want to make sure 
they’re willing to tell us (and track) how many 
customers have clicked on that. Since we’re mostly 
looking at how this thing might work for them, we 
would check in weekly and make ourselves available 
for questions and help. 
 
Next, we’d look at if/whether it helped- the 
customers. We’d do this at the end of the process, 
after they build a final version of this features. 
2 Wizard of Oz We’d make the product available to a limited 
set of users and have them supply the inputs 
Does anyone do this? Where do they drop off? 
 
 
Hypothesis-Driven Development 
 
 
 
 
 
 
Rogerio Mendes Ferreira: Creating and Testing a Demand/Value Hypothesis 
we anticipate using for them to suggest new 
features. After they submit those inputs, we’d 
post back to them a message saying ‘Thanks!’ 
Can we make what we think is a good ffeature from 
the inputs they supply? If not, that’s a sign we need 
to rethink the process.

Mais conteúdos dessa disciplina