Answer the question
In order to leave comments, you need to log in
Which member of the development team writes down the requirements for the MVP?
Guys, voice your opinion, please. We have a small team, we started to make our own web application. We are currently in the MVP development stage. The architect is for not wasting time on a detailed schedule of each step, but leaving a short comment during development, and the programmer lead is for describing all the requirements in detail. Well, they are in trouble on this basis, who should do it - 1, is it necessary now to spend time on such a detailed description -2. I want to know how others do it. And then there are more disputes than deeds, to be honest.
Answer the question
In order to leave comments, you need to log in
And who is responsible for marketing and promotion of the product? Who owns the product idea? It seems to me that these people should have a significant voice in the decision-making process in this process. After all, an MVP should be simple and do the bare minimum, which is the idea of the project. Select them, and I think it will be easier.
The truth, in my opinion, is in the middle.
If you have a team of several people - one of the people should take on the role of a formal project manager and draw up a functional description of what you are going to do (small, maximum 2-3 pages of text) and based on it - a work plan at least weekly.
This will allow all team members to synchronize understanding of where the project is heading.
leave a short comment during developmentI didn’t quite understand this - are you talking about documenting the already implemented functionality? It seems to me that at the MVP stage this is unnecessary, your task is to implement something of value as quickly and efficiently as possible and use it to test the hypotheses of demand, etc.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question