Hello!
Below in the text, I propose to get acquainted with the approach that I use to determine the functionality that should be included in the MVP for products with a sufficient degree of certainty in the backlog. If he comes, I will sign in more detail. Please do not judge strictly, but I will be glad to constructive criticism.
For anyone who is willing to put up with the dampness of the idea, welcome to kat)
Introduction
The task of determining the MVP functionality appears at the planning stage of product development and requires an updated solution as the product develops, up to the end of the MVP development.
The very concept of MVP assumes the fastest possible delivery of the product to end users in order to get feedback from them, however, Product Owners often exceed the minimum functionality in an effort to make the product better, which entails delays, exceeding budgets, and in worst cases even product development in the wrong direction.
To mitigate the above-mentioned risks, it is proposed to use a specific approach based on mathematical principles to regulate the process of determining the MVP functionality.
Criteria
The criteria for the task of determining MVP functionality are the criteria taken from the WSJF methodology, as well as an additional decomposition of Job Duration into components:
Cost of delay
- User-Business Value: ? , ? , , ?
- Time Criticality: ? - ? ? , ?
- Risk Reduction: - ? ? ?
- Opportunity Enablement: ? / ?
Job Duration
- Job Duration – , Features . , Features
- Job Complexity- , , , . Features, Features.
- Job Cost — , - , - . , .
1 21. (1, 3, 5, 8, 13, 21). Story Points , Scrum-poker.
, , , . , 3 21 Story Points.
Jobs Duration , Cost Of Delay – - .
:
MVP .
, (. Multi-objective optimization) — . , . . . . , .
:
.
:
Cost Of Delay = User-Business Valuek11+ Time Criticalityk12+ Risk Reductionk13+ Opportunity Enablementk14
Jobs Duration = Job Durationk21+ Job Complexityk22+ Job Cost*k23
K11+K12+K13+K14=1
K21+K22+K23=1
(Mutual Criteria) = Cost of Delay/Jobs Duration.
:
Mutual Criteria.
MVP ABC – .
ABC- — , . . — 20 % 80 % . ABC- : 20% 80 % .
ABC- — ( Features) :
— , 20% — ; 80% —
— , 30% — ; 15% —
— , 50% — ; 5% —
MVP.
, ABC- — . .
- , . , ABC-. , 20% , 80% . , , MVP.
:
- – 20% , MVP.
- – Features .
- , (MC).
- 2 – 20% (A), 80% (B+C).
- First class (A) - defines MVP.
Important Note: You must also consider CORE functionality. Group “A” may coincide with CORE, but if not, the results of ABC analysis should be supplemented with Core functionality.
CORE - functionality - this is the basis for the functioning of the product, which consists of functionality without which the functioning of the product is impossible. (For example, authorization).
conclusions
The application of this methodology to determine the Features set for MVP provides a reasonable choice of a rational number of tasks required to be completed to achieve MVP as soon as possible.