Free ECBA Exam Flashcards

The act of transformation in response to a need (BABOK v3). Change never occurs in isolation -- it is always undertaken to address a specific Need and takes place within, and is constrained by, a Context.

A problem or opportunity to be addressed (BABOK v3). Need is neutral -- it does not presuppose any particular Solution; jumping to a solution before the need is understood is a common business analysis failure.

A specific way of satisfying one or more needs in a context (BABOK v3). A solution that ignores its Context will fail to deliver the Value stakeholders expect.

A group or individual with a relationship to the change, the need, or the solution (BABOK v3). Stakeholders determine what has Value, and that determination is always relative to a particular Context.

The worth, importance, or usefulness of something to a stakeholder within a context (BABOK v3). Value is never absolute -- it is judged by a specific stakeholder from within specific circumstances.

The circumstances that influence, are influenced by, and provide understanding of the change (BABOK v3). A shift in the understanding of any one BACCM concept requires the BA to reevaluate the other five.

"The practice of enabling change in an enterprise by defining needs and recommending solutions that deliver value to stakeholders." A BA enables change -- sponsors and delivery teams own and execute it, and the work is anchored to value, not just documentation.

Agile, Business Intelligence, Information Technology, Business Architecture, and Business Process Management. Each is a lens on the same core BA work (elicitation, analysis, solution evaluation) -- not a separate methodology.

Per the Business Analysis Standard, an empowering mindset is built around: achieving organizational outcomes, discovering value, adopting principles, deciding on approach, developing foundational competencies, and using foundational techniques. It is built through deliberate practice, not innate talent.

See the Whole = analyze needs in the big-picture context and ask why a change is necessary before acting on a narrow request. Avoid Waste = identify which activities add value and remove those that don't. Two of the Business Analysis Standard's seven core principles.

Adaptability, Facilitation, Leadership and Influencing, Problem Solving, and Systems Thinking -- identified by the Business Analysis Standard as essential across all BA work. The BABOK Guide expands these into 29 underlying competencies (Chapter 9).

Predictive (plan-driven/waterfall): requirements defined in detail up front, formally baselined, changed only through a controlled change process -- suits stable, regulated needs. Adaptive (Agile/Scrum/Kanban): requirements captured at a high level and progressively elaborated in iterations -- suits evolving, uncertain needs.

BA work is performed under many job titles (business systems analyst, business architect, product owner, data analyst), not only "Business Analyst." A BA may report through a centralized center of excellence, a decentralized/embedded structure, or a matrixed structure; influence comes from facilitation skill and analytical credibility, not positional authority.

A requirement is a usable representation of a need -- it describes what is required, without prescribing how it will be delivered. A design is a usable representation of a solution -- it describes how the need will be met once options are evaluated and a direction is chosen.

Goals, objectives, and outcomes explaining why a change is being initiated -- the broadest, least detailed category in the requirements classification schema. Example: "Reduce customer onboarding time by 30% within one year."

The needs of a specific stakeholder or group that must be met to achieve the business requirements. They bridge business requirements and solution requirements, answering "what does this stakeholder need?"

The capabilities and behaviors a solution must have -- answers "what must the solution do?" Example: "The system shall auto-populate the application form from the existing customer record."

The quality-of-service conditions a solution must satisfy: performance, security, usability, availability, and capacity -- answers "how well must the solution do it?" Example: "The form shall auto-populate within 2 seconds of customer lookup."

Capabilities needed only to move from the current state to the future state, such as data conversion or parallel-run procedures. Unlike the other three categories, transition requirements are temporary and are retired once the transition is complete.

Three categories: organizational (structure, culture, processes, policies), environmental (regulatory requirements, market conditions, competitor actions, technology trends), and stakeholder (readiness for change, resistance or support, prior change experience).

Identifies which requirements, designs, processes, systems, and stakeholders are affected by a proposed or actual change, using requirements traceability. Each change is evaluated by weighing benefit against cost, urgency, and risk before a disposition of approve, reject, or defer.

BABOK v3: atomic, complete, consistent, concise, feasible, unambiguous, testable, prioritized, and understandable.

A requirement that expresses a single, self-contained need rather than bundling multiple needs into one statement -- one of BABOK's nine characteristics of a good requirement.

BABOK v3: the process of drawing out, exploring, and identifying information relevant to a change from stakeholders or other sources. Three activities: Prepare for Elicitation, Conduct Elicitation Activity, and Confirm Elicitation Results.

Interviews are structured (fixed question list) or unstructured (open-ended), depending on how well the topic is already understood. Observation (job shadowing) is active (the BA asks questions during the task) or passive (the BA only watches and records).

Ensures a requirement or design is well-formed, at the right level of abstraction, and meets quality standards (BABOK v3). Verification asks: was the requirement written correctly?

Ensures a requirement or design delivers business value and aligns to business goals and objectives (BABOK v3). Validation asks: was the correct requirement identified? A requirement can pass verification yet still fail validation if it no longer supports a business objective.

Acceptance criteria describe the minimum set of requirements a solution must meet to be acceptable to key stakeholders. Evaluation criteria support a broader comparative assessment of a solution, or competing options, against a set of standards.

Comparing solution options covers three factors: technical (can it be built with available technology/skills), operational (can the organization run it day to day), and economic (is it cost-effective). Risk Analysis and Management is the named BABOK technique used alongside feasibility to weigh implementation, operational, adoption, technology, and financial risk.

Responsible (does the work) and Consulted (two-way input gathered before a decision) can involve multiple stakeholders. Exactly one stakeholder is ever Accountable for a given activity. Informed means the stakeholder is only notified after the fact.

BABOK v3 identifies four underlying communication skills: verbal, non-verbal, written, and listening. Active listening includes restating what a stakeholder said in the analyst's own words and watching for non-verbal cues that may signal unspoken disagreement.

An output is the tangible or intangible artifact a change produces (e.g., a new report). An outcome is the end benefit realized because of that output (e.g., faster decisions). Tracking progress focuses on outcomes, not just outputs.

Potential value is the value expected or projected before a solution is implemented. Realized (actual) value is what the solution genuinely delivers, confirmed only after it is in use. A KPI is a metric explicitly tied to a solution's success against a business objective; leading indicators predict future performance, lagging indicators confirm outcomes after they occur.

A constraint is an internal restriction imposed by the organization or team that limits the solution options available. A dependency is a relationship in which one element relies on the completion or existence of another (BABOK v3).

Describes how a business analyst determines which activities are necessary to perform business analysis on a given initiative, including the BA approach, stakeholder engagement, governance, and how BA performance itself is monitored and improved.

Describes how a business analyst prepares for and conducts elicitation activities, confirms the results, and collaborates with stakeholders to communicate information throughout an initiative.

Describes how a business analyst manages and maintains requirements and design information from inception to retirement, including tracing, maintaining, prioritizing, and approving requirements, and managing changes to them.

Describes how a business analyst analyzes the current state of an enterprise, defines a desired future state, assesses risks, and defines a change strategy to move from the current state to the future state.

Describes how a business analyst structures, organizes, specifies, and models requirements and designs, verifies and validates information, and identifies solution options that meet business needs.

Describes how a business analyst assesses the performance of, and value delivered by, a solution in use, and recommends actions to increase the value the solution delivers.

Generates a large volume of creative ideas from a group by deferring judgment during idea generation; ideas are evaluated only after generation is complete.

Elicits information one-on-one or in small groups; best suited to a few knowledgeable stakeholders or sensitive topics. Structured interviews use a fixed question list; unstructured interviews are open-ended exploration.

Brings diverse stakeholders together in a facilitated session to reach group consensus on requirements quickly.

Reviews existing business or technical documentation (policies, procedures, system documentation) to establish the as-is state without requiring additional stakeholder time.

Sorts requirements into four categories: Must have (non-negotiable), Should have, Could have, and Won't have this time. "Won't have" means deferred from the current scope, not permanently rejected.

Captures a requirement briefly from the perspective of the person who wants the capability, typically in an "As a... I want... so that..." format, paired with acceptance criteria to drive iterative delivery.

Organizes internal Strengths and Weaknesses and external Opportunities and Threats to support strategic decision-making.

Distinguishes a problem's underlying cause from its visible symptoms, often using the 5 Whys or a fishbone (Ishikawa) diagram. It looks backward at a known problem, while Risk Analysis and Management looks forward at potential future uncertainty.

BABOK Chapter 9 groups 29 underlying competencies into six categories: Analytical Thinking & Problem Solving (7), Behavioural Characteristics (5), Business Knowledge (5), Communication Skills (4), Interaction Skills (5), and Tools and Technology (3). All 29 are considered testable on the ECBA.

Facilitation means guiding a group neutrally toward its own outcome. Leadership and Influencing means actively persuading stakeholders toward a specific direction. Both are Interaction Skills competencies (BABOK Chapter 9) but differ in whether the BA steers the outcome.