Answer the question
In order to leave comments, you need to log in
How to manage teams within a single project?
Hello everyone
I was wondering how to manage a large number of teams, say, about 20 teams of the company involved in one project. For example, there is a project, and 20 teams of 4-5 developers, plus an architect over them.
If a project with a small number of teams, the lead or architect can distribute directives and control the quality of decisions, because there is not much code to go through, and it is possible to make a review.
If we have many teams with different expertise, then it is impossible to physically check and correct the changes (there will not be enough time within, say, a sprint). Therefore, it turns out that the responsibility for the review (or completely, or everything except the architecture) should be delegated to the team leads.
If you delegate responsibility to team leaders, it turns out that the overall level of quality is provided only by the level of teams, and the architect himself only sets the direction and works with high-level things. Then it turns out that the architect alone is not a warrior in the field, and if the teams are not of a high level, technical problems (maybe even architectural ones) will creep into the product.
In summary, the question is how to build a process so that changes made by many teams of one project meet the requirements of the architect and pass the correct check (architectural errors, or gross coding errors do not fall into the common code base)?
If you know literature, please advise
Answer the question
In order to leave comments, you need to log in
Therefore, it turns out that the responsibility for the review (or completely, or everything except the architecture) should be delegated to the team leads.
If we delegate responsibility to team leaders, it turns out that the overall level of quality is provided only by the level of teams,
the architect alone is not a warrior in the field, and if the teams are not of a high level, technical problems will creep into the product
Roman Yakimchuk Roman And why not throw Agile in the trash?
In fact, the customer is given the idea that he will be able to plan Tyap-Lyap, save on technical specifications and business analytics, and add or remove features along the way. In fact, it turns out that what you said, who is in the forest and who is for firewood.
See how modern scalable frameworks - Nexus, LESS, SAFe - offer to solve these problems. For a better understanding of any of them, you should first understand how Scrum works within one team, what are the features and benefits of self-managed teams, how to build them, and how to ensure quality at the same time. The road is long, there is no silver bullet.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question