Universal Containers is developing a new recruitment app using Service Cloud. The project team has started writing user stories including:"As a human resources (HR) manager, I need to document the progress of a candidate's submission so I can manage the candidate's application throughout the recruiting process." What is one definition of done for this user story?
Answer(s): B
A definition of done is a set of criteria that determines when a user story is completed and ready for deployment. It typically includes technical, functional, and quality aspects of the user story, such as code quality, unit testing, documentation, performance, security, and usability. One possible definition of done for this user story is "The Candidate Status field can be updated." This criterion checks if the functionality of updating the candidate's submission progress is working as expected and meets the user's need.
https://trailhead.salesforce.com/en/content/learn/modules/business-analysis-user-stories/define- done
The Cloud Kicks business analyst (BA) is frustrated because the requirements tracking spreadsheet is often incomplete or out-of-sync for the Slack transition project. The development team has recommended that the BA use a DevOps tool as an alternative. What are the benefits of using a DevOps tool in this situation?
Answer(s): C
This answer states that using a DevOps tool can help to track changes in real time and provide a single source of truth as the benefits of using a DevOps tool in this situation where the requirements tracking spreadsheet is often incomplete or out-of-sync for the Slack transition project. A DevOps tool is a software application that supports the collaboration and automation of development and operations teams, such as Git, Jira, or Azure DevOps. A DevOps tool can help to track changes in real time by synchronizing the code changes, user stories, tasks, and bugs across different environments and branches. A DevOps tool can also help to provide a single source of truth by storing and managing all the project artifacts, such as requirements, code, tests, and documentation, in one centralized location that is accessible and visible to all project team members.
https://trailhead.salesforce.com/en/content/learn/modules/git-and-git-hub-basics/work-with-teams
Universal Containers has scheduled a meeting with stakeholders, business analysts (BAs), and technical resources to review user stories. A BA reviews the user stories in advance of the meeting and notices that some best practices have been ignored. The first user story is focused on escalating cases in Service Cloud:"The customer service agent needs the ability to escalate a case so they can assign high-risk cases to tier 2 support for faster resolution."Acceptance Criteria:1. Add permission set2. Users can escalate cases3. Create fields on the Case object4. ReportsWhich best practice was ignored?
A use case is a type of documentation that describes how a user interacts with a system to achieve a specific goal. It is written from the user's point of view and follows a standard format of "A [user role] wants to [goal] by [steps]". A use case helps to capture the user's needs and expectations from the system and provides a basis for developing test cases and acceptance criteria. A BA should use use cases to document how users will interact with the system and what outcomes they expect from it.
https://trailhead.salesforce.com/en/content/learn/modules/business-analysis- functional-requirements/write-use-casesThis answer points out that the previous VP's requirements may differ from those of the new executive as the largest risk with this approach of using the inherited requirements in lieu of a traditional discovery process for a Sales Cloud implementation. Requirements are statements that describe what a solution must do or have to meet the needs and expectations of the stakeholders or users. Requirements may change over time due to various factors, such as business goals, market trends, customer feedback, or stakeholder preferences. Using the previous VP's requirements without validating them with the new executive may result in a solution that does not align with their vision, strategy, or value proposition.https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick- look/use-user-stories-to-capture-requirements
The sales team at Cloud Kicks is rolling out a new sales methodology. To incorporate the requested changes, the business analyst working with the technical team identifies several integrations that touch the Opportunity object and could be impacted by the changes. The project manager wants the solution to include unit testing, code reviews, and functional testing. What does the project team need to agree upon to ensure the work is ready to be deployed?
The project team needs to agree upon a definition of done to ensure that the work is ready to be deployed. A definition of done is a set of criteria that determines when a user story is completed and ready for deployment. It typically includes technical, functional, and quality aspects of the user story, such as code quality, unit testing, documentation, performance, security, and usability. A definition of done helps to ensure that the work meets the expected standards and quality, satisfies the user's needs and expectations, and aligns with the project goals and scope.
The Salesforce delivery team at Cloud Kicks consistently has user stories that developers start but are unable to complete during each sprint. During the most recent retrospective, the development team expressed that they are running out of time to complete the stories. The team used the INVEST checklist to diagnose why these stories are incomplete at the end of the sprint. Which checklist item is the most likely reason why the stories are incomplete at the close of the sprint?
The checklist item that is the most likely reason why the stories are incomplete at the close of the sprint is small. Small means that a user story should be simple and concise, and it should be able to be completed within a single sprint by a single developer or a small team. A user story that is too large or complex may be difficult to estimate, prioritize, test, or deliver within the sprint timeframe. A user story that is too small may be trivial, redundant, or irrelevant to the project goals. A user story that is not small enough may need to be broken down into smaller and more manageable chunks.
https://trailhead.salesforce.com/content/learn/modules/user-story-creation/write-user- stories
Post your Comments and Discuss Salesforce Certified Business Analyst exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the Certified Business Analyst content, but please register or login to continue.