Scotiabank

 Setting the Scope We have to understand business process and aim of organization to make a scope. we need to find what our owner is doing and how our product will benefit them. There are different parts of business that we should understand like "the Work" that define precise scope of work and parts of organization that are included in work. In addition, there is scope for owner's work that involve work that owner want to change or improve. Stakeholders Stakeholders are those who are interest in and affected by the output or result of project. Therefore, a single project involve many stakeholders to complete a project. For example sponsor, customer, suppliers, consultants, manager, opponents etc. Some of important stakeholder discussed below: The Sponsor: A sponsor is a person who represents owner's interest to other stakeholder and provide budget for developing the resources of project. It means sponsor pays for development of product. a project can not go

According to chapter 2 of the Mastering the requirements process book, the first step of the Volere requirements process is the Project Blastoff.  It might last a few hours or several days it all depends on the size of the project and the amount of uncertainty. Key Purpose – The key purpose of the project blastoff is to build the foundation for the requirements discovery and ensure that all the needed components for a successful project are in place.   It identifies the purpose of the result the project is trying to achieve and the stakeholders. Main deliverables: 1)      Purpose of the project The blastoff group confirms the goals of the project. In order to determine where to start the requirements gathering, the BA must understand what the project is trying to achieve. 2)      Project Scope The scope must be set and understood by the project team. Identifies boundaries on what part of the business to study and who to interview for the requirements.  

  Some Fundamental Truths                                                                                              post by Paramjeet Kaur Toor Some Fundamental Truths are: 1. Requirements are not really about requirements Requirements are what you are going to build that can be software, hardware or any service so these are developed to be confirm about our specific output. Therefore, requirements activity is not just write them on paper but focus on problem and finding its solution is most important. 2. If we must build software, then it must be optimally valuable for its owner. It our primary job to meet the product/service' s qualities to owner's expectation who is paying for it. Therefore, people must know owner's needs deeply so that final output will be beneficial for owner. Optimally valuable means that owner must earn more profits from that product' s costs. Therefore, it become concern to make more and more profitable product