Agile methods have been demonstrated to enhance customer value, improve organizational morale, and provide step improvement in product development and quality info. When the added complexity of product development is thrown into the mix, in addition to the technical aspects, the organization and social aspects of software development and sustainment also become more pronounced.
This talk is about how a Product Owner ‘must know’ and to understand about product definition goals, either it is a product development firm or a consulting firm, both place, we are doing Software product Development and a Product Owner must know his/her engagements, understand team and business, go beyond PO and contribute as Business Servant Leader to get best out of the concepts and envision. A PO is a misunderstood role and folks think that h/she is the person to write stories and apporve stopries. However, PO, being techno-functional guy, must understand with his/her work experience, and groom themselves for defining and identifying requirement items at granular level, understand technicalities at logic level etc. that will assist a PO to work for well defined and projected Acceptance criterion, understand agilie jargons etc. How a PO contribute with efficacy with Business and Team.