Checklist progress
0/102Learned
Business Analyst
Study Checklist
Checklist progress
0/102Learned
Determine business strategies, goals, initiatives, and challenges to define the scope of a Salesforce project or business initiative.
0/10
Business strategy versus goals, initiatives, and scope
Learn this conceptStrategic drivers that define Salesforce project scope
Learn this conceptStakeholders whose strategies and goals bound scope
Learn this conceptDiscovery questioning for goals, initiatives, and challenges
Learn this conceptChallenge framing and right-sized initiative scope
Learn this conceptObjectives, success criteria, assumptions, and constraints
Learn this conceptOrganizational alignment frameworks for Salesforce scope
Learn this conceptWhen a Salesforce request conflicts with strategy
Learn this conceptProduct roadmaps in customer discovery
Learn this conceptDriving organizational change in Salesforce initiatives
Learn this conceptDiscover how a customer is leveraging existing products to establish the current state.
0/5
Understand and explain Business Analyst roles and responsibilities in different phases of the implementation lifecycle.
0/6
Apply the implementation lifecycle for planning business analysis activities.
0/3
Analyze the customer's Salesforce environment(s) to identify opportunities and constraints.
0/6
Demonstrate knowledge of Salesforce capabilities, align them with business needs, and recommend potential solutions.
0/5
Prepare for the Exam
Study Community
Ask questions and get the latest info from other Business Analyst studiers.
During information discovery, a business analyst gathers as much information as possible by asking every who, what, where, why, when, and how question about the work, because without the right information you cannot form the best conclusions or bring a project to fruition. Strategy analysis starts by identifying the business need, which is of strategic or tactical importance, then uses that need to observe the current state, define future and transition states, and recommend the highest-value approach, including the work or scope required. Much of that information lives in stakeholders’ and end users’ minds rather than in documents, so the analyst elicits it through interviews, observation, process mapping, and related techniques.