Development Support and User Acceptance12% of the exam
Supporting the build and validating delivery
What the BA does while the solution is built: clarifying story intent and updating acceptance criteria, working the Scrum meetings, accepting or returning stories against their criteria, protecting existing functionality, and preparing the evidence, training and communications the business needs before release.
Support and validate project delivery to ensure the solution meets the requirements.
~8 min read · 18 practice questions ·
What the exam expects
- Act as the liaison during the build: clarify intent with the stakeholder, settle developer-versus-stakeholder readings, and fold the answer back into the story and its acceptance criteria.
- Use the Scrum meetings (backlog refinement, daily stand-up, sprint demo) to keep stories ready and unblocked.
- Accept, split or return a delivered story by checking it against its acceptance criteria, and route new requests through prioritization rather than into the sprint.
- Protect existing functionality with regression testing, and confirm the technology team's testing is done before business testers start.
- Assemble delivery evidence and release-readiness material: test results against criteria, outstanding defects, documentation and training built from the future-state process, and timely communication of deferrals.
Key terms:
- Acceptance criteria: pass/fail statements that specify when a user story is fulfilled.
- Definition of done: the completion standard the team agrees for all its work.
- Backlog refinement: the meeting where upcoming backlog items are clarified and made ready.
- Regression: a change that negatively impacts existing functionality.
- Product owner: the Scrum role that defines, prioritizes and approves the team's work.
Key facts
Acceptance criteria
- Detail
- Pass/fail statements that specify when a story is fulfilled
Backlog refinement
- Detail
- Breaks work into smaller chunks and drafts conditions of satisfaction
Daily stand-up
- Detail
- Brief daily sync; visibility on daily progress
Sprint demo
- Detail
- Finished work presented to product owners and stakeholders
Product owner
- Detail
- Defines, prioritizes and approves the team's work
Definition of done
- Detail
- Decided together by the team
Regression
- Detail
- A change that negatively impacts existing functionality
Test order
- Detail
- Technology team QA first, then UAT in a sandbox
Training
- Detail
- The BA builds training material for the implemented solution
Sources for this section (6)
- Construct a User Storytrailhead.salesforce.com (opens in a new tab)
- Implement Scrumtrailhead.salesforce.com (opens in a new tab)
- Learn About Scrumtrailhead.salesforce.com (opens in a new tab)
- Test New Featurestrailhead.salesforce.com (opens in a new tab)
- Learn About UATtrailhead.salesforce.com (opens in a new tab)
- BA Roletrailhead.salesforce.com (opens in a new tab)
- Why should the BA update the story and its acceptance criteria after clarifying a developer's question?
- When does UAT start relative to QA?
- What happens in backlog refinement?
- Who approves adding new work to the team's plan?
- Why add regression tests when changing a shared flow?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Business Analyst pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 22 lessons of the Business Analyst guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (18 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams