I85PREP
⌘ K
EXIN BCS Agile BA Professional study materials
EXIN BCS Agile BA Professional study resources

EXIN BCS Agile BA Professional practice questions

One question at a time. Build your EXIN BCS Agile BA Professional understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1Agile business analysis principles and mindset

In an Agile business analysis context, what does the principle of 'just enough, just in time' primarily guide a business analyst to do?

  1. Hand requirement decisions entirely to the product owner without analyst involvement
  2. Defer all analysis until the final iteration before release
  3. Elaborate analysis artefacts only when they are needed and only to the depth the current decision requires Correct answer.
  4. Produce detailed requirements documentation up front so the delivery team is never blocked

Explanation

Agile business analysis favours lightweight, timely artefacts: analysis is performed when a decision or delivery step actually needs it, and only to the level of detail that step requires. This avoids the waste of speculative documentation that may be invalidated by learning.

Question 2Agile business analysis principles and mindset

Which behaviour best illustrates the Agile BA mindset of 'collaboration over contract negotiation'?

  1. Agreeing a fixed requirements baseline before development starts
  2. Escalating every requirement change through a formal change control board
  3. Documenting acceptance criteria in isolation and emailing them to the team
  4. Working with developers and stakeholders continuously to refine shared understanding Correct answer.

Explanation

The Agile value statement prioritises individuals and interactions and customer collaboration over rigid contractual mechanisms. For a business analyst this translates into continuous, conversation-based refinement of understanding with the people who build and use the solution.

Question 3Agile business analysis principles and mindset

An organisation asks a business analyst to define all requirements for a twelve-month programme before any development begins. How should an Agile BA respond?

  1. Refuse to participate because Agile forbids any forward planning
  2. Propose incremental elaboration aligned to delivery slices, with a lightweight roadmap for the longer horizon Correct answer.
  3. Accept, because comprehensive requirements are always required for large programmes
  4. Produce the full specification but label it a product backlog

Explanation

Agile business analysis scales by elaborating detail close to the point of use while still providing lightweight, longer-horizon visibility. This balances the organisation's need for planning with the reality of change and learning.

Question 4Agile business analysis principles and mindset

What is the primary purpose of the 'definition of ready' in an Agile BA context?

  1. To establish a shared, agreed set of criteria a backlog item should meet before it is taken into delivery Correct answer.
  2. To list the technical tasks a developer must complete during an iteration
  3. To record which stakeholders have signed off the requirements
  4. To document the retrospective actions of the previous sprint

Explanation

A definition of ready is a team-agreed checklist describing the conditions a backlog item should satisfy before work starts, supporting shared understanding. It helps the analyst judge when analysis is sufficient to begin delivery.

Question 5Agile business analysis principles and mindset

A business analyst discovers that two stakeholder groups interpret the same requirement differently. Which Agile BA action best reflects the mindset of valuing working software and shared understanding?

  1. Facilitate a conversation with both groups and agree concrete examples of expected behaviour Correct answer.
  2. Write a longer requirements document so both interpretations are recorded
  3. Defer the requirement until the next programme increment
  4. Choose the interpretation of the most senior stakeholder without discussion

Explanation

Agile business analysis resolves ambiguity through conversation and concrete examples rather than through accumulating text. Examples make expected behaviour testable and expose differing assumptions quickly.

Question 6Agile business analysis principles and mindset

Which statement best describes the Agile BA's relationship with the product owner?

  1. The business analyst and product owner should avoid interacting to preserve role clarity
  2. The business analyst replaces the product owner for all requirement decisions
  3. The business analyst reports to the product owner only on documentation status
  4. The business analyst supports the product owner by eliciting, analysing and structuring information to inform prioritisation Correct answer.

Explanation

In Agile teams the product owner owns value and prioritisation, while the business analyst contributes analysis skills that help shape and inform those decisions. The roles are complementary rather than competing.

Question 7Agile business analysis principles and mindset

Why does Agile business analysis favour vertical slices of a solution over horizontal layers when elaborating requirements?

  1. Vertical slices remove the need for acceptance criteria
  2. Vertical slices reduce the total number of requirements to be written
  3. Horizontal layers are easier to document in a requirements specification
  4. Each slice delivers an end-to-end, demonstrable increment that generates early feedback Correct answer.

Explanation

Vertical slices cut across the solution so each increment can be demonstrated and validated with stakeholders. This produces early feedback, which is the learning mechanism Agile analysis is designed to exploit.

Question 8Agile business analysis principles and mindset

Which of the following best reflects the Agile principle of 'responding to change over following a plan' for a business analyst?

  1. Treating the backlog as a living artefact that is re-prioritised as new information emerges Correct answer.
  2. Recording change requests only after delivery
  3. Keeping the backlog stable so the team is not disrupted
  4. Freezing scope at the start of each release

Explanation

Agile planning is continuous and the backlog is expected to evolve as learning occurs. The analyst maintains and refines it so that change is absorbed deliberately rather than resisted.

Question 9Agile business analysis principles and mindset

A stakeholder insists that every requirement must be fully specified and signed off before any development. Which response is most consistent with Agile BA principles?

  1. Produce the specification but omit acceptance criteria to save time
  2. Explain that detailed specification is deferred until the point of use, while agreeing lightweight acceptance criteria and a prioritised roadmap now Correct answer.
  3. Refuse to work with the stakeholder until they accept Agile
  4. Agree to full specification because stakeholder preference always overrides process

Explanation

The Agile BA negotiates the level and timing of detail rather than rejecting the stakeholder's concern. Providing a prioritised roadmap and clear acceptance criteria gives confidence without speculative full specification.

Question 10Agile business analysis principles and mindset

What role does 'value' play in prioritising analysis effort in an Agile BA approach?

  1. Analysis effort should be spread evenly across all backlog items
  2. Analysis effort should be concentrated on items the team finds most technically interesting
  3. Analysis effort should follow the items that are highest value or highest risk and therefore being delivered soonest Correct answer.
  4. Analysis effort should focus on the items easiest to document

Explanation

Agile business analysis is value-driven: detailed analysis is invested where the team is about to deliver or where uncertainty and risk are greatest. This concentrates effort where it produces the most learning and value.

Question 11Agile business analysis principles and mindset

Which practice most directly supports the Agile BA principle of making progress visible to stakeholders?

  1. Sending monthly status reports summarising documentation completed
  2. Maintaining a hidden analysis repository accessible only to the analyst
  3. Presenting a final specification at the end of the programme
  4. Demonstrating working increments and reviewing the evolving backlog with stakeholders regularly Correct answer.

Explanation

Agile makes progress visible through demonstrated increments and transparent, evolving backlogs. Stakeholders can then inspect what has been achieved and steer the work accordingly.

Question 12Agile business analysis principles and mindset

An analyst is tempted to add detailed technical design decisions to user stories. Which Agile BA principle should guide them?

  1. The analyst should avoid writing user stories altogether
  2. The analyst should document design decisions only in the retrospective
  3. The analyst should specify all design to ensure consistency
  4. The analyst should focus on the problem and outcomes, leaving solution design to the delivery team Correct answer.

Explanation

Agile business analysis concentrates on understanding the problem space and desired outcomes, enabling the delivery team to own solution design. This separation preserves team autonomy and technical judgement.

Question 13Agile business analysis principles and mindset

Which of the following best characterises 'rolling wave' planning as applied by an Agile business analyst?

  1. Planning only after each release has finished
  2. Planning near-term work in detail while keeping later work at a higher, lighter level Correct answer.
  3. Planning the whole delivery in detail once and never revising it
  4. Planning without any stakeholder involvement

Explanation

Rolling wave planning elaborates near-term detail and keeps the longer horizon at a coarser level, to be refined as more is learned. This matches the just-in-time elaboration principle in Agile analysis.

Question 14Agile business analysis principles and mindset

A team is deciding how much analysis is enough for an upcoming iteration. Which consideration is most aligned with Agile BA thinking?

  1. Enough analysis to satisfy the latest documentation template
  2. Enough analysis to eliminate the need for further conversation
  3. Enough analysis for the team to start confidently and reduce the most significant uncertainty Correct answer.
  4. Enough analysis to cover every conceivable edge case in advance

Explanation

Sufficiency in Agile analysis is judged by the team's confidence to proceed and by the reduction of significant uncertainty. It is a pragmatic threshold, not an exhaustive or template-driven one.

Question 15Agile business analysis principles and mindset

Which statement about the Agile BA mindset toward failure and learning is most accurate?

  1. Failures and surprises are treated as learning opportunities that inform the next increment of analysis Correct answer.
  2. Failures should be hidden to protect stakeholder confidence
  3. Failures should trigger a return to full up-front specification
  4. Failures indicate the analyst should reduce stakeholder contact

Explanation

Agile treats short feedback loops as a way to learn quickly, including from mistakes. The analyst uses what is learned to refine understanding and priorities in the next increment.

Question 16Agile business analysis principles and mindset

A business analyst is asked to 'be the voice of the customer' in refinement sessions. What does this most appropriately mean in Agile BA practice?

  1. Documenting the customer's exact words verbatim in every story
  2. Bringing evidence of customer needs and outcomes into the conversation so the team can make informed decisions Correct answer.
  3. Making final decisions on the customer's behalf without consulting them
  4. Replacing the product owner in all customer-facing discussions

Explanation

Representing the customer means ensuring customer evidence and outcomes inform team decisions, not usurping the customer's or product owner's authority. The analyst supplies insight that improves the quality of decisions.

Question 17Agile business analysis principles and mindset

Which of the following best describes how an Agile business analyst should treat assumptions?

  1. Suppress them so the team is not distracted
  2. Convert them immediately into fixed requirements
  3. Record them once in the business case and leave them unchanged
  4. Make them explicit, validate them early and revisit them as evidence emerges Correct answer.

Explanation

Assumptions are a major source of risk in analysis, so Agile practice surfaces them and tests them as early as possible. Once validated or invalidated, the analysis and backlog are updated accordingly.

Question 18Agile business analysis principles and mindset

How does the Agile BA principle of 'individuals and interactions' shape the preferred way to resolve a requirement ambiguity?

  1. Through direct conversation between the people involved, supported by lightweight notes Correct answer.
  2. Through a formal change request raised to the steering committee
  3. Through a decision recorded only in the test plan
  4. Through a written clarification request routed through a document owner

Explanation

The value of individuals and interactions favours resolving ambiguity through direct conversation, with lightweight notes to capture the outcome. This is faster and produces richer shared understanding than routing through documents.

Question 19Agile business analysis principles and mindset

A stakeholder asks for a complete data model covering the whole enterprise before a single feature is built. Which Agile BA response is most appropriate?

  1. Model only the data needed for the imminent features, with a lightweight conceptual view of the wider landscape Correct answer.
  2. Abandon data modelling because Agile does not value models
  3. Model the enterprise but keep the model confidential from developers
  4. Build the full enterprise model because data modelling must always precede development

Explanation

Agile analysis models only what the near-term work requires while retaining a lightweight view of the broader context. This avoids speculative modelling while keeping the team aware of enterprise constraints.

Question 20Agile business analysis principles and mindset

Which behaviour is least consistent with the Agile BA mindset of servant leadership within a delivery team?

  1. Coaching stakeholders and developers toward shared understanding
  2. Directing developers on how to implement each story Correct answer.
  3. Facilitating workshops to clarify outcomes
  4. Removing analysis blockers that impede the team

Explanation

Servant leadership supports the team's ability to do its work rather than directing how it is done. Telling developers how to implement stories takes ownership away from the people doing the work.

Question 21Agile business analysis principles and mindset

What is the main reason Agile business analysis emphasises outcomes over outputs?

  1. Outputs cannot be demonstrated to stakeholders
  2. Outputs are easier to measure than outcomes
  3. Outcomes describe the change in behaviour or value that stakeholders need, which guides better decisions than counting deliverables Correct answer.
  4. Outcomes remove the need for acceptance criteria

Explanation

Focusing on outcomes keeps analysis anchored to the value stakeholders seek rather than to the volume of features delivered. This improves prioritisation and helps the team evaluate whether the solution is actually achieving its purpose.

Question 22Agile business analysis principles and mindset

An analyst notices the team is building a feature that no longer aligns with the current business goal. Which Agile BA action is most appropriate?

  1. Raise the misalignment with the product owner so prioritisation can be reconsidered Correct answer.
  2. Quietly remove the feature from the backlog without discussion
  3. Continue building it to avoid disrupting the iteration plan
  4. Document the misalignment and address it at the next annual review

Explanation

The Agile BA continuously checks alignment between work in progress and current business goals. Surfacing misalignment to the product owner allows prioritisation to be adjusted transparently.

Question 23Agile business analysis principles and mindset

How should an Agile business analyst balance the need for documentation with the value of working software?

  1. Avoid documentation entirely because working software is the only measure of progress
  2. Produce comprehensive documentation for every story to be safe
  3. Produce documentation after release so it does not slow delivery
  4. Produce documentation only when it serves a real communication or compliance need, keeping it as lean as possible Correct answer.

Explanation

Agile values working software over comprehensive documentation but does not forbid documentation. The analyst produces lean artefacts where they add real communication, decision or compliance value.

Question 24Agile business analysis principles and mindset

Which situation best demonstrates an Agile business analyst applying systems thinking?

  1. Analysing a single user story in isolation from its surrounding processes
  2. Optimising one team's workflow at the expense of the end-to-end customer journey
  3. Documenting each department's requirements separately without comparison
  4. Considering how a change to one business process affects upstream and downstream stakeholders and systems Correct answer.

Explanation

Systems thinking considers the whole end-to-end system and the ripple effects of change across stakeholders, processes and technology. This prevents local optimisation that harms overall value delivery.

Question 25Agile business analysis principles and mindset

A programme wants to standardise every team's analysis artefacts to a single detailed template. Which critique is most consistent with Agile BA principles?

  1. Standardisation is acceptable only if the template is longer than the previous one
  2. A rigid template can impose unnecessary detail and should instead be a lightweight guide that teams tailor to context Correct answer.
  3. Templates should be banned because Agile rejects all standards
  4. Standardisation always improves quality and should be accepted without question

Explanation

Agile BA favours fit-for-purpose artefacts over rigid conformity, so standards work best as lightweight guides that teams adapt to their context. This preserves consistency where it helps while avoiding unnecessary detail.

Question 26Agile business analysis principles and mindset

Which statement best captures why Agile business analysis treats requirements as conversations rather than fixed artefacts?

  1. Only the product owner is permitted to describe what the business needs
  2. Written requirements are prohibited because documentation slows delivery
  3. Understanding emerges through dialogue, so requirements are refined continuously as knowledge grows Correct answer.
  4. Conversations remove the need to record any decisions for later reference

Explanation

Agile business analysis assumes that understanding is discovered rather than fully known up front, so dialogue with stakeholders is the primary vehicle for elaborating needs. Artefacts still capture outcomes, but they are lightweight and evolve as shared understanding improves.

Question 27Agile business analysis principles and mindset

An Agile BA is deciding how much detail to add to a backlog item that will not be built for several months. What is the most appropriate mindset?

  1. Capture just enough to preserve intent and defer detail until it is near delivery Correct answer.
  2. Specify it fully now so that nothing is forgotten later
  3. Hand the item to a developer and let them invent the detail
  4. Omit it from the backlog until the team is ready to start it

Explanation

Agile BA applies progressive elaboration, keeping far-future items coarse and adding precision when feedback and timing make detail useful. This avoids investing in specifications that will change before they are built.

Question 28Agile business analysis principles and mindset

Which behaviour best demonstrates that an Agile BA values customer collaboration over contract negotiation?

  1. Limiting stakeholder contact to formal change-control meetings
  2. Sending requirements documents to the customer for signature at each stage
  3. Freezing the scope in a contract so that changes are formally rejected
  4. Inviting business stakeholders to review increments and adjust requirements together Correct answer.

Explanation

The Agile value of customer collaboration means working with stakeholders continuously so that needs and solutions co-evolve. Regular joint review of increments turns the relationship into a partnership rather than a transactional exchange.

Question 29Agile business analysis principles and mindset

Why does Agile business analysis recommend delivering value early and often rather than in a single big-bang release?

  1. It allows the business to realise benefit sooner and to steer later work using real feedback Correct answer.
  2. It removes the need for any stakeholder involvement after launch
  3. It guarantees that scope will never change after the first release
  4. It proves that the analysis phase is complete and can be closed

Explanation

Early, frequent delivery lets the organisation gain benefit before the whole solution exists and generates evidence that shapes subsequent analysis. The BA uses that feedback to confirm, refine, or discard requirements.

Question 30Agile business analysis principles and mindset

An Agile BA is facilitating a workshop where two business units describe conflicting definitions of 'active customer'. Which mindset most helps resolve this?

  1. Record both definitions and defer the decision indefinitely
  2. Escalate immediately to senior management without any prior discussion
  3. Assume the largest business unit's definition is automatically authoritative
  4. Treat the conflict as useful information and facilitate a shared definition with the affected parties Correct answer.

Explanation

Agile BA welcomes differing perspectives as a source of insight and uses collaboration to build a shared understanding. Facilitating agreement among the people who own the concepts produces a definition the whole organisation can use.

Question 31Agile business analysis principles and mindset

Which statement best describes the Agile BA's stance on the 'comprehensive documentation' value?

  1. Documentation has value when it serves a real communication or compliance need, so it is produced deliberately and kept lean Correct answer.
  2. Documentation quality is measured by the number of pages produced
  3. Documentation should be as exhaustive as in a waterfall programme to satisfy auditors
  4. Documentation should be eliminated because working software is always enough

Explanation

Agile BA does not reject documentation; it weighs its cost against its usefulness and produces what is genuinely needed. Lean, purposeful artefacts support communication and governance without becoming an end in themselves.

Question 32Agile business analysis principles and mindset

An Agile BA is asked to describe the mindset behind 'working software over comprehensive documentation'. Which interpretation is most accurate for business analysis?

  1. Analysis should produce artefacts that demonstrably help the team deliver valuable working solutions Correct answer.
  2. Analysis has no value unless it is embedded in code
  3. Software must always be released before any analysis is performed
  4. Documentation should be replaced entirely by verbal briefings

Explanation

The value directs analysis toward enabling delivery of valuable working solutions rather than producing documents for their own sake. The BA still analyses, but measures success by the usefulness of the outcome.

Question 33Agile business analysis principles and mindset

What does the Agile BA mindset of 'enough is enough' most directly encourage when deciding how much analysis to do?

  1. Skipping analysis entirely for small backlog items
  2. Stopping when the team has sufficient shared understanding to deliver and learn Correct answer.
  3. Continuing analysis until every possible exception has been documented
  4. Stopping analysis as soon as a single stakeholder is satisfied

Explanation

'Enough' analysis is the point at which the team understands the need well enough to build and test it, with remaining detail deferred. This balances the risk of building the wrong thing against the cost of over-analysis.

Question 34Agile business analysis principles and mindset

A sponsor asks the Agile BA to guarantee that the delivered solution will match the original specification exactly. Which response best reflects Agile BA thinking?

  1. Explain that the goal is to deliver the best value against evolving needs, with traceability to decisions as they change Correct answer.
  2. Accept the guarantee, because Agile fixes scope at the start
  3. Promise exact conformance provided no stakeholder attends reviews
  4. Refuse to discuss the specification at all

Explanation

Agile BA treats the original specification as a starting hypothesis, not a guarantee, because learning during delivery may reveal better options. The BA maintains traceability so that changes are deliberate and visible rather than uncontrolled.

Question 35Agile business analysis principles and mindset

How should an Agile BA treat a non-functional concern such as response time when it is raised late in delivery?

  1. Capture it as a quality attribute, make it visible in the backlog, and agree how it will be evidenced Correct answer.
  2. Document it but leave it untested until after go-live
  3. Convert it into a separate waterfall project
  4. Discard it because non-functional requirements cannot be analysed iteratively

Explanation

Quality attributes are analysed iteratively like any other need, captured in a way the team can act on, and given explicit acceptance evidence. Making them visible ensures they influence design and testing rather than being discovered at the end.

Question 36Agile business analysis principles and mindset

Which practice best reflects the Agile BA principle of welcoming changing requirements, even late in development?

  1. Assessing late changes for value and impact, then incorporating them through normal prioritisation Correct answer.
  2. Rejecting late changes to protect the original baseline
  3. Requiring a change board to meet monthly before any change is considered
  4. Allowing any change without assessment so that nobody is inconvenienced

Explanation

Welcoming change does not mean accepting every change uncritically; it means treating change as expected and evaluating it for value and impact. Normal prioritisation keeps the backlog aligned with current business goals.

Question 37Agile business analysis principles and mindset

An Agile BA is supporting a team new to iterative delivery. Which approach to planning analysis work best fits the Agile mindset?

  1. Plan only one day ahead so that no commitments are ever made
  2. Avoid planning analysis because plans are incompatible with Agile
  3. Plan analysis in thin increments, refining the near-term view and keeping the longer view coarse Correct answer.
  4. Produce a complete analysis plan for the whole programme before any iteration starts

Explanation

Rolling-wave planning keeps near-term analysis commitments concrete while the horizon stays intentionally coarse, so plans can adapt as learning occurs. This supports predictability without pretending the future is known.

Question 38Agile business analysis principles and mindset

A delivery team asks the Agile BA to approve a design decision that belongs to the architects. What is the most appropriate response?

  1. Escalate the request to the sponsor as a scope change
  2. Document the design in detail so that accountability is clear
  3. Approve it so that the team is not blocked
  4. Decline to decide and instead help the team identify the right decision owner while ensuring the business need is represented Correct answer.

Explanation

Agile BA respects role boundaries while ensuring business context informs technical decisions. The BA facilitates the right people making the decision rather than substituting for them.

Question 39Agile business analysis principles and mindset

Which attitude best characterises how an Agile BA handles uncertainty about a proposed solution?

  1. Choose the most complex option because it is likely to be most complete
  2. Suppress uncertainty so that stakeholders remain confident
  3. Wait until all uncertainty is removed before any analysis is shared
  4. Frame uncertainty as hypotheses to be tested cheaply and early with stakeholders Correct answer.

Explanation

Agile BA treats uncertainty as something to reduce through small, fast experiments and stakeholder feedback rather than analysis paralysis. Hypotheses make assumptions explicit and testable.

Question 40Agile business analysis principles and mindset

A business analyst new to Agile keeps producing detailed functional specifications before stories are written. Which mindset shift is most needed?

  1. Move from talking to stakeholders to working alone to save time
  2. Move from specifying solutions to facilitating shared understanding of needs and outcomes Correct answer.
  3. Move from iterative delivery to a single big-bang release
  4. Move from testing assumptions to assuming the specification is correct

Explanation

Agile BA shifts emphasis from producing definitive solution specifications to enabling the team and stakeholders to understand the problem and desired outcome. Detail then emerges collaboratively as the team builds and learns.

Question 41Agile business analysis principles and mindset

How does the Agile BA mindset treat the concept of a 'definition of ready' for backlog items?

  1. As a rigid gate that permanently rejects any item lacking full detail
  2. As a document owned solely by the business sponsor
  3. As an optional formality that has no effect on delivery
  4. As a shared team agreement about sufficient understanding, reviewed and adapted over time Correct answer.

Explanation

A definition of ready is a team-owned agreement describing when an item is understood well enough to start, and it evolves as the team learns. It supports shared understanding rather than acting as a bureaucratic gate.

Question 42Agile business analysis principles and mindset

An Agile BA notices that a stakeholder group is consistently excluded from refinement sessions although their processes are affected. Which principle should prompt action?

  1. Contract negotiation, because exclusion protects the original agreement
  2. Comprehensive documentation, because the group can read the specification later
  3. Following a plan, because the schedule was agreed in advance
  4. Individuals and interactions, because excluded voices prevent shared understanding Correct answer.

Explanation

The value of individuals and interactions highlights that understanding is built through the right people talking together. Excluding an affected group guarantees blind spots that surface later as rework.

Question 43Agile business analysis principles and mindset

Which statement best explains why Agile business analysis favours emergent design of requirements over a fixed baseline?

  1. Emergent requirements are always cheaper to produce than baselined ones
  2. Fixed baselines are impossible to create in any methodology
  3. Emergent requirements remove the need for any change control
  4. Understanding improves through delivery feedback, so requirements should be allowed to evolve deliberately Correct answer.

Explanation

Emergent requirements reflect the reality that stakeholders learn what they need by seeing working increments. Deliberate evolution keeps the backlog aligned with value while preserving appropriate control.

Question 44Agile business analysis principles and mindset

A team wants to reduce the time between a requirement being identified and its value being demonstrated. Which Agile BA behaviour most directly supports this?

  1. Deferring all stakeholder feedback until the final release
  2. Batching analysis into large documents delivered at phase boundaries
  3. Collaborating with the team to slice and refine items so that small, valuable increments can be delivered Correct answer.
  4. Increasing the number of approval signatures required per item

Explanation

Shortening the idea-to-value cycle depends on small, well-understood increments that can be built and validated quickly. The BA contributes by slicing work and refining just in time so the team is never blocked.

Question 45Agile business analysis principles and mindset

An organisation measures its business analysts by the number of requirement documents produced. Which critique is most consistent with Agile BA principles?

  1. It is problematic because analysis should not be measured at all
  2. It is flawed only because documents are never useful
  3. It is acceptable because volume correlates perfectly with quality
  4. It encourages output-focused behaviour rather than outcomes that deliver business value Correct answer.

Explanation

Measuring document volume rewards activity rather than the value delivered to the business. Agile BA aligns measures with outcomes, such as decisions enabled and value realised, rather than artefact counts.

Question 46Agile business analysis principles and mindset

A stakeholder argues that because Agile embraces change, no requirement should ever be considered stable. Which response reflects a sound Agile BA position?

  1. Explain that decisions can be stabilised for a period while remaining open to evidence-driven change Correct answer.
  2. Insist that all requirements must be frozen at the start of every iteration
  3. Agree, because stability is incompatible with Agile
  4. Propose abandoning prioritisation so that everything can change at once

Explanation

Agile BA distinguishes between commitment to a near-term increment and openness to change based on new evidence. Temporary stability enables delivery, while explicit review points allow deliberate adjustment.

Question 47Agile business analysis principles and mindset

An Agile BA is working in a regulated environment where evidence of analysis decisions is audited. Which approach best reconciles Agile mindset with this constraint?

  1. Abandon Agile practices because regulation is incompatible with them
  2. Rely on team memory and reconstruct records only if an audit occurs
  3. Create exhaustive documentation for every conversation held
  4. Produce lean, traceable records of decisions as a by-product of normal collaboration, sized to satisfy the audit need Correct answer.

Explanation

Agile BA treats necessary documentation as a legitimate requirement and captures it efficiently within normal working practice. Traceable decision records satisfy audit needs without reverting to exhaustive specification.

Question 48Agile business analysis principles and mindset

Two teams deliver components of one customer journey and optimise their own backlogs independently, producing a disjointed experience. Which Agile BA response best reflects systems thinking?

  1. Ask each team to optimise its own component more efficiently
  2. Merge the teams so that a single backlog is the only option
  3. Facilitate end-to-end analysis of the journey and align both backlogs to shared customer outcomes Correct answer.
  4. Escalate the issue and wait for a central team to take ownership

Explanation

Systems thinking focuses on the behaviour of the whole rather than locally optimised parts. The BA makes the end-to-end journey visible and aligns priorities to shared outcomes across team boundaries.

Question 49Agile business analysis principles and mindset

A product owner wants to defer all analysis until the iteration begins so that the team 'stays lean'. Which risk is most significant from an Agile BA perspective?

  1. Stakeholders may become too involved in refinement
  2. The backlog may become too small to manage
  3. Critical dependencies and assumptions may surface too late to influence prioritisation and design Correct answer.
  4. The team may deliver too much documentation

Explanation

Just-in-time analysis still requires enough lead time to expose dependencies and test assumptions before commitments are made. Deferring everything to iteration start pushes discovery into delivery, where it is costly.

Question 50Agile business analysis principles and mindset

An Agile BA must choose between documenting a complex business rule in detail now or prototyping it with users next week. Which consideration should dominate the decision?

  1. Which option follows the template used on the previous project
  2. Which option avoids any contact with users
  3. Which option produces the longest document
  4. Which option most cheaply and reliably reduces the uncertainty that matters most Correct answer.

Explanation

The choice should be driven by which technique most efficiently resolves the significant uncertainty. Where users can react to something concrete, a prototype often yields better understanding than further prose.