Me and agile development story--Agile role PO

a background for agile development in the previous three articles , 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 completed the development of the 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 . when Agile starts, the entire team is tasked with a related division. , 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 of the line and executes po role itself does not develop One aspect of dealing with her is the development team on our side , Another aspect is the business team of the line , She as a bridge for development and business

PO The main goal is to determine the direction and vision of the product, define the content, priority and delivery time of the product release, and be responsible for the product. Is the person who maintains the product requirements list (products backlog) . 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'sPOto take a look at the actual situation,at the beginning of the project ourPOIt's basically the dragon, see the head.,seldom have a chance to see his face.,because he's still in the other positions in the line.,always come and hurry and hurry,so it leads to many unavoidable problems in the early development..after that, the team arranged full-time personnel to act as projectPO,Entire project group -The individual is divided into two major groups,two xPOresponsible for the tasks and plans of our two big groups..

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

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

Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.

Me and agile development story--Agile role PO