CCBA flashcards
CCBA · 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.
- Business analysis governance
- Defines how business analysis decisions are made, including change control, approval authority, prioritization, and escalation paths, and sets the principles by which business analysis work is conducted.
- Stakeholder power-interest grid
- Classifies stakeholders by their level of influence and interest so engagement effort and communication frequency can be targeted to those who affect or are affected by the change.
- Plan-driven business analysis
- An approach in which business analysis deliverables are defined in detail before work proceeds and changes are controlled formally, suited to low-uncertainty or regulated work.
- Change-driven business analysis
- An approach in which business analysis deliverables emerge incrementally through repeated cycles with frequent stakeholder feedback, suited to high uncertainty and evolving needs.
- BA performance improvement
- A task that identifies and acts on opportunities to improve the efficiency and effectiveness of business analysis work itself, based on defined measures and lessons learned.
- Business analysis information management
- Defines how business analysis information is structured, stored, accessed, traced, and reused, including the repository, attributes, and formats applied across the life cycle.
- Elicitation
- The activity of drawing out business analysis information from stakeholders and other sources using research, collaborative, experimental, and questioning techniques.
- Job shadowing
- An observation technique in which the analyst watches a stakeholder perform real work, capturing actual steps and exceptions that written documentation may not reflect.
- Focus group
- A facilitated discussion with a small, pre-qualified group of stakeholders used to gather qualitative attitudes, opinions, and ideas that individual interviews may not surface.
- Confirm elicitation results
- Reviewing gathered information against other sources and stakeholders to ensure it is accurate and complete, resolving discrepancies before it is used as a basis for requirements.
- Manage stakeholder collaboration
- Working with stakeholders to encourage shared understanding and joint ownership of business analysis work and to keep them engaged across the change life cycle.
- Traceability
- The ability to link a requirement to its origin backward and to other requirements, designs, and solution components forward, supporting impact analysis and verification.
- Derive relationship
- A traceability relationship indicating that one requirement was inferred or developed from another requirement, a higher-level requirement, or a stakeholder need.
- MoSCoW prioritization
- A prioritization scheme that classifies requirements as Must have, Should have, Could have, or Won't have for a given delivery timebox.
- Requirements baseline
- An approved and captured set of requirements that serves as the reference against which subsequent proposed changes are assessed and controlled.
- Requirements change impact analysis
- Assessment of the benefit, cost, effort, risk, dependencies, and downstream effects of a proposed requirement change before a decision to approve or reject it.
- Requirement attributes
- Metadata recorded for each requirement, such as identifier, priority, owner, source, status, stability, complexity, and verification method, used to manage it through its life cycle.
- Current state analysis
- Examination of the existing business need, enterprise structure, capabilities, processes, technology, policies, and stakeholders to establish a baseline for change.
- Gap analysis
- Comparison of the current and future states by capability or element to identify what must be added, removed, or changed to reach the target state.
- Business need
- A problem or opportunity faced by the enterprise that creates a reason to act and motivates a change initiative.
- Transition state
- An intermediate condition between the current and future states that is designed and managed so stakeholders can move to the target state.
- Change strategy
- The approach for moving from current to future state, covering solution scope, transition states, delivery approach, investment, and risk mitigation.
- Requirement verification
- Confirms a requirement is correct, complete, consistent, unambiguous, and conforms to agreed standards; it does not confirm the requirement delivers business value.
- Requirement validation
- Confirms that requirements and designs deliver value, meet stakeholder needs, and align with the business objectives of the enterprise.
- Requirements architecture
- The structure, views, and relationships that organize requirements into a coherent whole for a solution, ensuring the set is complete and consistent.
- Design option
- A candidate way of satisfying one or more requirements, assessed for value, cost, feasibility, and risk before a solution is recommended to stakeholders.
- Decision model
- A model showing how decisions are made within a business area, including decision points, the rules applied, and the inputs that determine outcomes.
- Solution performance measures
- Indicators defined from business objectives and evaluation criteria that show how well a solution delivers expected value once it is deployed.
- Solution limitation
- A constraint, defect, or capability gap in the solution itself that prevents it from delivering the expected value to the enterprise.
- Enterprise limitation
- A condition in the wider organization, such as policy, culture, structure, or process, outside the solution that limits the value the solution can deliver.
- Acceptance criteria
- Conditions that a solution or solution component must meet to be accepted by a stakeholder, expressed as testable statements used to verify the solution.
- Evaluation criteria
- Criteria such as cost, benefit, risk, and feasibility used to compare alternative solutions or designs and to support a recommendation.