BA:Innovate, Ideate & Create

Shagun Sareen To understand a product or service, the BA must understand the stakeholders and the business requirements. FUNCTIONAL REQUIREMENTS - These involve certain actions that the product should take to ensure its usefulness. These arise from the work the clients perform. For instance, calculating, publishing and inspecting. NON-FUNCTIONAL REQUIREMENTS - These are the properties or qualities that a product must possess. They are most likely to enhance the product and they are determined after the product's functionality. They also define the product's usability and stability. For instance, capacity, reliability and availability. Formality Guide for recording requirements- Rabbit- little, quick, and fleeting-   Rabbit ventures are regularly littler undertakings with shorter lifetimes, where close partner interest is conceivable. Rabbit extends more often than exclude a lesser number of partners. Horse- quick, solid, and reliable-   Horse ventures require ...

Truth 5        -The requirements do not have to be written, but they have to become known to the builders.       It is often observed that requirements and the goals given by the stakeholders are properly observed and noted by the business analysts and they believe that they should aim on achieving it by creating some more requirements and many stakeholders are never satisfied with whatever the result is but the thing is writing down the goals and completing the assignment gives us motivation despite this behaviour when we focus on requirements sometimes it is more effective when communicated verbally. except all these things, requirements are not meant to place extra burden on team there should be nothing written unless it is a clear need for it. Truth 6        - Your customer won’t always give you the right answer. Sometimes it is impossible for the customer to know what is right, and sometimes he just doesn’t know ...

Truth 9 (There is no silver bullet. All our methods and tools will not compensate for poor thought and poor workmanship) This truth says that the business analyst is supposed to think, analyze and make assumption regarding any work he is asked to do. Basically, he is supposed to work in orderly process, but this doesn’t mean that he will not think about the work. Smart people take advantages of processes more than the people who don’t think. In requirement processes, most of the time the Business Analyst is required to analyze the various requirements and think about the output which they would give in future. Truth 10 (Requirements, if they are to be implemented successfully, must be measurable and testable.) This truth says that we should be precise about the requirements. We humans are not always very accurate regarding the fact of requirements. We should be measuring the requirements using numbers instead of words to ensure necessary level of precession and make these re...

Truth 7 - Requirements do not come about by chance. There needs to be some kind of orderly process for developing them. Any vital undertaking needs a systematic procedure. Irregular utilizations of steel and cement don't deliver structures; there is a characterized procedure for planning and raising such structures. These procedures are not lockstep techniques where one thoughtlessly adheres to each guidance beyond a shadow of a doubt, in the recommended succession, and without variety. In particular, the general population who are dynamic in the process must have the capacity to perceive any reason why distinctive undertakings inside the procedure are critical, and which assignments convey the most centrality for their task. Truth 8- You can be as iterative as you want, but you still need to understand what the business needs. Since the past version of this book was distributed, iterative improvement techniques have turned out to be significantly more mainstream. This is su...

v   Truth 3               It is not about what do you want to build but it is all about what your customers are looking for.      When a developer understand that what will the user get from this product and in what manner then a successful product is developed. To understand these, one must understand the work of the business owner and then determine how that work should be carried out in the future.   Business Analyst then shows which product will improve the work to the business owner and then requirements are made which describes the functionality of the product (what will it do? how well it will do?). These requirements are a crucial part of the success of the product. Moreover, requirements are must for any business and even it does not depend on programing language and programming life cycle.   v   Truth 4 It is not about which software you build it is all about that software should solv...

Truth 1  -  Under this, the requirements are not only just restricted to requirements. If a problem is faced in a business, the main focus is laid on understanding that problem and then, finding out every possible solution to solve it. Truth 2 - Under this, the benefit that is achieved for building a software must be in proportion to the cost. It must be made sure that it holds optimal value to its owners.

DEVELOPERS Developer is the key individual behind all product applications. By and large, designers are knowledgeable in no less than one programming dialect and capable in the specialty of organizing and creating programming code for programming or a program. Contingent upon employment job and sort of programming built up, an developer might be named a product designer, application engineer, portable engineer, Web designer, and so on. DEVELOPER IN RBC RBC is first Canadian bank to open an API developer portal. Royal Bank is opening select bits of its information to outside programming engineers in an offer to encourage development and make new devices for shoppers. The RBC developer portal will allow eligible, external software developers, industry innovators and clients to access select RBC APIs. STANDARDS GROUP The Standards Group is responsible for making sure that the corporate standards are maintained as the project consists of many standards. ...

Requirements Life Cycle Management It can be referred to the process of documenting, analyzing, prioritizing and agreeing on requirements and then controlling change and communicating to relevant stakeholders. Trace Requirements It defines that the requirement is fulfilled both functionally and technically. Keep requirements aligned Setting up the goals of an organization and collecting various resources to achieve these goals. Maintain Requirements It refers to the activities required to conserve the original state of objective while implementing new ideas. Maintain accuracy and consistency It means that to achieve goals there must be accuracy and consistency of data. There should be proper and accurate data before starting a new plan or set new goal. Prioritize Requirements It can be defined as the ranking of requirements on basis of their importance. Functionality and accuracy. Rank for importance After the requirements are prioritized...