• Cert++
  • Practice
  • Certle
  • Review
  • Tracks
  • Checklist
  • Guides
  • Upgrade
Cert++
  1. Home
  3. Business Analyst

Business Analyst

Checklist progress

0/102Learned

Business Analyst

Study Checklist

  • Platform Administrator
  • Platform App Builder
  • Platform Foundations
  • Platform Developer
  • Platform Administrator II
  • Agentforce Sales Consultant
  • Agentforce Service Consultant
  • Platform Data Architect
  • Platform Development Lifecycle and Deployment Architect
  • Platform Identity and Access Management Architect
  • Platform Integration Architect
  • Platform Sharing and Visibility Architect
  • Heroku Architect
  • B2C Solution Architect
  • Experience Cloud Consultant
  • Agentforce Field Service and Operations Consultant
  • Agentforce Nonprofit Consultant
  • Data 360 Consultant
  • Omnistudio Consultant
  • CRM Analytics and Einstein Discovery Consultant
  • Platform User Experience Designer
  • Platform Strategy Designer
  • B2C Commerce Developer
  • JavaScript Developer
  • Omnistudio Developer
  • Platform Developer II
  • Marketing Cloud Engagement Administrator
  • Marketing Cloud Engagement Specialist
  • Marketing Cloud Engagement Consultant
  • Agentforce Sales Foundations
  • Business Analyst
  • Marketing Cloud Engagement Developer
  • Marketing Cloud Engagement Foundations
  • Agentforce Specialist
  • Agentforce Life Sciences Consultant
  • B2B Commerce Administrator AP
  • B2B Commerce Developer AP
  • Agentforce Consumer Goods AP
  • Agentforce Financial Services AP
  • Agentforce Health AP
  • Agentforce Manufacturing AP
  • MuleSoft Integration Foundations
  • MuleSoft Developer
  • MuleSoft Developer II
  • MuleSoft Platform Integration Architect
  • MuleSoft Platform Architect
  • Tableau Desktop Foundations
  • Tableau Data Analyst
  • Tableau Consultant
  • Tableau Server Administrator
  • Tableau Architect

Checklist progress

0/102Learned

  • Business strategy versus goals, initiatives, and scope
  • Strategic drivers that define Salesforce project scope
  • Stakeholders whose strategies and goals bound scope
  • Discovery questioning for goals, initiatives, and challenges
  • Challenge framing and right-sized initiative scope
  • Objectives, success criteria, assumptions, and constraints
  • Organizational alignment frameworks for Salesforce scope
  • When a Salesforce request conflicts with strategy
  • Product roadmaps in customer discovery
  • Driving organizational change in Salesforce initiatives
  • Current state as a prerequisite to future-state design
  • Existing product usage and benefits in the current state
  • Empathetic research methods for current-state discovery
  • Customer language during current-state discovery
  • Journey mapping for current product experience
  • Business Analyst as liaison between business and technical teams
  • Salesforce Business Analyst versus Salesforce Admin
  • Business Analyst responsibilities versus adjacent delivery roles
  • Business Analyst responsibilities across implementation lifecycle phases
  • SDLC methodology implications for the Business Analyst role
  • Salesforce release notes in the Business Analyst role
  • Planning BA activities across the implementation lifecycle
  • Implementation work streams for business analysis
  • Application Lifecycle Management for BA planning
  • Production, sandbox, and multi-org landscape
  • Edition and license constraints in the customer org
  • Unused licensed Salesforce capabilities as opportunities
  • Existing customizations and technical debt as constraints
  • Salesforce Optimizer for org health insights
  • Whole-organization impacts in a shared Salesforce org
  • Salesforce capability alignment with business needs
  • Customer 360 versus single-cloud solution recommendations
  • Native Salesforce versus AppExchange for a business need
  • Salesforce features versus custom development recommendations
  • Ideation and prototyping for Salesforce solution options
  • Stakeholder-based discovery activity planning
  • Determining information needs in discovery
  • Customer industry language in discovery planning
  • Identifying key stakeholders
  • Trusted advisor relationships with stakeholders
  • Liaison between business and technical teams
  • Communication with business and technical stakeholders
  • Salesforce adoption strategies for user success
  • Business-needs elicitation techniques
  • Whiteboarding to elicit business needs
  • Journey mapping to elicit experience needs
  • Process-design sessions to elicit business needs
  • Current-state versus future-state design
  • Salesforce features and best practices in future-state design
  • Technical debt as a constraint on future-state design
  • Stakeholder agreement on future-state design
  • Solution roadmaps as agreed future-state design
  • Facilitating consensus on competing stakeholder priorities
  • Prioritization methods for competing stakeholder requests
  • Negotiating stakeholder conflict toward consensus
  • Stakeholder sign-off after priority alignment
  • Agile collaboration with stakeholders
  • Defining the scope of a process map
  • Hierarchical process mapping and drill-down
  • Capability maps versus process maps
  • Purpose of business process mapping
  • Questions to define, engage, and identify a process
  • Current-state process mapping to elicit requirements
  • Future-state process visualization with stakeholders
  • Hierarchical process maps for stakeholder levels
  • Functional ownership on process maps
  • Universal Process Notation versus flowcharts
  • Version-controlled repositories for process maps
  • Governance of agreed future-state processes
  • Scope versus requirements versus user stories
  • Well-defined requirements
  • Aligning requirements to business needs
  • Pain points as sources of requirements
  • Identifying new requirements for future state
  • Validating existing requirements with stakeholders
  • Prioritizing requirements with stakeholders
  • Requirement dependencies
  • Requirements across the implementation lifecycle
  • Whiteboarding during requirements meetings
  • Scrum versus Kanban workflows
  • Version-controlled repository for requirements
  • Change sets versus version control for requirements

Understand the components of a user story to perform thorough analysis.

0/6

  • Purpose of user stories in Agile analysis
  • User story who, what, and why
  • Acceptance criteria as a story component
  • INVEST criteria for user stories
  • Common mistakes when writing user stories
  • User story writing workshops

Demonstrate how to write acceptance criteria that convey the requirements and are ready for development.

0/2

Writing development-ready acceptance criteria

Learn this concept
Unseen

Acceptance criteria versus definition of done

Learn this concept
Unseen

Document user stories in a version controlled repository to manage scope.

0/1

  • Version-controlled repository for user stories
  • Validating project delivery against requirements
  • Requirement clarification with developers during delivery
  • Purpose of user acceptance testing
  • Business analyst role in user acceptance testing
  • User acceptance test plan
  • Selecting UAT testers
  • UAT test scripts
  • Guiding UAT and managing results
  • Stakeholder sign-off
  • Go/no-go release decisions
  • Compliance considerations in UAT

Prepare for the Exam

Play Today's Certle
Back to track

Study Community

Ask questions and get the latest info from other Business Analyst studiers.

Go to Discord

Acceptance criteria versus definition of done

Explainer

Learn More

Practice Question

Keep going

Next conceptVersion-controlled repository for user stories

Checklist progress

0/102 (0%)

0 of 102 concepts learned

Tip: You can filter concepts by status.

Prepare for the Exam

Play Today's Certle
Back to track

Study Community

Ask questions and get the latest info from other Business Analyst studiers.

Go to Discord

Explainer

Acceptance criteria are pass/fail statements added to a user story that specify the conditions under which that story is fulfilled, giving the project team an agreed gauge of success. Definition of done is a separate team decision: Salesforce Scrum teams decide together on work items, working agreements, definition of done, and roles, and everyone honors those decisions. Criteria prove whether this user story is fulfilled; definition of done is a shared agreement the team chooses and then sticks to.

Core information
  • When a project group sees the same problem from different angles, it still needs one agreed gauge of success, otherwise known as acceptance criteria: a set of statements, each with a clear pass/fail result, added to a user story to specify the conditions under which the story is fulfilled.
More details and nuances
  • If acceptance criteria are too vague, there is no reliable way to measure when the user story is successfully completed. Keep every criterion independent and true or false, and write them with the project team so they align with the user's goal.