Introduction to Business Analysis (Group 4)

Rabbit —small,  fast , and  brief -lived. Rabbit  tasks  are  generally  smaller  initiatives  with shorter lifetimes,  where   near  stakeholder participation is  possible . Rabbit  projects   typically   encompass  a lesser  number  of stakeholders. Rabbit  projects  do  not  spend an  excellent  deal of time writing the  necessities ,  but  use conversations with the stakeholders as a  manner  to  difficult  the  requirements  written on  tale   playing cards . Rabbit  tasks   nearly constantly  collocate the  business   know-how  stakeholders with the  enterprise  analysts and the  developers . Horse  tasks  are  possibly  the  maximum   not unusual   corporate   projects — they may be  the “ midway   house ”...

Quality Gateway Requirements are the foundation for all that is to follow in the product development cycle. Quality Gateway ensures that requirements are rigorous by testing each one for completeness, correctness, measurability, absence of ambiguity, and several other attributes, before allowing the requirement to be passed to the developers. Negative Stakeholders Negative stakeholders have opposite opinions which are against the procedure of project. Although they may not be the most cooperative individuals. Negative stakeholders can also be considered the people who threaten your product. For example – hackers, defrauders, and other malevolent people. These people do not provide cooperation in any task unless mistreating your product.

Truth 7: Requirements do not come about by chance. There needs to be orderly process for developing them. This means that requirements are not to be found just by chance or sitting next to the project layout but for each and every business project you need to follow a certain different process to gather business requirements. This process is different for different business projects because keeping your mindset limited would not help you in every project you are working on. Truth 8: You can be as iterative as you want, but you sell need to understand what the business needs. This refers to a common problem the arises in a company that processes are that go successful for one project are to most likely to be repeated or to be implemented for the upcoming projects. Even if the process is working just fine there will always be a process to make things better than just fine. For making things better you will always need to understand the requirements of the business project. -...

The NorthWest Company has expanded its business through the isles in Central America, which is a very huge challenge. Basically, there are cultural differences, several different languages, different currency, so different market, costumes and behaviours. In other words, there are several issues to be understood to have those barriers solved. The Business Analyst in that company is responsible to deep understand all the specific issues and requirements needed in each place in Central America where the company is being expanded. This is essential to understand the requirements to solve business issues. Otherwise, they will propose only pieces of a software that will frustrate the business needs. After reviewing all the specific requirements, the Business Analyst will be able to propose specific solutions such as, exchanging currency, which one is the best way to develop the supply chain system, the specific federal tax system for each country.

Truth 11 You, the business analyst, will change the way the user thinks about his problem, either now or later.  While solving a problem, it is seen as a duty of a business analyst to describe the problem to the user. When people understand the problem appropriately, they themselves will look into solutions to improve the case of the problem. Types of the requirements: Functional requirements : A functional requirement essentially specifies something the system should do. Non-functional requirements : A non-functional requirement specifies how the system should behave. Constraints:   Constraints are effectively global requirements, such as limited development resources or a decision by senior management that restricts the way you develop a system.   Aziz

Truth 9 There is no silver bullet. All our methods and tools will not compensate for poor thought and poor workmanship. Business processes are not very easy, and they need a person’s appropriate thinking and perception regarding the project to succeed. There is no straight path with prearranged processes which has all the solutions and will be helpful every time. Truth 10 Requirements, if they are to be implemented successfully, must be measurable and testable. When gathering requirements, anyone can make mistakes. To avoid the case when mistakes in requirements can affect the success of a project, requirements should be measurable and testable.

Fundamental Trusts (1 and 2) Trust 1 - Requirements Requirements are what a service ou product intend to do or to be. They are not some information or specs in a document. The business analyst must know what are the real needs of his/her client and define the real needs/requirements. Trust 2 - Benefits / Cost (product) The owner will not pay for the service until the product provides a benefit. This benefit can be a capability that was not possible before, a business process that is better or cheaper nowadays. To be optimally valued, the product must provide a benefit better than the cost.