Let’s continue with part 2 of 3 of the “usual suspects” for the technical deliverables in Salesforce discovery projects.
3. User Flows
Purpose:
- Understand the different actors and their interconnectivity and dependency
- Visualize the steps and easy-of-use required from each actor
- Help make decisions about the scope during the implementation stage
Usage:
- Serve as guidelines for the broader context of user experience (UX)
- Are a critical input for contextualizing the user stories
- Establish a baseline understanding of the “completeness” criteria for features within the application
Required:
- Swimlanes to divide logic per actor
- Transitions between the various actor
- Major steps taken by each user and by the system
- Decision points along the way
Example:
4. Salesforce Security Model
Purpose:
- An artifact containing a list of user profiles and permissions, and the data each of them is able to interact with
Usage:
- To ensure users only have access to what they need to see and nothing more
- To create user stories that meet the security requirements outlined
Required:
- A table of profiles, permission sets, and objects
- An indicator of which action is allowed for the profile and permission set
Example:
Category:
Salesforce