This is a team where there is a PM who decides what to do, what tasks, etc. There are also technical specialists: analysts, designers, frontend and backend specialists, QA. The concept of guilds in the Quarks organizational structure by the CTO. It has separate DevOps, service teams, as well as frontend, backend, and QA leads. As a QA leader, I manage both my automotive team and horizontally the entire QA direction of our company. What it means? The PM in each cross-functional team solves tasks relate more to the product load, what functionality will be done, what will be its priority. And I am more responsible for how it should be done.
Who understands the specifics
Thus the QA engineer in the team has two leaders – the PM and the leader of the QA department. That is why it is calle a horizontal system or a guild system. Advantages of a horizontal organizational structure: each guild is manage by a leader of the Colombia Phone Number List specialists’ work; a cross-functional team focuses on its results and processes, it does not nee to coordinate its flow with other teams; The team’s PM is focuse on product tasks; system of “checks and balances”. No one manages everything alone.
Team PMs have different levels
There are several decision-making centers, and this minimizes risks; a more objective assessment of the performance of technical specialists; unification of AERO Leads approaches and technology stack. The main difficulties in the guild system It is important that the PM and the QA lead work in unison, understand each other, or at least do not interfere. Each team has its own pace, and this can hinder unification to some extent. It is necessary to find a compromise between all participants so that unification takes place without breaking processes for anyone. of technical skills.
