How to organize the work of programmers in a startup if you are not a programmer?

Question

Project management

To understand the context of the question, I suggest that you familiarize yourself with the introductory data:
- there is a founder of a startup, he is also the bearer of the idea.
- knowledge of the code - 0 (maybe you can at least learn to read the code in a reasonable time?).
- there is a common understanding of the solution architecture - clients for iOS, Android; SQL database for data; data is stored in encrypted form on the server; data transmission over SSL. (I will not paint in detail, I do not think that this will somehow fundamentally affect the answers).
- implementation tools - Azure mobile services (I know about the existence of AWS and Google), Xamarin for cross-platform development in C # (because I think that this can speed up the development process, I'm not sure - scold me).
- understanding of project management terminology - scrum, agile, etc (perhaps the use of these tools will help control the execution process, but in practice I have not worked with them)
- I think in the direction of breaking down the task into smaller ones so that: a) the general concept remains secret, b ) parallel development will probably speed up the process.
Where to begin?
How to organize development without contacting studios, but working directly with freelancers?
And most importantly, how to organize control over the execution of work?
Thank you.

Answer 1

I had such a situation, jambs and plugs in projects were constantly. I decided simply: I learned programming. Now:
1. If a programmer breaks a high price - I land it
2. If a programmer says long terms - I speed it up
3. You can read the code only by learning to write code
4. I understand the architecture of systems and evaluate the proposed solutions competently
5. Your idea is nothing, everyone FSUs on it
Read my question half a year ago, I did not listen to all these people and I have no regrets . Is it possible to become an effective project manager without programming knowledge? And in general, listen to those who have money, and not those who do not))

Answer 2

In your case, it is better to freelance a project manager and leave him the technical stuff.

Answer 3

1) Your understanding of the overall architecture sucks (at least get familiar with the terms so that you don’t write such things)
2) Your understanding of implementation tools sucks (projects are made not by tools, but by developers. And developers sometimes know some tools and are completely unfamiliar with others. And at the same time they remain brilliant)
3) Your understanding of project management sucks (management activity is generally indicative in terms of the fact that without practice, theory is only negative)
4) Your desire to parallelize the process is as old as the world and in itself doesn't work (read Mythical man-month)
5) Your desire to keep everything a secret (even from the developers? :) ) sucks. Only Microsoft is more or less successful with it.
6) Ideas by themselves suck, worthless.
7) Your desire to learn programming for the sake of the project - does not work.
What to do if there is an irresistible desire to stir up a project based on a personal idea (dictated by the market or not? ... an extraordinary thought in our time, isn't it?):
1) Infect a technically competent person with your idea, whom you can trust percent, so, at 99. And entrust the technical side to him.
2) Find an investor who, by a lucky chance, will not notice that you do not know how to work, take money from him and hire a manager who knows what to do and who to pay how much.
PS Software development is such a broad topic that in over 40 years of serious commercial application, even the most basic parts of the process cannot be formalized and solved universally.
You can't tell what to do. We can say which path is most likely to be preferable in this particular case (task + context + command + resources).

Answer 4

Hire a manager

Answer 5

You can use crm to organize and schedule tasks. There you can put down your task to each programmer, watch their implementation, deadlines.