UDD steps for software development (based on Steve Blank's Four Steps for customer development):
The goal from each step is increase its metrics. And than, build the next step cheaper.
From Enterprises to Startups, software projects mostly fail from skipping the validation phase. Teams normally jump from the ideation straight to development assuming that they already know what users want. And then, they stay for a long amount of time at the development phase, building new features continually before confronting them with real users.
The idea of the User Driven Development methodology is to add the user interaction practices to the Agile process. In other words, to drive the team to test the most valuable features earlier, having a chance to don't spend time developing useless features and stoping enhancing the code as soon as the users agree that the existing development is already good enough.
Ideation |
Validation |
Development |
Scaling |
|||
 |
 |
 |
|
|||
| BUILD:
Vision Statement
Lean UX
(Persona & Uses) |
BUILD:
Production Environment
New features prototype
|
BUILD:
Safety
Performance
Quality
Beta version
.
|
BUILD:
Revenue
Profit
Feature release
|
|||
| MEASURE:
# people w/ problem
# people w/ solution # visits # sign-ups # logins |
MEASURE: # people clicked feature # people used feat. once # people use feature often # clicks on new features # clicks on the old features |
MEASURE:
# satisfied users
# paying users
# lives improved
|
MEASURE:
ROI per user
# profit users
|
|||
| LEARN:
Surveys
Interviews
Market Research
Non-Coded MVPs Feedback Analysis |
LEARN:
Problem-Solution Fit
A/B Tests
Coded MVPs
Usability Tests
|
LEARN:
Product-Market Fit
Kanban |
LEARN:
Virality models
|
| .................. | 
50% users
clicked to use
the feature
|
............ | 35% early-adopters are using the feature often |
......... |
40% customers
will be very disappointed
without the feature
|
...... |
From Enterprises to Startups, software projects mostly fail from skipping the validation phase. Teams normally jump from the ideation straight to development assuming that they already know what users want. And then, they stay for a long amount of time at the development phase, building new features continually before confronting them with real users.
"It is impossible for a man to learn what he thinks he already knows." - Epictetus
The idea of the User Driven Development methodology is to add the user interaction practices to the Agile process. In other words, to drive the team to test the most valuable features earlier, having a chance to don't spend time developing useless features and stoping enhancing the code as soon as the users agree that the existing development is already good enough.
No comments:
Post a Comment