Me and agile development story--Agile role PO

In the previous three articles on the agile development of a background, is based on the author's personal experience as the main line to gradually understand the agile development from a personal point of view.

Through the pair programming to complete the development framework of the building, in the framework of the fact that our formal agile process has not yet begun, the real start is that everyone can act. When agile starts, the whole team will be in the relevant division of labor to complete the task, so different people have different roles, The next step is to understand the roles in agile development.

The first character to be said is PO.

The PO in Agile development is productowner, which literally means a product or business owner, who is familiar with all the business-related logic, processes, settings, and other aspects of the product, typically by a product manager, or by a developer who is familiar with the business.

In our team PO is a dedicated business person who serves and executes the PO role and does not develop itself. One aspect of dealing with her is the development team on our side, and the other is the line business team, which serves as a bridge for development and business.

Po mainly determines the direction and vision of the product, defines the content, priority and delivery time of the product release, and is responsible for the product. Is the person who maintains the product requirements list. Detailed responsibilities for seven points:

1, determine the function of the product;

2. Decide the date and content of the release;

3, responsible for the product ROI;

4, according to the market value to determine the function priority;

5. In each sprint, adjust functions and priorities as needed (before each sprint starts);

6, accept or reject the development team's work results;

7. Participate in Scrumplanning Meetings (Sprint planning Meeting), Sprint Review meetings (Sprint review) and Sprintretrospective meet (Sprint review)

Combined with our team's PO to say the actual situation, in the early stage of the project our PO is basically the Dragon saw the head, there is little chance to see his face, because he himself also as the other positions in the line, always come also hurried to also hurriedly, So it leads to a lot of unavoidable problems in the early development. After that, the team arranged the full-time personnel to serve as the project team PO, the whole project group of 20 people into two groups, two PO responsible for our two large groups of tasks and plans.

Then through the team's running-in, PO is also more and more professional, began to prototype design, mining business, more harmonious with the developers to communicate and communicate.

The success and failure of an iteration is entirely up to the PO (in the relatively ideal case), the summary is: Tell the product team what to do, what the sequencing of functions, how to deal with changes in demand.