Agile Business Analysis Agile Methodology 4 — Questions and Answers
Question 1: What is the primary difference between a 'spike' and a regular user story in Agile?
- A spike is a user story with extra-high business value
- A spike is a time-boxed research task to reduce uncertainty, not to deliver shippable functionality (Correct answer)
- A spike is a bug fix that must be resolved before the sprint can start
- A spike refers to an unexpected increase in team velocity
Correct answer: A spike is a time-boxed research task to reduce uncertainty, not to deliver shippable functionality
A spike is a time-boxed investigation or experiment whose output is knowledge rather than a deliverable increment, helping the team estimate or design effectively.
Question 2: In Agile business analysis, 'acceptance criteria' BEST serve which purpose?
- Specifying the technology stack to be used for implementation
- Defining the conditions that must be met for a story to be considered done (Correct answer)
- Setting the team's velocity target for the sprint
- Documenting the risk register for the project sponsor
Correct answer: Defining the conditions that must be met for a story to be considered done
Acceptance criteria establish clear, testable conditions agreed upon by the team and Product Owner that determine when a user story is complete.
Question 3: Which Agile framework uses the concept of a 'Kanban board' combined with explicit policies and feedback loops rather than fixed iterations?
- Scrum
- Extreme Programming (XP)
- Kanban method (Correct answer)
- Crystal
Correct answer: Kanban method
The Kanban method relies on visualizing workflow, limiting WIP, and managing flow using explicit policies; it does not prescribe fixed sprint lengths or sprint ceremonies.
Question 4: A business analyst wants to understand WHY a feature is needed before writing user stories. Which tool BEST supports this goal?
- Burndown chart
- Impact map (Correct answer)
- Velocity chart
- Release roadmap
Correct answer: Impact map
An impact map links business goals to actors, impacts, and deliverables, ensuring the team understands the 'why' before deciding on the 'what'.
Question 5: What is the key characteristic of an 'Agile Release Train' (ART) in SAFe?
- A single cross-functional team of 5–9 members aligned to one product area
- A long-lived team of teams (50–125 people) that delivers value on a shared PI cadence (Correct answer)
- A quarterly governance meeting for executive stakeholders
- A deployment pipeline that automates releases to production
Correct answer: A long-lived team of teams (50–125 people) that delivers value on a shared PI cadence
An ART is a stable, long-lived team-of-teams structure in SAFe that aligns multiple Agile teams around a common mission and delivers value every PI.
Question 6: During retrospectives, a Scrum team repeatedly identifies 'unclear requirements' as a problem. As a business analyst, what is the BEST systemic fix?
- Replace the Product Owner with a more experienced one
- Establish a formal backlog refinement cadence with the whole team (Correct answer)
- Have the Scrum Master write the requirements instead
- Document all requirements in a detailed BRD before the sprint
Correct answer: Establish a formal backlog refinement cadence with the whole team
Regular backlog refinement sessions (grooming) allow the business analyst, Product Owner, and team to clarify, split, and estimate stories before they enter a sprint.
Question 7: What does 'inspect and adapt' mean in the context of Agile frameworks?
- Running automated tests after every code commit to inspect quality
- Regularly reviewing progress and outcomes to make timely adjustments to process or product (Correct answer)
- Having the Scrum Master inspect each team member's work daily
- Adapting the sprint length based on how much work remains
Correct answer: Regularly reviewing progress and outcomes to make timely adjustments to process or product
'Inspect and adapt' is a core Agile empirical principle where teams frequently examine their work and process, then make informed adjustments to improve.
What is the primary difference between a 'spike' and a regular user story in Agile?