PBA IQA flashcards
PBA IQA · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Stakeholder analysis
- A technique that identifies stakeholders and assesses their influence, impact, attitude, and authority to determine engagement and communication needs.
- Business analysis approach
- The selected method for performing BA work, ranging from predictive to adaptive, chosen based on risk, regulation, and rate of change.
- Governance
- The decision-making authority, escalation paths, and approval thresholds that control requirements and changes in a project or organization.
- BA plan
- A document describing the scope of BA work, activities, deliverables, stakeholders, communication, and performance measures.
- Communication plan
- A plan specifying who receives which information, in what format, and how often during business analysis work.
- Performance measurement
- Tracking BA work using metrics such as requirement defect rates, stakeholder satisfaction, and cycle time to assess effectiveness.
- Elicitation
- The discovery of information through prepared, conducted, confirmed, and communicated activities; it is broader than requirements gathering.
- Workshop facilitation
- Running a structured group session with a defined purpose, agenda, facilitator, scribe, and decision log to elicit information.
- Confirmation activities
- Reviews, walkthroughs, and sign-offs that verify elicited information is accurate and complete before it is used.
- Stakeholder collaboration
- Ongoing engagement with stakeholders through communication and involvement, not a single elicitation event.
- Elicitation technique selection
- Choosing a technique based on information type: tacit knowledge favors observation and interviews; group consensus favors workshops.
- Requirements traceability
- Linking requirements backward to business need and forward to design, test, and delivery to support impact analysis and verification.
- Change control
- The process of evaluating a change request for impact on scope, cost, schedule, risk, and other requirements before approval.
- Baselining
- Freezing an approved requirement set so that subsequent changes are tracked as versions against a known reference point.
- Requirements prioritization
- Ranking requirements by value, risk, cost, and dependency using schemes such as MoSCoW or weighted ranking.
- Requirements attributes
- Metadata about a requirement, including ID, source, owner, priority, status, complexity, and rationale.
- Current state analysis
- Examination of business need, organizational structure, capabilities, technology, and culture to understand the starting point for change.
- Future state definition
- A description of the desired outcomes and the capabilities required to achieve them, guiding solution design.
- Gap analysis
- Comparing current and future states to identify what must change in processes, systems, skills, or structure.
- Business need
- A problem or opportunity that justifies change and is validated before solution design begins.
- Change strategy
- The scope, approach, and transition path from current to future state, including associated risks.
- Solution scope
- The agreed boundary of what a solution will and will not address, confirmed with stakeholders.
- Requirements classification
- Categorizing requirements as business, stakeholder, solution (functional and non-functional), or transition requirements.
- Requirements verification
- Checking that requirements are unambiguous, complete, consistent, feasible, testable, and traceable.
- Requirements validation
- Confirming with stakeholders that requirements represent the real need rather than just a stated want.
- Design definition
- Translating requirements into solution components, interfaces, and allocation of requirements to those components.
- Non-functional requirements
- Quality attributes such as performance, security, usability, and availability that constrain how a solution performs its functions.
- Solution evaluation
- Measuring whether a delivered solution meets the business need and delivers expected value in its operational context.
- Performance measures
- Operational and outcome metrics defined before evaluation to compare actual results against the business case and success criteria.
- Solution limitations
- Constraints or shortcomings of a solution identified during evaluation and analyzed for root cause before recommending action.
- Analytical thinking
- Decomposing problems into parts, identifying patterns, and evaluating evidence before reaching conclusions.
- Ethical behavior
- Disclosing conflicts, protecting confidential information, and reporting accurately in business analysis work.