What are the two key document types that a consultant might be asked to produce for Public Sector Solutions implementation? Choose 2 answers

During a Salesforce Public Sector Solutions implementation, a consultant's primary role is to elicit, analyze, and document the client's needs to configure the system correctly. Functional Requirements Specifications (FRS) and User Stories are two standard, key artifacts used for this purpose. An FRS is a formal document common in traditional (waterfall) methodologies that details what the system must do. User Stories are the primary method for capturing requirements in Agile methodologies, describing a feature from an end-user's perspective. Both are central to defining the scope and functionality of the solution, making them core deliverables for a consultant.

A. Budget Plan: The budget plan is typically created and managed by the public sector agency's project manager or leadership, not the implementation consultant whose focus is on solution design and configuration.

C. Marketing Plan: A marketing plan is irrelevant as it focuses on promoting a product to external customers. A Public Sector Solutions implementation is an internal project to improve service delivery.

1. Salesforce Trailhead, Module: Consultant's Guide to Business Analysis, Unit: Document and Confirm Requirements. This unit explicitly details the methods for documenting requirements. It states, "User stories are the most common way to document requirements on an agile project... For more traditional projects, you might create a business requirements document (BRD) or a functional requirements document (FRD)." This directly supports that both User Stories (D) and Functional Requirements Specifications (B) are key documents a consultant produces.

2. Salesforce Trailhead, Module: Salesforce Agile Basics, Unit: Write and Review User Stories. This module establishes User Stories as a fundamental component of Salesforce implementations using an Agile framework. It defines a user story as "a way of describing a feature of a product from the perspective of the user," confirming its role as a primary requirements document.

3. Sommerville, I. (2016). Software Engineering (10th ed.). Pearson. Chapter 4, "Requirements Engineering," extensively covers different methods for documenting system requirements. Section 4.5, "Requirements specification," describes the Software Requirements Specification (SRS), of which an FRS is a key component. Section 4.2.3, "Scenarios and user stories," details the use of user stories in agile methods. This academic source validates both FRS and User Stories as standard, key document types in software implementation projects.