How to create a team and organize a modern C#/.NET development process?

Question

Agile

How does the work of the development team work today when creating an internal product (finance, own payment cards, API, communication with banks)? Interested in the minimum and / or average number of specialists with their positions (for example, several developers, tester, team leader, project manager), as well as how the work process and interaction between them should be organized + software stack (C# + Windows mainly), which needs to be used.
At the entrance there is: a team of four C# developers, one database developer (T-SQL), two leads (one is responsible for product support, the other for development, but both are C# developers), a couple of project managers, three technical specialists. support, one system administrator. The number of leads for such a team is probably high because 3 developers left the team for a separate project and 1 more will leave in 2 months. At the moment, it is planned to hire 1-2 new developers and 1 tester, at least. The development uses the agile / scrum methodology with sprints, but without daily stand-ups. Also in the team as a type there is no testing and CI / CD. SVN is used (not git), there is no development culture. There is also another outsourced development team.
At the end, I want: a full-fledged team that will support old projects and develop new ones according to modern standards. However, realizing that the team is stuck somewhere in the Stone Age, I want to at least start somewhere.
Any links, any experience, any opinion will do.

Answer 1

Why do you need 2 project managers if you have to ask this question here?

Answer 2

However, realizing that the team is stuck somewhere in the Stone Age, I want to at least start somewhere.

Well, start with the git - it will give you normal opportunities for both testing and CI.
You can say that git is a flexible thing, you need to have some requirements for the organization of the process in order to adjust it for yourself. This is true, so while you explain to people how git can be useful, you yourself will understand what you need.
The modern development process is dictated not by the language or even by the platform, but by the business requirements for flexibility, short releases and fast MVP, as well as the understanding that "if they can roll out 2 times a day, then we would need more often than once every 3 month".

Answer 3

It lacks a lot of structure.
You need to set up a project management system in which you can describe your projects. For example, Redmine . (because it has svn integration, commits will be displayed in the comments on issues)
This will help you structure your projects, there will be some physical representation of the project: a list of tasks / ideas / bugs.
It is very important to correctly use such systems, which will help you a lot in scrum.
Choose a project -> Create a version for a future release -> Throw tasks there (a correctly set estimate of labor costs plays a very important role, which will allow you not to overload programmers and evaluate the scope of work)