ECBA flashcards
ECBA · Build recall with a focused review session.
30 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Business Analysis Planning and Monitoring
- The knowledge area that governs how business analysis work is organized: choosing approaches, planning stakeholder engagement, deciding governance, and planning how performance will be monitored and improved.
- Business Analysis Approach
- A documented decision on how analysis work will be performed on an initiative, covering deliverables, timing, methods, and level of formality, chosen to fit the change context and risk.
- Plan-Driven Approach
- An analysis style that emphasizes early, comprehensive documentation and formal approval gates, suited to stable, regulated, or contract-bound environments where rework is expensive.
- Change-Driven Approach
- An analysis style that favors short cycles, lightweight documentation, and frequent stakeholder feedback, suited to evolving needs where learning happens through delivery rather than upfront specification.
- Stakeholder Engagement Plan
- A plan describing which stakeholders matter for the work, what each needs, and how, when, and by whom they will be involved, including escalation routes when agreement stalls.
- Stakeholder Map
- A visual model placing stakeholders by influence, interest, attitude, or impact so the analyst can tailor communication and involvement strategies to each group.
- RACI Matrix
- A responsibility assignment grid naming who is Responsible for doing work, Accountable for the outcome, Consulted for input, and Informed of progress or decisions on each activity.
- Business Analysis Performance Assessment
- A review of how well analysis activities performed against the plan, identifying gaps, root causes, and corrective actions so later work benefits from the lessons.
- Requirements Governance
- The agreed rules for how requirements are identified, prioritized, approved, changed, and traced, including who holds decision authority when views conflict.
- Elicitation
- The planned drawing out of information from people and sources, using techniques such as interviews, workshops, observation, and document analysis, before that information is confirmed and organized.
- Elicitation Activity Plan
- A schedule of what information to gather, from which sources, by which techniques, in what sequence, and with what logistics, prepared before elicitation events begin.
- Collaboration
- Working jointly with stakeholders so information is shared, misunderstandings surface early, and decisions gain commitment rather than mere compliance.
- Facilitation
- Guiding a group session so participants reach a shared outcome: setting ground rules, managing airtime, resolving conflict, and recording decisions transparently.
- Workshop
- A structured group event convened to elicit, elaborate, prioritize, or resolve requirements, valued for speed and for building shared understanding across functions.
- Observation
- Watching people perform real work in their own environment to capture tacit knowledge, workarounds, and context that interviews or documents may not reveal.
- Confirmation
- Validating that elicited information is accurate and complete with the sources who provided it, closing the loop before the information is treated as agreed requirements.
- Requirements Life Cycle Management
- The knowledge area covering how requirements are traced, maintained, prioritized, assessed for change impact, and approved from creation through retirement.
- Requirements Traceability
- Recording and following links between requirements and their origins, related requirements, designs, and test cases, so impact of change and coverage of scope can be assessed.
- Change Control
- A defined process for logging, evaluating, deciding on, and communicating proposed changes to requirements or baselines, protecting agreed scope from unmanaged drift.
- Requirements Approval
- The formal or informal acceptance of requirements by those with authority, confirming that the stated need is understood, agreed, and fit to be used as a basis for further work.
- Prioritization
- Ranking requirements by value, risk, difficulty, or urgency so limited effort goes first to what matters most; approaches include ranking, grouping, and time-boxed allocation.
- Strategy Analysis
- The knowledge area that examines the current state, defines a desired future state, assesses risks and change options, and produces a recommended direction for the enterprise.
- Current State Analysis
- Examining how the enterprise works today - processes, capabilities, systems, culture, and pain points - to establish a baseline against which change will be judged.
- Future State Definition
- Describing the desired condition after change in terms of goals, capabilities, and value, giving the initiative a target to design and measure against.
- Gap Analysis
- Comparing current and future states to identify what capabilities, processes, or resources are missing, and therefore what the change must deliver.
- Solution Scope
- The boundary of what a proposed solution will and will not change, used to keep expectations, design, and delivery effort aligned with the intended value.
- Requirements Analysis and Design Definition
- The knowledge area that structures raw requirements, models and refines them, verifies quality, and identifies design options that satisfy the need.
- Requirements Classification
- Grouping requirements by type or level - such as business, stakeholder, solution, functional, or non-functional - so each is analyzed, documented, and verified appropriately.
- Requirements Quality Criteria
- Attributes used to judge a requirement, such as being clear, complete, consistent, feasible, testable, and unambiguous, applied during verification and review.
- Requirements Verification
- Checking that requirements are correctly written, internally consistent, and meet quality standards - distinct from validation, which asks whether they describe the right need.