It often happens that a developer becomes the head of a development group and it turns out that although you are programming, in fact, you become a completely different specialist who needs a set of slightly different competencies. At the stage of becoming in a new position, previous experience is very important - that is, if a developer was previously a member of an agile team, then it is likely that he will use agile techniques in current development. What happens if the development manager has not previously participated in agile development and does not even know that such techniques exist or knows, but does not have time to learn, or they seem very fanciful or ineffective? This is the topic of the publication.
It was this way that I happened to go, where I learned a lot, got tremendous experience and made a number of interesting conclusions, which I want to share.
Introduction The main factor of development efficiency
So, back to the question - if you are not familiar with the methodologies, then what method of organizing the development seems to be the most logical and acceptable? Well, of course, divide the developed configuration into subsystems and assign each developer responsible for one of the subsystems. Is it logical? It is logical!
— , — , . , - . — ? - , , . — , — , , ; — , , , , . , . , , . : ( ) . .
? — , . , " " , .
.
( ) , — , "" . — , , ? , , . . , - , .
, — , . , , , . , , , , ; — ; — , , ? , . , , "", , , , , , , , .
. , , ...
.
.
, , , ? . , agile.
, - — , , , agile [1, 2, 3], . , , , agile, [4, 5]. , - , - . .
. , . — ( , ) ( ). : , ; — , , " " ( ), , .
:
- , , , ;
- , , ;
- , . .
, "" "", ( ).
( ) , . , , . , . — , . , , . ? , . , . - , , .
, "", , . , , .. , "", "" "". , . "", . ( , ) , . , , . , , . () , [3].
, , agile. - , , .
.
… , , , "" , .
… .
[8], , , , ? — , ? , , , , , , , , . , , . .
, . , , , , . , , , .. , .
, , . , " ", — " ", " " ..
- ( ),
- ( , ),
- ( )
- ( )
, . , .
. .
. agile
. — .
, , . , , , . — . . — , — .
. , , , , , . . , , , , — , . .
, , ( , agile). ( , "").
(, " ") ( ), , ,
agile, , , , . , . — , . , "" - " ", , . "", , . .
. agile
… , , . , - , " ". , " " " ". .
, , , , , , .
— KPI , , .
.
:
- , , . , , .
, , . - , , . , . . , . .
, ( ) . , , . . - , , , ; ( ), , .
- ( agile), .
, , , , , , . — ( ), , , . - Individual responsibility for the team's result provokes the creation of a hierarchy within, therefore, for the development of team work, either responsibility must be team responsibility or demand from the team leader is necessary for both the results of work and the results of team interaction.
I hope that you will learn something useful from my experience, and maybe even adopt it.
References from the article:
1. "Comprehending Agile" by Jennifer Green
2. “Scrum. A Revolutionary Project Management Method Jeff Sutherland
3. “Agile management. Leadership and Team Management »Jürgen Appelo
4. “Management of the new time. Simple Mechanisms Leading to Growth, Innovation, and Market Dominance Edwards Deming
5. "Effective Leader" Peter Drucker
6. "Styles of management - effective and ineffective" Yitzhak Adizes
7. "Five vices of the team" Patrick Lencioni
8. “Strategic Safari. Excursion through the wilds of strategic management "Henry Mintzberg