Slide 1

Slide 1 text

Feature Injection discovering and delivering testable value @helmedeiros

Slide 2

Slide 2 text

They’re using it well, all or almost all functionalities delivered we need to delivery more functionalities but this is a 3 person application! how are they using this so far? Do we have sure about it? The product isn’t helping us to really do what we wan’t PROJECT IS SHELVED SIT THAT THERE COMES HISTORY Our development time finished.

Slide 3

Slide 3 text

LAYERING-DRIVEN DEVELOPMENT

Slide 4

Slide 4 text

I REALLY DON’T CARE WITH BUSINESS VALUE-DRIVEN DEVELOPMENT

Slide 5

Slide 5 text

SIT THAT THERE COMES HISTORY

Slide 6

Slide 6 text

SIT THAT THERE COMES HISTORY

Slide 7

Slide 7 text

SIT THAT THERE COMES HISTORY

Slide 8

Slide 8 text

SIT THAT THERE COMES HISTORY

Slide 9

Slide 9 text

SIT THAT THERE COMES HISTORY

Slide 10

Slide 10 text

No content

Slide 11

Slide 11 text

EVERYONE LOVES TO SAY HOW IT SHOULD BE DONE

Slide 12

Slide 12 text

AND OFTEN IS NOT NECESSARY!

Slide 13

Slide 13 text

THE VALUE OFTEN GETS LOST PASSING THROUGH LAYERS

Slide 14

Slide 14 text

NOTHING. I have read a book that speaks of simplicity. we need to know our users. Let's use a third party that is very simple! is there any restriction on integration? What needs to be learned to integrate it? TONS OF PROBLEMS! We are not advancing We lost a lot of time the system is no longer needed PROJECT IS SHELVED But what is our strategy? WHAT’S OUR PROBLEM? ? WHAT’S THE GOAL? ? WHAT WE SHOULD DO? ? HOW FREQUENT IT CHANGE? ? WHAT’S RESTRIC US? ? WHO DOES BUSINESS? ? WHAT’S THE VALUE? ? SIT THAT THERE COMES HISTORY

Slide 15

Slide 15 text

NADA. Lí um livro que fala da simplicidade. precisamos conhecer nossos usuários. Vamos usar um third party que é muito simples! existe alguma restrição na integração? O que precisa ser aprendido para integrá-lo? MUITO PROBLEMAS! Não estamos avançando Perdemos muito tempo o sistema não é mais necessário PROJETO ARQUIVADO ISN’T IT TOO MUCH INFORMATION? paralysis of analysis

Slide 16

Slide 16 text

FEATURE INJECTION! - maybe it can help you -

Slide 17

Slide 17 text

FEATURE INJECTION

Slide 18

Slide 18 text

FEATURE INJECTION Hunting the value ONE STRATEGY three steps 1 Injecting the value 2 Detailing by example 3

Slide 19

Slide 19 text

HUNTIG THE VALUE Solution? Problem? goal? USER STORY x

Slide 20

Slide 20 text

5 whys 1 2 3 ? HOW WE CAN DO IT WHY? WHY? WHY? WHY? WHY? HUNTIG THE VALUE

Slide 21

Slide 21 text

elevator pitch HOW WE CAN DO IT HUNTIG THE VALUE

Slide 22

Slide 22 text

BUSINESS MODEL CANVAS

Slide 23

Slide 23 text

FEATURE INJECTION Hunting the value ONE STRATEGY three steps 1 Injecting the value 2 Detailing by example 3

Slide 24

Slide 24 text

discover the outputs VALUE DRIVEN ! what’s our MVP? ! making assumptions ! make it clear !

Slide 25

Slide 25 text

VALUE DRIVEN what’s our MVP? !

Slide 26

Slide 26 text

VALUE DRIVEN making assumptions ! USER STORY ASSUMPTION METRICS

Slide 27

Slide 27 text

FEATURE INJECTION Hunting the value ONE STRATEGY three steps 1 Injecting the value 2 Detailing by example 3

Slide 28

Slide 28 text

JEFFREYFISHER DETAILING BY EXAMPLE Questions risk assumption information unknown known

Slide 29

Slide 29 text

BDD given when then NOSSAS FERRAMENTAS DETAILING BY EXAMPLE MY USER WILL LOVE TO USE THE CORE FEATURE WITH BEHAVIOUR A GIVEN my user open the page WHEN he use the core feature with behaviour A THEN we should do something and we should track if he is rolling and spending more than 5 min in it HOW WE CAN DO IT WE NEED TESTS AND METRICS THAT COULD BREAK! BUT THEY SHOULD BE CLOSER TO THE REAL USERS AND ALL ABOUT HOW THEY USE THAT!

Slide 30

Slide 30 text

MARKETING ENGINEERING PRODUCT DETAILING BY EXAMPLE CUSTOMER LIFE CYCLE ACQUISITION ACTIVATION RETENTION REFERRAL REVENUE

Slide 31

Slide 31 text

As a I want so that In Order To 
 As a 
 I want mike cohn chris matts DETAILING BY EXAMPLE HOW WE CAN DO IT

Slide 32

Slide 32 text

APERFEIÇOANDO COM AS CRÍTICAS Fail Fast, Succeed Faster!

Slide 33

Slide 33 text

NADA. Lí um livro que fala da simplicidade. precisamos conhecer nossos usuários. Vamos usar um third party que é muito simples! existe alguma restrição na integração? O que precisa ser aprendido para integrá-lo? MUITO PROBLEMAS! Não estamos avançando Perdemos muito tempo o sistema não é mais necessário PROJETO ARQUIVADO DO YOU RECOGNISE IT? AGILE CYCLE

Slide 34

Slide 34 text

VALUE DRIVEN KANBAN BUILD MESURE LEARN PRODUCT IDEAS DATA

Slide 35

Slide 35 text

SIT THAT THERE COMES HISTORY

Slide 36

Slide 36 text

SIT THAT THERE COMES HISTORY

Slide 37

Slide 37 text

SIT THAT THERE COMES HISTORY

Slide 38

Slide 38 text

Feature Injection discovering and delivering testable value @helmedeiros