BUSINESS ANALYST

image description

Project Key players!

Here are the key players before project moves to the development phase… hope, you find it useful. Project Owner: Accountable for the development of the Business Case, Cost Benefit Analysis, and documentation of the benefit realization of the project. And he is responsible to assure that the project is appropriately aligned with the organizational strategies, that the project is feasible,

BUSINESS ANALYST

image description

What is a Risk & how do you manage?

An uncertain situation that exists in a project is nothing more than a situation that impact on the project cannot be accurately predicted. There is always the probability that the risk will not materialize but if it does materialize then its impact may not be accurately predicted. Risk may be due to a number of reasons, including the inherent complexity of the project or the limited experience of the project team with similar projects.

As in most occupations and roles in the organization, there are a number of principles that apply to the successful completion of the job. Some of the principles are high-level and generic while others are specific to an area of concern. The following is a list of such principles that apply to the role of business analyst.

Are you looking to improve your career as a business analyst? And that’s the opportunity I’m going to give you right now. Keep reading this article, you’ll learn three techniques that help you get more respect, earn a higher income, and create a better, less stressful future. If you’re like many business analysts out there, that last one may seem nearly impossible, but once you learn these three techniques that apply to both [waterfall and agile] methods.....

As a daily duty, we work with business stakeholders very frequently to assess their business needs and provide solutions utilizing our projects and solutions. We identify requirements and design documentation with regular meetings and coordinate with application development with the overall goal of ensuring the delivery of our products and solutions. However, one of our primary daily tasks is Gathering requirements (Business or Functional and /or Technical) and translating them as per the business rules and/or needs. With respect to our goals, we facilitate JAD sessions and walkthroughs, so that we can extract information from SMEs, Architects, Developers and/or some time third party vendors too… Biweekly Tasks: Depending upon the project period and complexity, we should facilitate team meetings in order to evaluate status of the project; also taking Meeting Minutes and distribute them to Senior Management to report the status of the project...

Few days back, one of my friend attended an interview for “UAT Business analyst”… & here is what he explained to the interviewer about “Tell me about yourself” For several years I’ve been working as a Business Analyst, and most of my experiences is gathering, analyzing the requirements and performing UAT. I truly enjoy working with Business stakeholders & testers throughout the SDLC… In my current project, I’m not only responsible for UAT, I’m also accountable for RTM as well as TTM which helped to assist in creation of Test Plan.

I was part of full Test Life Cycle (TLC) to create or validating Test plan, Test scenarios, Test Cases & Test scripts for each phase/step… such as Unit Testing, Integration Testing, Regression Testing, Performance Testing, Smoke Testing and User Acceptance Testing (UAT). ..

As a Business Analyst we need to collect the information from various Business people, who could be Requirement Owners, SMEs, or Users, certain times we may need to elicitate as part of the Requirement gathering phase. You may get confused why it is called Elicitation when we can use the term “gathering the requirements” instead of “eliciting the requirements”. In simple terms Gathering can be done if requirements already exist and are ready for documentation or review and forwarding to developers. however real work starts when investigation...