A Goal-Oriented Proposal to Support Product Owner Activities in Scrum Projects
Scrum, Product Owner, GORE, Planning
The Scrum has emerged as an alternative to traditional software development methods. In this method, the Product Owner takes a central role within the process, being responsible for communicating between the customer and the development team. To do this, he executes the management of the Product Backlog, which is the artifact that maintains a list of items to be developed by the team, corresponding to customer needs. In this sense, the literature has explored the challenges of the Product Owner, mainly in the planning and prioritization activities of the Product Backlog items. With regard to these activities, decision making is seen as the most important task of the Product Owner. Due to the unstable presence of resources lack of information about the business, the Product Owner may make wrong decisions or, because of lack of business ownership, omits this responsibility. In Goal Oriented Requirements Engineering, the requirements are described from the stakeholder organizational goals. Although in Scrum projects the requirements are internalized in the development process through items stored in the Product Backlog, the same is not true of the customer goals, which are not evidenced in the process. Given this, the present work proposes a goal-oriented requirements gathering methodology for Scrum projects, aiming to evidence the customer's goals within the development process, in order to maximize the results of the Product Owner's actions in order to fulfill the project success.