He knows what the result should be, but is not a manager in the standard sense

[mstakh.i.mo.mi]

Feedback from customers at the end of the cycle. Feedback after each block allows the group to assess how well the task was completed. In addition, all information is used for further planning. Agile Development Methodology Team The construction of an Agile team is based on the principles of self-organization and relative equality of its members. It is interesting that even the product owner, that is, the one who seems to be the head of the project, is in reality only the personification of the requirements for the product.


The problem is that workers rarely manage to overcome the habit of strict hierarchy, so overseas chinese in australia often this member of the group is forced to control the work. However, the ideal feature of the application of the Agile methodology is the collective mutual responsibility of specialists. The system has the following roles: Product owner . Has no idea about the technical side of the work, but represents the product and its audience as a whole, sees the tasks for which it will be used.


Action Coordinator . Responsible for team processes, directs the potential of group members. Team of developers . Engaged in creating the technical component. Agile teams are formed based on different principles – it all depends on the specific project. In any case, this format of work ensures the interpenetration of knowledge: normally, a group member is not limited to his own narrow area, but strives for cross-disciplinarity. It is not worth thinking that the Agile project management methodology forces a programmer to become a salesperson, and turns a designer into a marketer.