The Salesforce development team is strictly following scrum to govern its releases. An executive trying to plan a vacation wants to know when work on the feature will begin so they can be available for additional implementation questions. After consulting with the product owner, the business analyst (BA) learns the team has decided to adopt Kanban instead for all future releases.What should the BA tell the executive?
Answer(s): C
The business analyst should tell the executive that work will begin when capacity becomes available. This is because Kanban is a development model that focuses on continuous delivery and flow of work, rather than fixed iterations or sprints. Kanban uses a visual board that shows the status of work items across different stages, such as backlog, in progress, done, etc. Work items are pulled from one stage to another when there is available capacity or demand, rather than according to a predefined schedule or plan. Work will not begin after executive approval is given or in the next sprint because these are concepts that are more relevant for other development models such as change set development or org development.
https://trailhead.salesforce.com/content/learn/modules/salesforce-business-analyst-certification- prep/user-acceptance https://trailhead.salesforce.com/content/learn/modules/agile-development- with-scrum
Cloud Kicks has moved into the quality assurance (QA) phase of Salesforce product configuration and extension. The QA team is now trying to confirm it has delivered value to stakeholders based on business requirements. The team is asking questions such as, "Did we build the right product?'' and "Did we build the product right?"Which element should the business analyst use to help the QA team validate that the product fulfilled the requirements without ambiguity?
The element that the business analyst should use to help the QA team validate that the product fulfilled the requirements without ambiguity is acceptance criteria. Acceptance criteria are statements that define the conditions that a product or feature must meet in order to be accepted by stakeholders or end users. They can help the QA team test the functionality based on specific scenarios or outcomes, and verify that it meets the expectations or needs of stakeholders or end users. Process maps are diagrams that show how a business process flows from start to end. They can help the QA team understand how a product or feature works in relation to a process, but not how to validate it without ambiguity. User stories are statements that capture a requirement or feature from an end user's perspective. They can help the QA team understand what needs to be done and why it matters, but not how to validate it without ambiguity.
https://trailhead.salesforce.com/content/learn/modules/salesforce-business-analyst-certification- prep/user-stories https://trailhead.salesforce.com/content/learn/modules/salesforce-business- analyst-certification-prep/user-acceptance
Northern Trail Outfitters (NTO) is undergoing a Salesforce implementation for Service Cloud. The busjpess analyst is currency working with the development team as they build features in the sandbox. NTO wants to test these features before the changes are deployed to the production environment.As part of the Application lifecycle Management (ALM) process, which three development models does Salesforce support?
Answer(s): A
The three development models that Salesforce supports as part of Application Lifecycle Management (ALM) process are Change Set Development, Org Development, and Package Development. Change Set Development is a model that uses change sets to deploy metadata changes from one org to another org. Org Development is a model that uses scratch orgs to create and test metadata changes in isolated environments before deploying them to other orgs. Package Development is a model that uses unlocked packages to bundle and distribute metadata changes across orgs as modular applications. Rapid Application Development, Flow Builder, and Salesforce DX are not development models supported by Salesforce as part of ALM process.
https://trailhead.salesforce.com/content/learn/modules/salesforce-business-analyst-certification- prep/user-acceptance https://trailhead.salesforce.com/en/content/learn/modules/application- lifecycle-and-development-models
The business analyst (BA) at Northern Trail Outfitters is writing user stories about a Case creation feature within Service Cloud for an upcoming sprint. This feature overlaps with another feature that is being developed in the current sprint. The BA is working with the technical team to identify metadata dependencies across features to prevent overwriting before the release.What should the BA use?
The business analyst (BA) at Universal Containers (UC) wants to understand why UC failed to meet a deployment date for its product go live while following the Agile process. According to the BA's research, the developers lacked a sense of the work in progress and the intended goal of that work, and the QA team was unable to clearly test the functionality based on a given persona.Which step should the BA take next?
The next step that the business analyst should take is to review the user stories to ensure they are small, testable, and valuable. User stories are statements that capture a requirement or feature from an end user's perspective. They should be small enough to be completed within a sprint, testable enough to be verified by acceptance criteria, and valuable enough to deliver benefits or outcomes for end users. Reviewing user stories can help UC understand why development and testing took more time than expected, and how to improve them for future sprints.Creating a SWOT (Strengths, Weaknesses, Opportunities, Threats) analysis to understand why development and testing took more time is not a good next step because it is a strategic tool that evaluates the internal and external factors affecting a project or initiative, not a tactical tool that evaluates the quality or effectiveness of user stories. Moving the deployment date out so the teams have more time to work is not a good next step because it does not address the root cause of why development and testing took more time, and it may affect the project scope or budget.
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.