B-a-Analyst

Success A seven letter word which the world has been chasing since they learned its meaning. We receive so much of messages defining its various meanings various full forms and multiple videos on YouTube and other information sites just to help you learn a very simple rule of it “Never lose confidence in yourself”. But to achieve that seven letter word or to be a dream maker an entrepreneur or to be on front page of a book / magazine or a newspaper is what everyone among us want to be somewhere deep inside us. We want to be famous for what we are and how we are but do you know hardly 8% of people achieve success while rest 92% are the reason they been there. So it’s simple those 8% people choose to take risk, help you manage what they seek from life, teach you skills to build their dreams. But to achieve Success you need to run by certain set of rules. There are various rules and ways of achieving it but I would go by the most needed and common of every rule I have heard from spee

Knowledge Area - Business Analysis Knowledge areas are the major components of business analysis as this are the key skills every BA should have. Also this are the aspects on which a IIBA certification rely on to identify your BA skills and responsibilities that were executed during the period. In other words Knowledge Areas define areas of specific expertise.There are overall of 6 knowledge areas in business analysis. Keys knowledge areas are; BA Planning & Monitoring Elicitation Requirement Life Cycle Management Strategy Analysis Requirement Analysis Solution Evaluation Summarized information for knowledge areas is as below, &nbsp BA Planning & Monitoring &nbsp Elicitation This is the phase where requirements are collected by various techniques by conducting meetings with external stakeholders. In requirements engineering, requirements elicitation is the practice of collecting the requirements of a system from users, customers and other stakeholde

There are various types of documentation created by a Business Analyst. Being a analyst documentation is a primary task they should be good and skilled at. Documentation would vary from phase/stage of the product/project they are on. i.e. If they are drafing the requirement and need to have external staekholders approval to freeze it than it is called as BRD/BRS. In other words, the type and specifications a business analyst is expected to create in an organization depends upon many parameters like organization’s processes and policies, need and expectations of the business, and the stakeholder requirements. Below are the common documents a business analyst is expected to create and they are extensively used throughout the course of a project. Each of these documents has a specific template and it’s a part of the overall project documentation. The documents are: Project vision Document Requirement Management Plan User stories Business Requirement Document Requirement tr

Business Analysis Techniques varies from situation to situation and there are three different approach/methods to it which we need to understand prior to techniques First we need to understand what BA technique means, Business - Understanding the need of the product, Analysis - Design a solution to the problem identified while developing a product, Technique - Approach or method to be utilized for achieving the goal of product. PESTAL - Political, Economical, Social, Technological, Legaal, Environmental MOST - Mission, Objectives, Strategy, Tactics. SWOT Business Analysis techniques varies from category to category. In this article we would be explaining the brief understanding of BA techniques in reference to BABOK guide. BA techniques can be categorized into various categories such as, Elicitation Planning RAD - Rapid Application Development Requirement LCM (lower of cost or market) Solution Evaluation Strategy Elicitation: In requirements engineering, requir

Agile Method This article is a introduction to Agile software development methodologies and it's application. This is not only suitable for software developers but also for Team Leaders, Project Managers, Product Managers, Development Managers, Testers, QA Managers, QA Engineers, Technical Writers, UX Designers, anyone involved in the delivering software.It doesn't describe any code or technology it's an method or an software engineering model which helps to develop a tool to it's best requirements or goals. Agile Method is a combination of various sprint cycles initially of 1 to 4 weeks per sprint cycle. Deployment is alligned with the changing business need after the completion of every sprint cycle. Agile adapts of frequent feedback by delivering workable product after every iteration/sprint cycle end. In other words Agile Method is a series of short iteration/sprint cycles. Agile Model is an incremental version of multiple waterfall model cycle so,br the cha

A Good BA ? We often face a question at interview about, what is a Business Analyst ? What are the Roles and responsibilities of BA ? What should a good BA possess? So here is the answer to it with refernce to an IT Business Analyst or Tecchnical Business Analyst. Q. What is a Business Analyst? A. &nbsp Business Analyst is an individual who acts as a spock between the internal and external entities during the product design and deployment cycle. A business analyst (BA) is someone who analyzes an organization or business domain (real or hypothetical) and documents its business or processes or systems, assessing the business model or its integration with technology. Q. What are the roles and responsibilities of a Business Analyst? A. &nbsp Roles and responsibilities of a business analyst can differ from type of IT industry one works in below is a generic skills required, &nbsp Communication - As being a spock one needs to be excellent in communication skills.

BRS vs SRS: Know the Difference The difference between a Requirement and a Specification &nbsp &nbsp Requirement &nbsp &nbsp &nbsp &nbsp Specification &nbsp &nbsp &nbsp They outline “what” the software must do &nbsp &nbsp They outline “how” the software will be created &nbsp &nbsp They outline the software from the end-user, &nbsp business and stakeholder perspective. &nbsp They outline the software from the technical &nbsp team perspective. There are a plethora of terms and terminology for various documents Specification Documents are of different types - SRS - System Requirement Specifications FRS - Functional Requirement Specifications BRS - Business Requirement Specification CRS- Compatibility Requirements Specifications PRS - Performance Requirements Specifications RRS- Reliability Requirements Specifications CRS-Configurations Requirements Specification Requirement documents are of differ

Change Control Process Business Analysts often function as agents of change, canvassing for improvements in the business or pointing out when a change should be nipped in the bud, for example, when the costs of implementing a requested feature outweighs the benefits. Changes often mark the beginning of projects, with some change requests coming in during the project and even after the project has been implemented. Not all changes are created equally, however. While some change initiatives are implemented with minimal resistance, some are faced with stiff resistance, conflicting interests and fears that need to be managed to ensure that the desired change sees the light of day. Managing change requests is particularly important in ensuring that the business does not spend its limited resources on changes that offer no real value at the expense of those that can deliver real value and lasting benefits. What is Change Control? Change Control is the process that a company uses to doc

Requirement Life Cycle: Validation, Documentation & Management Requirement lifecycle involves a number of phases and at times it can be a complicated process. The nature of the process depends on the methodology you choose for your software development like Agile, Waterfall, Incremental, etc. Each phase may involve a lot of paperwork and approval procedure. It also deals with the project documents like a project proposal, project management plan, project scope, and the business case. Let see some of the common requirement lifecycle required to know for a Business Analyst. Requirement Definition It is one of the primary phases of the requirement gathering process commonly known as Requirement extraction. Once the requirement is gathered, it can be organized in folders logically as per product release or sprint. These requirements are analyzed further to prepare facts and figures for a business analyst to track possible result based on analysis. This procedure is referred as

Stakeholder Analysis & Mapping with Template Example Stakeholder Analysis and Mapping is done to map the interest of your stakeholders. It is a process of systematically analyzing and gathering qualitative information to determine whose interest should be taken into account. Stakeholder Analysis and Mapping is important because it helps project leaders and managers to access a stakeholder's interest, positions, alliances and knowledge related to the project. When Stakeholder Analysis need to be done? Stakeholder analysis should always be done at the beginning of a project. Such analysis is helpful in the drafting of a log frame. Log frame is nothing but a general approach to project planning, monitoring, and evaluation in the form of a 'logframe matrix'. Whenever log frames are reconsidered during the life cycle of a project, a stakeholder analysis will be useful. Which means whenever mid-term reviews or annual monitoring is handled, stakeholder analysis should be