I85PREP
⌘ K
IIBA-AAC study materials
IIBA-AAC study resources

IIBA-AAC practice questions

One question at a time. Build your IIBA-AAC 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 Analysis

In the BACCM, which core concept describes any change that is of value to stakeholders and is within the scope of the solution?

  1. A need
  2. A stakeholder
  3. A change Correct answer.
  4. A solution

Explanation

The BACCM defines six concepts: change, need, solution, stakeholder, value, and context. Change refers to an act or instance of alteration that has value to stakeholders and is within scope. Need is the problem or opportunity, and solution is the specific way needs are satisfied.

Question 2Agile Analysis

An agile BA is choosing how much detail to add to a user story before the next iteration. Which principle from the Agile Extension should guide the amount and timing of this detail?

  1. Write the full acceptance criteria for the entire backlog
  2. Defer all elaboration until after the release is delivered
  3. Specify everything up front so developers are never blocked
  4. Elaborate detail just in time, only as much as is needed to act Correct answer.

Explanation

Agile analysis favors just-in-time elaboration, producing only enough detail to support the next decision or step. This avoids rework from prematurely specified requirements that change. Detail is added progressively as understanding grows.

Question 3Agile Analysis

A team needs a lightweight artifact that captures a goal, the users, and the value in one sentence before committing to build. Which agile analysis practice fits best?

  1. A story card with a role, goal, and benefit statement Correct answer.
  2. A formal change control request
  3. A full software requirements specification
  4. A detailed entity-relationship diagram

Explanation

The role-goal-benefit format (as a role, I want goal, so that benefit) captures the who, what, and why concisely. It communicates value quickly and supports conversation. Heavyweight specifications and data models are not lightweight intent statements.

Question 4Agile Analysis

What does the 'Definition of Done' primarily provide to an agile team?

  1. A prioritized list of features for the next release
  2. A schedule of who works on which task
  3. A record of every defect found in testing
  4. A shared agreement on the quality criteria an increment must meet Correct answer.

Explanation

The Definition of Done is a shared checklist of quality criteria that an increment must satisfy to be considered complete. It creates a common understanding of completeness across the team. It is not a backlog, defect log, or task schedule.

Question 5Agile Analysis

Which statement best describes how value is understood in agile analysis?

  1. Value is defined solely by the development team
  2. Value is fixed at project initiation and cannot change
  3. Value is determined by stakeholders and may be realized over time Correct answer.
  4. Value is measured only by lines of code delivered

Explanation

In agile analysis, value is a stakeholder judgment about what is worthwhile, and it can be realized progressively as increments reach users. It is not static and is not defined by the team alone. Delivery volume is not a proxy for value.

Question 6Agile Analysis

An agile BA wants to visualize a backlog item's path from idea to delivered value. Which technique is most appropriate for showing the flow of work states?

  1. A RACI matrix of team roles
  2. A SWOT analysis of the market
  3. A use case diagram of system actors
  4. A value stream map of the delivery workflow Correct answer.

Explanation

A value stream map depicts the steps and states work passes through, exposing delays and handoffs. It helps teams see where value is added or lost. RACI, SWOT, and use case diagrams serve different purposes.

Question 7Agile Analysis

Which of the following is a characteristic of an effective agile analysis approach to requirements?

  1. Requirements emerge and are refined through collaboration Correct answer.
  2. Requirements are documented once and never revisited
  3. Requirements are frozen before any design work begins
  4. Requirements are owned exclusively by the business sponsor

Explanation

Agile analysis treats requirements as emergent, refined through ongoing collaboration between stakeholders and the team. This supports responding to change. Freezing, one-time documentation, and single-owner control conflict with that principle.

Question 8Agile Analysis

What is the primary purpose of a retrospective in agile analysis work?

  1. To inspect how the team works and identify improvements Correct answer.
  2. To gather new requirements from customers
  3. To approve the budget for the next release
  4. To demonstrate the increment to stakeholders

Explanation

A retrospective is a reflection session where the team inspects its process and identifies improvements. It focuses on how the team works rather than on product content. Requirements gathering and demonstrations happen in other activities.

Question 9Agile Analysis

A product owner has a long list of candidate features and needs to sequence them so that the highest-value items reach users first. Which practice should the agile BA recommend?

  1. Order features alphabetically for predictability
  2. Assign every feature equal priority to avoid conflict
  3. Defer all prioritization until the final release
  4. Rank the backlog by estimated value and risk, refining order each iteration Correct answer.

Explanation

Backlog prioritization sequences work by value, risk, and other factors, and the order is revisited as learning occurs. This ensures the most valuable increments are delivered early. Equal priority, alphabetical order, and deferred prioritization do not optimize value delivery.

Question 10Agile Analysis

During a story-mapping session, the team arranges user activities along a horizontal backbone and places stories beneath them by priority. What is the main benefit of this technique?

  1. It fixes the scope for the entire project
  2. It replaces the need for acceptance criteria
  3. It produces a complete data dictionary
  4. It shows the whole user journey and supports release slicing Correct answer.

Explanation

A story map organizes stories around the user journey, showing the big picture while allowing the team to slice releases horizontally. It supports conversations about scope and sequencing. It does not produce data dictionaries or replace acceptance criteria.

Question 11Agile Analysis

A team is uncertain whether a proposed feature will actually be adopted by users. Which approach best reflects agile analysis under uncertainty?

  1. Escalate the decision to avoid any risk
  2. Document the assumption and proceed without testing
  3. Build the full feature and measure adoption after launch
  4. Run a small experiment or prototype to test the assumption first Correct answer.

Explanation

When uncertainty is high, agile analysis favors small, cheap experiments that generate learning before large investment. Prototypes and experiments test assumptions with limited exposure. Building fully or ignoring the assumption increases risk.

Question 12Agile Analysis

An agile BA is facilitating a session to define acceptance criteria for a story. Which set of criteria best supports agile analysis?

  1. Criteria that list every possible edge case in advance
  2. Criteria that are testable and describe observable outcomes Correct answer.
  3. Criteria that describe internal code structure
  4. Criteria that restate the story title verbatim

Explanation

Good acceptance criteria are testable and describe observable, verifiable outcomes that confirm the story is done. They focus on behavior and value rather than implementation. Restating the title or listing exhaustive edge cases does not achieve this.

Question 13Agile Analysis

A stakeholder keeps adding new requests mid-iteration. How should the agile BA best handle this while preserving the iteration goal?

  1. Extend the iteration until all requests are done
  2. Capture the request in the backlog for later prioritization Correct answer.
  3. Add every request immediately to protect the relationship
  4. Reject the request without recording it

Explanation

New requests during an iteration are captured in the backlog so they can be prioritized against other work rather than disrupting the current goal. This preserves focus while ensuring the idea is not lost. Immediate insertion, silent rejection, and indefinite extension all harm the iteration.

Question 14Agile Analysis

Which technique helps an agile BA understand the root cause of a recurring delivery delay before proposing a solution?

  1. A burn-down chart of remaining work
  2. A stakeholder power-interest grid
  3. A five whys analysis of the delay Correct answer.
  4. A context diagram of external systems

Explanation

Five whys is a root-cause technique that repeatedly asks why to reach the underlying cause of a problem. Understanding cause before solution prevents treating symptoms. The other techniques serve different analysis purposes.

Question 15Agile Analysis

An agile team is deciding whether to split a large epic. Which split best preserves end-to-end value in each slice?

  1. Split by estimated hours to balance effort
  2. Split by developer so each person owns a slice
  3. Split by user workflow so each slice delivers a usable outcome Correct answer.
  4. Split by technical layer so each slice touches one component

Explanation

Splitting by user workflow yields slices that each deliver a usable, end-to-end outcome, preserving value. Layer, person, and effort-based splits tend to produce partial functionality that cannot be demonstrated or released.

Question 16Agile Analysis

A team maintains a product backlog that mixes bugs, features, and technical debt. Which practice best supports transparent prioritization across these types?

  1. Track each type in a separate system invisible to stakeholders
  2. Assign priority based on who submitted the item
  3. Make all items visible in one backlog ranked by value and risk Correct answer.
  4. Prioritize bugs only when customers complain

Explanation

A single visible backlog ranked by value and risk lets stakeholders compare unlike items and make transparent trade-offs. Hiding items or prioritizing by complainant or submitter undermines informed decisions.

Question 17Agile Analysis

Which statement best captures the relationship between the BACCM concepts of need and solution?

  1. A need exists only after a solution has been delivered
  2. A need and a solution are the same concept viewed differently
  3. A need is the problem or opportunity; a solution is a way to satisfy it Correct answer.
  4. A solution always precedes the identification of a need

Explanation

In the BACCM, a need is a problem or opportunity of value to stakeholders, while a solution is a specific way of satisfying one or more needs. Multiple solutions may address a single need. The concepts are distinct and a need exists before its solution.

Question 18Agile Analysis

An agile BA is preparing to elicit requirements from a group with conflicting views. Which facilitation approach best supports reaching shared understanding?

  1. Let the most senior person decide and record their view
  2. Collect written submissions and choose one silently
  3. Use structured techniques to surface and reconcile differing perspectives Correct answer.
  4. Avoid the conflict by excluding dissenting stakeholders

Explanation

Structured facilitation techniques surface differing perspectives and help the group reconcile them into shared understanding. Relying on seniority, silent selection, or exclusion suppresses information and risks poor decisions.

Question 19Agile Analysis

A team uses a burn-up chart that shows scope increasing alongside completed work. What should the agile BA conclude?

  1. The chart is invalid because scope should never change
  2. Scope is growing, so completed work may not reflect progress toward value Correct answer.
  3. The team is definitely behind schedule and must add people
  4. The team should stop tracking completed work

Explanation

A burn-up chart separates scope from completed work, so rising scope shows growth that can offset apparent progress. The BA should investigate whether the added scope is valuable and whether the trend threatens delivery. It does not automatically mean adding people or invalidate the chart.

Question 20Agile Analysis

A stakeholder asks for a detailed interface specification before any design discussion. How should the agile BA respond to balance stakeholder needs with agile principles?

  1. Clarify the underlying need and elaborate the interface just in time with the team Correct answer.
  2. Produce the full specification immediately to satisfy the request
  3. Refuse the request because specifications are not agile
  4. Hand the request to the team without discussion

Explanation

The agile BA probes the underlying need and provides detail at the point it is required, collaborating with the team. This satisfies legitimate stakeholder concerns while avoiding premature over-specification. Immediate full specification or outright refusal are both extremes.

Question 21Agile Analysis

A product owner wants to prioritize a set of features but has limited data on value. Which approach best supports a defensible prioritization decision under uncertainty?

  1. Postpone all prioritization until perfect data exists
  2. Rank by the loudest stakeholder's preference
  3. Prioritize strictly by development effort alone
  4. Use a transparent model combining value, risk, and effort estimates, then validate Correct answer.

Explanation

A transparent prioritization model that weighs value, risk, and effort enables reasoned trade-offs even with imperfect data, and results are validated as learning occurs. Deferring for perfect data stalls delivery, and single-factor or loudest-voice approaches are not defensible.

Question 22Agile Analysis

A team's story map reveals that an entire release slice depends on a single unvalidated assumption about user behavior. What is the most appropriate agile analysis action?

  1. Remove the slice from the map entirely
  2. Escalate to freeze the assumption as a requirement
  3. Insert a small validation experiment before committing the slice Correct answer.
  4. Proceed with the slice and hope the assumption holds

Explanation

When a slice rests on an unvalidated assumption, agile analysis inserts a small experiment to test it before large investment. This reduces risk while preserving the slice's potential value. Proceeding blindly, deleting the slice, or freezing the assumption as a requirement are inferior responses.

Question 23Agile Analysis

An organization wants to scale agile analysis across several teams working on one product. Which practice best maintains a coherent view of value across teams?

  1. Coordinate through a shared product vision and aligned backlog refinement Correct answer.
  2. Let each team maintain a fully independent, unshared backlog
  3. Require each team to use a different prioritization model
  4. Assign one team to write all requirements for the others

Explanation

Scaling agile analysis depends on a shared product vision and coordinated refinement so teams align on value and dependencies. Independent backlogs, centralized authoring, and divergent prioritization models fragment the product view.

Question 24Agile Analysis

A BA observes that a team delivers many features but stakeholders report little benefit. Which analytical lens best explains this gap?

  1. The team is using too many acceptance criteria
  2. Output volume is being confused with realized value Correct answer.
  3. The Definition of Done is too strict
  4. The backlog is too transparent

Explanation

Delivering many features measures output, not the value stakeholders actually realize. Agile analysis distinguishes output from outcomes and value. Acceptance criteria, backlog transparency, and a strict Definition of Done do not explain the gap.

Question 25Agile Analysis

A team is selecting an elicitation technique for a geographically distributed group with limited synchronous time. Which approach best fits agile analysis?

  1. Asynchronous collaborative tools combined with short focused sessions Correct answer.
  2. Collecting requirements solely through formal documents
  3. A single long synchronous workshop with everyone present
  4. Relying only on one-on-one interviews with the sponsor

Explanation

Asynchronous collaboration paired with short focused sessions respects distributed constraints while preserving shared understanding. A single long workshop, sponsor-only interviews, or document-only collection reduce participation and collaboration.

Question 26Agile Analysis

In agile analysis, the product backlog is best understood as which kind of artifact?

  1. A living, ordered list of needs and ideas that evolves as learning occurs Correct answer.
  2. A record of completed work kept only for audit purposes
  3. A technical design document maintained by architects
  4. A frozen contract that is baselined before development begins

Explanation

Agile analysis treats the backlog as an emergent, continuously reordered representation of needs rather than a fixed specification. Ordering reflects current value and risk, and items are refined as understanding grows.

Question 27Agile Analysis

Which concept from the BACCM describes the reason a change is worth making and the value it should deliver?

  1. Need Correct answer.
  2. Context
  3. Stakeholder
  4. Solution

Explanation

In the BACCM, Need captures a problem or opportunity that a solution may address, including the value at stake. Solution, Stakeholder, and Context describe other dimensions that must be considered together with Need.

Question 28Agile Analysis

An agile BA needs a lightweight, visual way to show how a customer moves through a service and where friction occurs. Which technique fits best?

  1. Data flow diagram
  2. Entity relationship diagram
  3. Customer journey map Correct answer.
  4. Gantt chart

Explanation

A customer journey map depicts the customer's end-to-end experience across touchpoints and highlights moments of friction or opportunity. That makes it a natural agile analysis tool for framing needs around customer value.

Question 29Agile Analysis

In agile analysis, what is the primary role of a persona when exploring requirements?

  1. To record the exact wording users gave during interviews
  2. To assign development tasks to individual team members
  3. To estimate the effort required for each backlog item
  4. To represent a recognizable user type so needs can be analyzed from that perspective Correct answer.

Explanation

A persona is a synthesized representation of a user group that helps the team reason about goals, behaviors, and needs. It keeps analysis anchored to real user perspectives rather than abstract requirements.

Question 30Agile Analysis

Which statement best describes how agile analysis treats documentation?

  1. Documentation is eliminated because working software is valued more highly
  2. Documentation is produced only at project closure
  3. Documentation is created just enough and just in time to support shared understanding and decisions Correct answer.
  4. Documentation must be approved by every stakeholder before any analysis continues

Explanation

Agile analysis favors sufficient documentation created when it adds value, rather than exhaustive upfront artifacts. The aim is shared understanding and informed decisions, not documentation for its own sake.

Question 31Agile Analysis

A team writes user stories in the form 'As a <role>, I want <goal>, so that <benefit>'. Which element most directly supports value-based prioritization?

  1. The role
  2. The story identifier
  3. The benefit clause Correct answer.
  4. The goal

Explanation

The benefit clause states why the capability matters, which gives the product owner a basis for comparing value across stories. Role and goal describe who and what, but not the rationale for prioritizing.

Question 32Agile Analysis

Which practice best keeps a distributed agile team aligned on analysis decisions between infrequent meetings?

  1. Sending decisions only to the product owner for safekeeping
  2. Maintaining a visible, shared information radiator that everyone can access asynchronously Correct answer.
  3. Scheduling longer weekly meetings to compensate for distance
  4. Relying on verbal agreements made in corridor conversations

Explanation

A shared, visible information radiator lets distributed team members see the same analysis artifacts and decisions without needing synchronous time. It supports transparency and reduces reliance on memory or private channels.

Question 33Agile Analysis

What distinguishes an agile analysis approach to defining scope from a predictive approach?

  1. Scope is determined exclusively by the delivery team without stakeholder input
  2. Scope is elaborated progressively and adjusted as feedback and learning accumulate Correct answer.
  3. Scope is fixed early and protected from change through formal change control
  4. Scope is defined only after all architecture is finalized

Explanation

Agile analysis accepts that understanding emerges over time, so scope is elaborated progressively and adapted to feedback. Predictive approaches instead try to fix scope early and manage change through formal control.

Question 34Agile Analysis

An agile BA is choosing how much detail to add to a backlog item that will not be built for several iterations. What is the most appropriate approach?

  1. Write only its acceptance tests and no description
  2. Fully specify it now so no further analysis is ever needed
  3. Leave it at a low level of detail and refine it closer to when it will be built Correct answer.
  4. Remove it from the backlog until the iteration begins

Explanation

Progressive elaboration keeps distant items coarse so effort is spent where uncertainty is being reduced soonest. Detail is added as the item approaches delivery, when learning is greatest.

Question 35Agile Analysis

A team discovers mid-iteration that a story's original assumption about user behavior was wrong. Which agile analysis response is most appropriate?

  1. Update the shared understanding, adjust the story or its acceptance criteria, and re-plan with the product owner Correct answer.
  2. Assign blame for the faulty assumption in the retrospective before making changes
  3. Suspend all analysis until the next quarterly planning cycle
  4. Complete the story as originally written to protect the iteration commitment

Explanation

Agile analysis treats new learning as valuable input, so the team revises the story and criteria and re-plans with the product owner. This keeps the work aligned with actual user value instead of a superseded assumption.

Question 36Agile Analysis

Which technique most directly helps an agile BA decompose a broad capability into progressively smaller, independently valuable pieces?

  1. Story decomposition using vertical slices Correct answer.
  2. Documentation sign-off matrix
  3. Cost-benefit ratio ranking
  4. Network diagramming

Explanation

Vertical slicing breaks a capability into thin pieces that each cross the full stack and deliver observable value. That supports incremental delivery and early feedback better than horizontal, layer-based breakdowns.

Question 37Agile Analysis

An agile BA wants to confirm that a delivered story actually meets the user's intent, not merely that it was coded. Which practice best serves this?

  1. Reviewing the story's acceptance criteria with the product owner and demonstrating the working result Correct answer.
  2. Checking that the story was estimated at the planned size
  3. Counting the number of tasks marked complete on the board
  4. Comparing the code against the original technical design

Explanation

Acceptance criteria express the conditions of satisfaction, and demonstrating the working result confirms intent against them. Together they verify value rather than mere completion of activity.

Question 38Agile Analysis

A product owner must choose between two candidate features with similar estimated effort but very different uncertainty. Which agile analysis practice best informs the decision?

  1. Selecting the feature with the more detailed specification
  2. Selecting the feature that is easiest to test after release
  3. Selecting the feature requested by the most senior stakeholder
  4. Selecting the feature that reduces the most significant uncertainty and enables learning Correct answer.

Explanation

When effort is comparable, prioritizing the item that retires the biggest uncertainty maximizes learning per unit of investment. This reflects agile analysis's emphasis on reducing risk early.

Question 39Agile Analysis

Which statement best explains why agile analysis favors collaboration over handoff of a requirements document?

  1. Handoffs are prohibited by agile frameworks
  2. Collaboration surfaces tacit knowledge and allows misunderstanding to be corrected immediately Correct answer.
  3. Documents cannot be stored in version control systems
  4. Documents are always inaccurate

Explanation

Conversation lets participants probe intent, expose assumptions, and correct misunderstanding in the moment, capturing knowledge that is hard to write down. That is why agile analysis treats collaboration as richer than a one-way handoff.

Question 40Agile Analysis

An agile BA is analyzing a process where several approval steps add days of delay but few defects are caught. Which analytical conclusion best fits agile analysis?

  1. The approvals are candidates for removal because they add delay without demonstrated value Correct answer.
  2. The approvals should be retained because they exist in the current process
  3. The approvals should be automated so they take less time but still occur
  4. The process should be documented in more detail before any change

Explanation

Agile analysis examines whether each step contributes value; steps that add delay without catching defects are waste. Identifying and removing such waste improves flow toward delivery.

Question 41Agile Analysis

Which approach best helps an agile BA ensure that non-functional expectations such as performance and security are not forgotten?

  1. Leaving them to the operations group after release
  2. Recording them as explicit constraints or quality attributes attached to relevant stories Correct answer.
  3. Documenting them once in a project charter and not revisiting them
  4. Assuming the team will address them during coding

Explanation

Making quality attributes explicit and tying them to the stories they affect keeps them visible during analysis and delivery. Implicit expectations are easily dropped when work is sliced.

Question 42Agile Analysis

A team's analysis artifacts are scattered across personal notes, chat threads, and local files. Which change most improves transparency for agile analysis?

  1. Requiring each person to keep more detailed private notes
  2. Restricting access to the product owner only
  3. Moving all analysis into a final report delivered at the end
  4. Consolidating analysis information into a single visible, shared space accessible to the team and stakeholders Correct answer.

Explanation

Transparency depends on a shared, accessible source that everyone can inspect and contribute to. Consolidating scattered information reduces misunderstanding and supports joint decision-making.

Question 43Agile Analysis

Which technique best helps an agile BA expose assumptions that, if wrong, would invalidate a proposed solution?

  1. A critical path calculation
  2. A resource histogram
  3. A requirements traceability matrix
  4. Assumption mapping that rates each assumption by importance and evidence Correct answer.

Explanation

Assumption mapping surfaces beliefs underlying a solution and ranks them by how much they matter and how much evidence supports them. That directs analysis and experimentation toward the riskiest beliefs first.

Question 44Agile Analysis

An agile BA must decide whether a new request belongs in the current product backlog or is out of scope for this product. Which consideration is most central to agile analysis?

  1. Whether the request can be implemented without new technology
  2. Whether the request was included in the original business case
  3. Whether the request fits within the current iteration's capacity
  4. Whether the request addresses a need of the product's stakeholders and aligns with the product vision Correct answer.

Explanation

Agile analysis evaluates requests against stakeholder needs and product vision, which define whether the work belongs to this product at all. Capacity and technology are delivery considerations that come after that judgment.

Question 45Agile Analysis

A team slices an epic into pieces that each deliver value, but stakeholders still cannot see progress toward the overall goal. Which analysis improvement is most appropriate?

  1. Add a visual model linking the slices to the product goal so stakeholders can see how each contributes Correct answer.
  2. Convert the epic into a single large story
  3. Stop reporting progress until the epic is complete
  4. Increase the number of slices to make progress more granular

Explanation

Stakeholders need to see how delivered slices advance the overall goal, which a visual linkage between slices and goal provides. More slices alone do not create that line of sight.

Question 46Agile Analysis

Two stakeholders give contradictory acceptance criteria for the same story. What is the most effective agile analysis action?

  1. Choose the criteria from the more senior stakeholder and proceed
  2. Record both sets of criteria and let developers decide later
  3. Facilitate a conversation to surface the underlying needs behind each criterion and agree on a shared condition of satisfaction Correct answer.
  4. Defer the story indefinitely until the conflict resolves itself

Explanation

Contradictory criteria usually reflect differing underlying needs, so facilitated conversation aims to reconcile intent rather than pick a winner. Agreement on shared conditions of satisfaction keeps the story actionable.

Question 47Agile Analysis

An agile BA is modeling a complex domain and wants a technique that shows the events that trigger behavior and the resulting responses. Which approach fits best?

  1. Force field analysis
  2. Event storming Correct answer.
  3. Earned value analysis
  4. Balanced scorecard

Explanation

Event storming is a collaborative modeling technique that maps domain events, the commands that cause them, and the responses around them. It builds shared understanding of complex domains quickly.

Question 48Agile Analysis

A team has strong delivery metrics but stakeholders repeatedly say the delivered increments solve the wrong problem. Which agile analysis failure is most likely?

  1. Insufficient analysis of the need before committing to solutions Correct answer.
  2. Too few acceptance criteria per story
  3. Excessive stakeholder involvement in refinement
  4. Overly frequent retrospectives

Explanation

When output is healthy but outcomes miss the mark, the likely gap is analysis of the underlying need rather than delivery efficiency. Agile analysis emphasizes validating the problem before investing in a solution.

Question 49Agile Analysis

An organization wants analysis to remain adaptive across many teams sharing a product. Which governance approach best supports agile analysis?

  1. Standardizing one detailed template that all teams must complete identically
  2. Freezing the product backlog quarterly so teams stay synchronized
  3. Defining lightweight shared principles and a common backlog of needs while letting teams elaborate locally Correct answer.
  4. Requiring every team to obtain central approval for each backlog item

Explanation

Lightweight shared principles plus a common view of needs preserve alignment while allowing local elaboration suited to each team's context. This balances coordination with the adaptability agile analysis requires.

Question 50Agile Analysis

An agile BA observes that a backlog item keeps returning to refinement without ever being ready. Which analysis diagnosis is most plausible?

  1. The item is too small to estimate accurately
  2. The item lacks a numeric identifier
  3. The underlying need or scope is still unresolved, so the team cannot agree on conditions of satisfaction Correct answer.
  4. The team is refining too infrequently

Explanation

Repeated refinement without reaching readiness usually signals that the need, scope, or acceptance conditions remain unclear. Resolving the underlying ambiguity is what allows the item to become actionable.