PBP flashcards
PBP · Build recall with a focused review session.
33 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Business Analysis
- The practice of enabling change in an enterprise by defining needs and recommending solutions that deliver value to stakeholders.
- Stakeholder
- Any individual or group with a relationship to the change, need, or solution; may be internal or external and can affect or be affected by the solution.
- Requirement
- A usable representation of a need; can be classified as business, stakeholder, solution, or transition requirement.
- Solution
- A set of changes to the current state that satisfy one or more needs in a context; can be a process, system, organizational structure, or product.
- Value Stream
- An end-to-end set of activities that create value for a customer; mapping it helps identify waste and improvement opportunities.
- Capability
- The ability of an enterprise to achieve a specific outcome; capabilities are stable and enabled by processes, people, and technology.
- BACCM
- The Business Analysis Core Concept Model with six concepts: Change, Need, Solution, Stakeholder, Value, and Context; each defined in relation to the others.
- BABOK Knowledge Areas
- Six areas: Business Analysis Planning and Monitoring, Elicitation and Collaboration, Requirements Life Cycle Management, Strategy Analysis, Requirements Analysis and Design Definition, and Solution Evaluation.
- Agile Extension Horizons
- Three horizons of business analysis: Horizon 1 Product Ownership, Horizon 2 Business Analysis, and Horizon 3 Business Architecture.
- Business Analysis Approach
- Defines the processes, deliverables, and techniques used to perform business analysis; can be predictive, adaptive, or hybrid.
- Strategy Analysis Tasks
- Tasks to analyze current state, define future state, assess risks, and define change strategy.
- Business Analysis Competency Model
- IIBA model defining underlying competencies such as analytical thinking, communication, interaction skills, and tool/technology knowledge.
- Stakeholder Analysis
- Identifying stakeholders, understanding their influence and interest, and determining engagement strategies; tools include power/interest grid and salience model.
- Elicitation
- The activity of drawing out information from stakeholders using techniques such as interviews, workshops, observation, surveys, document analysis, and prototyping.
- Requirements Traceability Matrix
- A matrix linking requirements to sources, design elements, test cases, and other artifacts to ensure coverage and manage changes.
- MoSCoW Prioritization
- A prioritization method categorizing requirements as Must have, Should have, Could have, and Won't have; often used in agile and time-boxed initiatives.
- Use Case
- A description of a sequence of interactions between a system and an actor to achieve a goal; includes a main success scenario and alternative flows.
- Business Process Model
- A visual representation, often using BPMN, of the flow of activities, events, and gateways in a process to identify inefficiencies and improvements.
- Decision Tree
- An analysis technique that models decisions, possible outcomes, and their probabilities to evaluate alternatives under uncertainty.
- Transition Requirement
- Describes the capabilities the solution must have to support the transition from current to future state; temporary in nature.
- Pilot Release
- A limited deployment of a solution to a subset of users to validate functionality and gather feedback before full rollout.
- Business Readiness Assessment
- Evaluates whether the organization is prepared for the change, including process, technology, and people readiness.
- Cutover Plan
- Defines the sequence of activities, timing, and responsibilities for moving from the old solution to the new solution.
- Rollback Plan
- Defines how to revert to the previous state if implementation fails or causes unacceptable issues.
- Training Needs Analysis
- Identifies the knowledge and skills required for stakeholders to adopt the solution and the gaps that must be addressed.
- Solution Evaluation Tasks
- Tasks to measure solution performance, analyze performance measures, assess solution limitations, and assess enterprise limitations.
- Key Performance Indicator
- A measurable value that demonstrates how effectively an organization is achieving key business objectives.
- Earned Value Management
- Integrates scope, schedule, and cost to assess project performance; key metrics include CV, SV, CPI, and SPI.
- Control Chart
- A statistical tool used to monitor process stability over time and distinguish common-cause from special-cause variation.
- Benefits Realization Plan
- Defines how and when the benefits of a solution will be measured and who is accountable for achieving them.
- IIBA Code of Conduct
- Requires business analysts to act with integrity, avoid conflicts of interest, protect confidential information, and comply with laws and regulations.
- Business Analysis Governance
- The processes, policies, and decision rights that guide and control the business analysis work and the solution.
- Requirements Change Control
- A process ensuring that changes are evaluated, approved, and implemented in a controlled manner to avoid scope creep.