Agile approach is one of the most widely approach used in software development, where it is considered as one of the software project management approach. During development a software some risks may occur, which adversary affects on project and leads to the project failure. For instance, incomplete requirement/ backlog that are initially begin, where iteration/sprints that are constructed through, ambiguity in task stories, making team development confused, lack of stakeholder involvement during iterations, lack of trained team members in agile methodology, product owners that don't have ability to express their needs, poor analyst experience to extract and understand product owners needs, poor sharing information among team members, and other risks that affect the project negatively, all are leading to failure. Many of these risks are related to stakeholders and requirements, most of previous works tried to reduce the negative impact of selecting random stakeholders. At the same time, they did not investigate what about selecting stakeholders in a way that minimize the risks that may occur from ambiguity of requirements that were collected to them. The present work proposed a methodology to minimize and mitigate such risks by selecting proper stakeholders for requirement elicitation in order to have complete, understandable and consistent requirements. The proposed methodology supports the development team to understand the requirements clearly without ambiguity to regulate the labor and deliver it within the specified time and budget. Furthermore, it supports selecting stakeholders that they can follow up with the development team throughout the construction and implementation of the project period. The present work, reduces large proportion of risks that team development facing in project.