27 Terms Every BA Must Know!

27 Terms Every BA Must Know!


1.     Business goal — A state predetermined target an organization must meet to achieve its intended vision

2.     Stakeholder/User — Anyone who is part of a project/who may be affected as a result of project execution or a beneficiary who interacts with a solution

3.     Business case — Justification/Reason for initiating a project or program

4.     Use case — Use Case is like a sequence of events a system should perform

5.     User story — User Stories are written from an end-user standpoint

6.     Requirement — A requirement (IT context) is a functionality that a user needs

7.     Verified requirement — A requirement that is unambiguous, complete, correct, and testable

8.     Validation — Process of checking whether the defined requirements really meet customer needs and business needs.

9.     Validated Requirement — A requirement that meets user needs & delivered business objectives

10.  Elicitation — Process steps to get info/requirements from stakeholders/users

11.  Scope — Set of specific project goals, deliverables, tasks, and requirements that will be a part of the project as agreed by all the stakeholders

12.  Change Request — Request for an alteration to an already developed product functionality based on previously agreed upon the requirement

13.  Requirements traceability — The requirement Traceability matrix is used to map a journey of a requirement till its implementation

14.  Requirements management — Process of analyzing, documenting, tracing, prioritizing, validating & controlling change, and communicating to stakeholders/users

15.  Process analysis — Technique used to assess the effectiveness of a process to come up with a possible improvement

16.  Prioritization — Organize requirements so that the most important thing is done or dealt with first

17.  Functional requirements — Description of Requirements that a solution should offer as expected by its users

18.  Non-functional requirement — Constraints/Requirements imposed on the system to enhance the solution’s functional requirements

19.  Estimation — Technique used to arrive at an effort required complete a task or a project.

20.  Current Vs. Future State—Present set of circumstances | Visualization of the desired future state

21.  Assumption — A belief based on which, a requirement or solution is created/designed

22.  Change Management — A systematic approach to deal with transition/transformation

23.  Business Constraint — A business situation/event that prevents the full delivery of a project

24.  Variance — Expected outcome – Actual outcome

25. Model/Wireframe — Visual representation of a topic, process, or requirement

26.  Workshop — Well-structured meeting, guided by a facilitator, to perform elicitation, define and refine requirements

27.  Active listening — Act of listening and interpreting what the other person is saying – which facilitates the mutual understanding

BONUS

BI (business intelligence)
Method of compiling, analyzing, and interpreting business data to make better-informed decisions. BI data is collected from multiple sources — including industry reports, customer feedback, actual usage data of the company’s products, and competitive research.

Agile
An iterative product-development methodology in which teams work in brief, incremental “SPRINTS” and produces working software frequently . This adds rapid feedback and the ability to switch focus and priority for teams to execute.

Sprint
In agile methodology, the sprint is the time period (e.g., 14 days) in which an agreed-upon set of development tasks takes place and is made ready for review. The BA and product development teams typically begin a sprint with a kickoff planning meeting, and in this meeting, the group agrees to the specific tasks needed to be completed in the sprint.