According to experts, the success of the project largely depends on the personal qualities of the leaders and the “staffing” of the management of these qualities. Unfortunately, these qualities are not always taken into account in the formation of management. This creates risks and often leads to failure. This article discusses the typology of Adizes managers and the correspondence of these types to different roles in Scrum.
Adizes classification
A global management expert, Yitzhak Adizes, proposed a typology of managers based on four functions:
- Producing results (P) - production of results, in fact, for the sake of which the organization exists (short-term perspective);
- Administering (A) - administration required for efficiency (short term);
')
- Entrepreneuring (E) is an enterprise for change management (long-term perspective);
- Integrating (I) - the integration necessary to ensure the viability of the organization in the long term by combining its elements (long term).
According to the expert, there are no managers who have all these functions at the same time have been very strongly developed (PAEI). Usually, successful managers have well developed functions and some of them are excellent (PaEi, Paei, paEi, etc.). At the same time, for the successful existence of an organization, it is necessary that, in the aggregate, in management, all these functions should be presented at an excellent level. Moreover, it is necessary that the characteristics of each manager correspond to his activities. So, the head of the production department needs to be at least Paei, and the HR manager for corporate culture and atmosphere should be paeI.
It happens that the manager completely lacks 3 (P ---, –A–, –E–, --- I) or all 4 (----) functions. According to Adizes, this is very dangerous for the project and the enterprise. So, --- I usually means intrigue and decomposition of a collective, instead of integration in the case of paeI. Of course, such a team cannot work normally, a routine is formed, and usually from the most qualified personnel. On the other hand, P --- is a manager who does all the work himself, without trusting her team members. This leads to blockages and downtime in the short term and creates great risks for the future project.
Adizes classification and roles in Scrum
Scrum does not mean a manager in the classic sense. His roles are blurred between Product Owner (PO), Scrum Master (SM) and the team (DT from the Development Team). However, this does not mean that there is no management and should not be taken into account by PAEI in the assignment to the role. Therefore, we will try to expand on these functions.
The PO must set goals, work out the concept, vision, form requirements, deal with issues of budget and profitability. He needs to collect information from all stakeholders, process it, determine the feasibility and profitability, find the most profitable solution. Therefore, he needs to have an entrepreneurial perspective, i.e. be E. For example, paEi.
But he also needs to understand how everything is produced, what is the specificity inside, as well as to be focused on the short term - what will happen at the end of the sprint and what will please the stakeholders. Therefore, all the same, in the opinion of the author, it is best if PO is PaEi.
The task of SM is to ensure that Scrum processes are respected. Even their evolution must go in accordance with these processes. He also needs to provide the team with everything necessary, to solve or escalate the problems that arise. Therefore, he needs to be A. Moreover, he must maintain an atmosphere in the team, promote mutual understanding between team members, as well as with people external to the team, and promote the growth of team spirit and cohesion. This is all I. Thus, pAeI.
Usually a team is focused on a short-term sprint length or 2-3. Their goal is to produce everything they promised for the sprint. Those. Paei. This is basically the minimum requirement for a team. However, if they do not think about architecture, refactor, implement any best practices, then at some point the system will simply become impossible to support and expand. Therefore, the team needs a long-term vision, analysis and implementation of best practices, etc., which corresponds to E.
Also, the team is engaged in planning and control, compliance with any accepted norms, processes and practices (code style, coverage with code review, etc.), which is an administrative function - A. Thus, it would be good for the team to be PAEi. Fortunately, it is a team and there may be people in it that promote productivity, long-term vision and administration.
I would like to draw attention to the fact that Adizes recommends that in the management of a team / enterprise there should be two people with PaEi and pAeI and better if PaEi is “higher” pAeI. This just corresponds to the functions of the Product Owner and Scrum Master, only in Scrum PO is not the head of the SM and the team, but only performs its functions.
Example
The author is familiar with the case when the Product Owner was --- I, and the Scrum Master - PaEi. Those. they had strongly / poorly developed these functions as individuals, although the roles required a different set. This led to intrigues from the POs, conflicts, a decline in performance and the dismissal of team members.
Not wanting to work in such an environment and in the conditions of personnel shortages in the market, they quickly found new jobs. The project at that time had dubious prospects, due to the lack of a complete set of PAEI in management: there was no one to “produce”, “administer” and think about the future.
Conclusion
Understanding the fact that there are not so many qualified personnel on the market, one should still take into account management styles when forming teams. This has a significant impact on the success and achievement of goals.
Literature
- Perfect leader. Why they cannot become and what follows from this, Adizes Yitzchak Calderon, 2013.
- Scrum Guide, Ken Schwaber and Jeff Sutherland, 2013.
- Scrum Body of Knowledge, Scrum Institute, 2016.