Salesforce Business Analyst flashcards
Salesforce Business Analyst · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- As-Is Process Map
- Documents how work is performed today, capturing steps, handoffs, systems, and delays; used as baseline for gap analysis before designing Salesforce improvements.
- To-Be Process Map
- Describes the future-state workflow after Salesforce is implemented, showing steps, roles, and automation; used to validate design and confirm scope.
- Stakeholder Power/Interest Grid
- Classifies stakeholders by influence and interest; high-power high-interest groups get close management, while low-interest groups receive periodic updates.
- Persona
- A fictional archetype representing a user group's goals, tasks, and pain points; used to write user stories and design role-based experiences.
- Five Whys
- Iterative root-cause technique that repeatedly asks why a problem occurs until the underlying process or system cause is identified rather than a symptom.
- Customer Journey Map
- Visual sequence of a customer's touchpoints, actions, and emotions across channels; highlights moments of truth and pain points that Salesforce can improve.
- Success Criteria
- Measurable outcomes tied to business goals, such as reducing handle time by 20 percent, used to justify and evaluate the Salesforce solution.
- Art of the Possible Demo
- A capability demonstration using standard Salesforce features to spark ideas; it elicits requirements but must not be treated as a scope commitment.
- RACI Matrix
- Assigns Responsible, Accountable, Consulted, and Informed roles per deliverable; exactly one person is Accountable for each item.
- RAID Log
- Tracks Risks, Assumptions, Issues, and Dependencies with owners and status; reviewed at each project meeting to keep the team aligned.
- Decision Log
- Records each decision with date, owner, and rationale; prevents re-litigating settled choices and preserves context for later team members.
- MoSCoW Prioritization
- Sorts requirements into Must have, Should have, Could have, and Won't have this time; clarifies scope trade-offs with stakeholders.
- Communication Plan
- Defines audiences, messages, channels, frequency, and owners for project communication; ensures stakeholders receive timely, consistent information.
- Parking Lot
- A visible list of off-topic or deferred items captured during a workshop; revisited later so discussion stays on agenda without losing input.
- Sprint Review
- Ceremony where the team demonstrates completed work to stakeholders and collects feedback; distinct from a retrospective, which improves team process.
- Escalation Path
- Pre-agreed route and thresholds for raising blockers to sponsor level; prevents stalls and keeps decision authority explicit.
- User Story
- A requirement written as As a role, I want capability, so that benefit; focuses on user value and invites conversation rather than fixed specification.
- INVEST Criteria
- A checklist for good user stories: Independent, Negotiable, Valuable, Estimable, Small, and Testable; poor stories are split or rewritten.
- Acceptance Criteria
- Conditions a story must satisfy to be accepted; written as testable statements, often in Given-When-Then form, and used for user acceptance testing.
- Definition of Done
- A team-wide checklist of quality conditions every increment must meet, such as reviewed, tested, and documented; broader than single-story acceptance criteria.
- Nonfunctional Requirements
- Describe quality attributes such as performance, security, scalability, usability, and compliance rather than a specific feature behavior; they constrain the design.
- Traceability Matrix
- Maps each requirement to its business objective, design element, and test case; shows coverage and impact when a requirement changes.
- Given-When-Then
- A template for acceptance criteria: Given a context, When an action occurs, Then an expected outcome; it makes tests unambiguous.
- Declarative Configuration
- Building functionality with Salesforce point-and-click tools rather than code; preferred because it is faster to maintain and upgrade-safe.
- BABOK
- The IIBA Business Analysis Body of Knowledge; a standard describing knowledge areas, tasks, and techniques for business analysis practice.
- Gap Analysis
- Compares current-state capability with future-state requirements to identify what must change in process, people, data, or technology.
- Requirements Lifecycle
- Elicit, analyze, document, review, approve, baseline, and manage changes; after baselining, changes go through formal change control.
- Impact Analysis
- Assesses the effects of a proposed change on processes, users, data, integrations, reports, and training before approval, so scope and risk are understood.
- User Acceptance Testing
- Business users validate the solution against acceptance criteria in a test environment; formal sign-off is the gate before deployment.
- Elicitation Techniques
- Interviews, workshops, observation, surveys, document analysis, and prototyping; the BA selects techniques based on stakeholder availability and problem type.
- Solution Evaluation
- Post-implementation measurement of the solution against agreed success metrics to confirm benefits realization and identify follow-up improvements.
- Change Control
- Formal process for requesting, assessing, approving, and recording changes to baselined requirements; prevents unmanaged scope creep.