Part 1: Planning and Analysis – BRD/Prioritized Product Backlog

In this part, you will learn about planning and analysis activities, starting with ways to identify the right sources of requirements and use elicitation techniques to understand business needs by engaging the right stakeholders. You will learn how to utilize tacit business analysis and Salesforce system analysis skills to rank and stack all requirements, and communicate and get buy-in from all stakeholders. Finally, you will document all your prioritized requirements in a business requirement document artifact. You will also learn how to create a roadmap to deliver a set of high-level requirements.

We will address some of the key challenges faced during this phase:

• Not being able to identify the right requirements, resulting in delivering unnecessary nice-to-have features without adding any business value
• Due to a lack of requirements or product backlog prioritization, projects not delivering the right solutions as requirements are accepted on a first-come, first-served basis, or the loudest voice gets prioritized
• Going all in rather than defining a clear Salesforce roadmap
• Not assessing the dependencies and integration impacts on concurrent Salesforce projects
• No clear understanding of what the current state process looks like or what the future proposed state process should be

The following chapters will be covered under this part:

• Chapter 1, Identifying Requirements
• Chapter 2, Elicitation and Document Requirements
• Chapter 3, Prioritizing Requirements
• Chapter 4, Process Flows – “As-Is” versus “To-Be”
• Chapter 5, Business Requirements Document