This is a typical agile development. Product Owner the.
This picture often causes a person to get into an argument : is it a domain expert, or an architect ? , to serve Product Owner?
actually arguing about this. basically only consider Agile development Product Owner definition " " products " " team member "
only consider " role " , domain experts, architects, decide who is in the company Product Owner, in the actual project, will often find the wrong (not suitable for) " people " , to serve as Product Owner . And to make the team in the operation of the project and version delivery of efficiency and quality, are caught in an unprecedented disaster.
For the "work" of the Product Owner, the domain experts and architects are the "right" roles, but the "right" role is not always the "right" person.
" The existing organizational role in the enterprise, directly on one-to-one correspondence to the agile development of product Owner, ScrumMaster, which is to ignore the product, ignoring the status of team members, a very wrong, very Stupid Organizational management model. such a pattern would enable the team to " right " the role ," wrong " the People, while falling into chaos, even collapsed to the point.
"The main team,the only task is to develop the product. not to follow the rules,dogma to do agile;Agile Development is just a tool. And to do the product is"people"is not"role". only to find"the"of the people, can make"the"of Products; Does this have a definite relationship with the character?? "
A herd of pigs and blind men, the company's existing organizational role, one-to-one correspondence to Product Owner