Among the developers, there are people who want to see that their product is being used. But what if the product is still in development? Or developed, but not the first pilot clients? In both cases, feedback is needed to understand which product features are in demand by the market and which are not. And if all this is complicated by the difficulty to present the results of work for non-techies? Well, the most difficult thing is if the product needs to be sold within the company so that it can be sold to customers?
How our team solved these issues under the cut.
A few words about the products of the team
We make backend solutions for game developers so that they can focus on the game and not on how to organize a store in the game or work with items in the player’s inventory.
Why do you need feedback?
Scrum. Scrum : , , , , .
?
Scrum — ( ) — . - , , , , , .
!
, , .
, , , . , — -. , , 15-20 , .
, — , . . , .
, — backend-. - API-, , . , , ?
— Postman (cUrl/Fiddler) . : , . , .
. , , , .
, , . — API, , .
.
, , . - , , .
, , . , -. -, .
, , . , . — - — backend , frontend , backend. — frontend .
, .
, . , . , - , . , , . — , , -.
, , , .
, , , , .
The main thing that we understood is that for the feedback to be really useful, you need to demonstrate the results as if the client uses this functionality.