Recent Posts

Pages: [1] 2 3 ... 10
BA understand the reason for change request, understand the impact for change request, understand the effort to implement the change, ensure that change request follows approval process.
Business Analyst Concepts Discussion / Re: User Stories?
« Last post by 1182234812 on January 30, 2019, 02:16:59 pm »
A user story is a very high-level definition of a requirement, containing just enough information so that the developers can produce a reasonable estimate of the effort to implement it.
Business Analyst Concepts Discussion / Re: Business Analyst delivered documents.
« Last post by 1182234812 on January 30, 2019, 02:10:51 pm »
The documents should be delivered by BA in different stages of SDLC
Pre-project : Business case
requirements gathering: BRD
requirements analysis: FRS from business requirements, SSD from technical team. prepares SRS by combining FRS and SSD. prepares RTM using SRS.
design: BA or test manager prepare test cases, initiate END USer manuals, Updates RTM and prepares HDD, ADD
development: LDD, CDD
testing: test case
implementation: submit to client after updating all documents.

User stories in agile
Business Analyst Concepts Discussion / role of BA and product owner
« Last post by 1182234812 on January 30, 2019, 01:57:47 pm »
Role of product owner:
1. product owner is only one person who is responsible for managing a product.
2. Product Owners duty is to clarify and deliver other elements of a product Backlog Just In Time
3. Project Owners have to do is ensuring the final product is compatible with User Stories.
4. The PO will help the development team understand the business needs and expectations for what they want to get.
5.  A product owner owns the product backlog, creates user stories, and interfaces with stakeholders as well as the Scrum team
6. Each Agile team needs a product owner, or they risk delivering the wrong functionality.

Role of BA:
1. Gather requirements using elicitation techniques
2. documents the requirements using industry standards.
3. model the requirements using UML.
4. communicate the requirements to the technical team
5. tracks the requirements during development stage using RTM
6. Handle change request
7. Facilitates Change requests
BA role in agile scrum is Product owner

The Product Owner is the one and only person responsible for managing the Product Backlog and ensuring the value of the work the team performs.Product owner job is to act as the voice of the customer, prioritize the backlog, answer or get answers to the team’s questions and accept/reject the work that the team generates.

In an agile environment, there is no role of project manage, the Product Owner owns the product, the Scrum Master owns the process and the team works together toward fulfilling the tasks. The Scrum product owner is typically a project's key stakeholder. Part of the product owner responsibilities is to have a vision of what he or she wishes to build, and convey that vision to the scrum team

Scrum master cant be project manager because scrum master cannot manage risk by himself. project manager can take risk management without involving team.

project manager cannot be a product owner because product owner focuses on project vision where project manager manages resources.
Business Analyst Concepts Discussion / Re: What are the Non Functional Requirements
« Last post by 1182234812 on January 30, 2019, 12:48:33 pm »
Functional requirements: functional requirement describes what system should do
Non-functional Requirement: Non Functional requirement describes how the system works.

four examples of non functional requirement:
Usability, performance, scalability, capacity, availability, security, reliability,
Project manager build the execution of vision. PM'S are analyze the scope, resources and current conditions to plan deliverable s.
product owner build the vision. PO'S set the priorities to deliver best.

Product owner represent the client or business. PO is customer focused
project manager represent the project to deliver. Pm is company focused
Business Analyst Concepts Discussion / Re: Agile-Scrum Interview Questions
« Last post by 1182234812 on January 29, 2019, 06:15:31 pm »
Burn up and burn down charts in agile

Burn up charts: this chart show that how much work is done is a sprint
burn down charts: thus chart show the remaining work to be done
Brainstorming – The purpose of gathering your stakeholders for brainstorming is “to produce numerous new ideas, and to derive from them themes for further analysis.

Document analysis – Document analysis involves gathering and reviewing all existing documentation that is pertinent to your business objective or that may hold data related to a relevant solution.

Focus Group – Focus groups consist of a mix of pre-qualified stakeholders who gather to offer input on the business need at hand and its potential solutions.

Interface Analysis – An interface analysis carefully analyses and deconstructs the way that a user interacts with an application, or the way one application interacts with another.

Interviews – One-on-one interviews are among the most popular types of requirements elicitation, and for good reason: they give an analyst the opportunity to discuss in-depth a stakeholder’s thoughts and get his or her perspective on the business need and the feasibility of potential solutions.

Observation (job shadowing) – Observation is quite helpful when considering a project that will change or enhance current processes.

Prototyping (storyboarding, navigation flow, paper prototyping, screen flows) – Prototyping is especially valuable for stakeholders such as business owners and end users who may not understand all of the technical aspects of requirements, but will better relate to a visual representation of the end product.

Requirements workshops – A requirements workshop involves gathering a previously identified stakeholders in a structured setting for a defined amount of time in order to elicit, refine, and/or edit requirements.

– While they preclude the opportunity for in-person, ad hoc conversations, surveys are useful for quickly gathering data from a large group of participants.
Business Analyst Concepts Discussion / Re: Basics of Gap Analysis
« Last post by Siluvai Michael Raja on January 28, 2019, 11:24:12 pm »
Gap analysis is a way to compare current conditions and practices in order to identify gaps and areas in need of improvement with regards to compliance to the relevant standards. Formally it means to identify and correct gaps between desired levels and actual levels of performance used by organizations to analyze certain processes.
Pages: [1] 2 3 ... 10