What processes should be established in an IT startup?

Question

Project management

Hey!

Are there any "courses" in nature (courses/resources/blogs/books) that comprehensively cover all the problems that all start-up IT companies have to go through, and offer options for solving typical problems and avoiding a rake?

Rake examples:

1. Task management. The importance of high-quality task management is far from clear to every novice IT office from the first days. Therefore, at first, office workers set tasks verbally, then on stickers, then they suffer in Trello, after which they come to Jira. Only, having overcome such a painful path, the organization comes to the fact that she "always needed", but she did not know about it.
   
2. Task management methodology. Hooray, we've come to Jira! It covers our "animal needs" in full, but we do not have a task management methodology, for which we are "not ashamed" in front of the departments. While we were struggling with Trello, we grew - QA, DevOps, designers departments appeared. And now a new problem has appeared - these departments somehow need to get along in Jira, and even better - work in it synchronously, without interfering with each other. We come to the concept of business processes, we collect in Jira our first ugly processes that have the opposite effect. Someone burns out from this, gets offended and leaves, because in paragraph 2 we have not yet grown up to what is described in paragraph 7.
   
3. Information flow management. At first it seems: what difference does it make what messenger we use to communicate within the team? But the difference becomes obvious only when you first suffered with Skype for several months, then with Telegram (already much less) for several years, and only after that you reach Slack with its killer channel system and integration with a cloud of various services, and finally , exhale.
   
4. Code management. GitHub+PullRequests. (Or is it still GitLab + MR?..)
   
5. Documentation. A very big pain for start-up organizations. What, how, where to document? How not to lose knowledge? Confluence.
   
6. Resource management. CRM with own dopilov.
   
7. Human resource management. HR service monitoring the status of employees.
   

You can continue to fill the list with "pains" endlessly. But I think everyone got the gist.
Question: would it be possible for potential future organizations not to fill typical bumps, going through this thorny path and stepping +/- on the same rake as a lot of other organizations, focusing from the very first days on processes and their adjustment?

Answer 1

Walking on a rake is normal, solve existing problems, don’t invent problems that don’t exist yet, you can optimize processes after you feel real pain.

Answer 2

only one
CashFlow needs to be adjusted, the
rest will grow

Answer 3

The first three points are closed by Yougile.
Trello is for those who like to move cards, it is not suitable for serious work.

Answer 4

As for me, to start it is enough to create an organization on gitlab.com even with a free plan for storing sources, and start using the rest as problems arise. Well, or right away, if there is experience and investments in implementation seem to pay off in a reasonable time.
Maybe guthub.com is also a worthy alternative now. Or a full package of services from Atlassian. But you can quickly and easily transfer the gitlab to a self-hosted server if necessary, or immediately raise it.

Answer 5

would it be possible for potential future organizations not to fill typical bumps, going through this thorny path and stepping +/- on the same rake as a lot of other organizations, focusing from the very first days on processes and their adjustment?

And normal organizations do just that - they hire CTO, PM, HR and other EXPERIENCED managers from the first days, sparing no expense for this. And they already provide everything that you wrote.

Answer 6

1. From the fact that you will take some courses - starting with the Guru, who is one of those who “I don’t know how, but I can teach everyone” to a super-cool American university - you’ll probably pick up terms and the ability to apply them (terms) where needed and where not needed. True, at least you will know what they are and what they mean. But when in life you come across a dozen real situations that seem to be described in the book, but only in life everything is a little “wrong” - then we can assume that you have learned something.
2. Is it possible not to fill cones? Well, the courses will explain to you what is possible. That's just for some reason, 101% of real firms, these bumps still fill up to one degree or another (if they do not have time to collapse to - or from - the first bump).
3. The essence, of course, everyone not only caught, but also described and discussed thousands of ways to solve them both in courses, and in books, and on the Internet, and even on this forum. Well? Here's a surprise, a silver bullet that allows you to "not step on a rake and focus on processes and their adjustment" has not been cast.

Answer 7

A startup is first and foremost a business.
All of the above is the tenth question.
For some reason, novice "start-ups" think that a startup is just an IT project

Answer 8

In fact, there are many such courses - infogypsies want to eat. But these are not the questions that you should think about at the very beginning, I mean until series C.
The main question is how to get from the point where there are zero users to the point where there are 100 users. And then, how many of them are left and what time they cost money.