You ate in a backlog refinement meeting with the development team and the product owner. You review a story for an integration Involving a third-party system. A payload will be sent from the Appian system through the integration to the third-party system. The story is 21 points on a Fibonacci scale, and requires development from your Appian learn, as well as the technical resources from the third-party system. This item is crucial to your project s success.
What are the two recommended steps to ensure this story can be developed effectively?
Correct Answer: C,D
Explanation
To ensure that this story can be developed effectively, you should take two recommended steps:
* Maintain a communication schedule with the third-party resources. Communication is key when working on an integration involving a third-party system, as it can help to clarify the requirements, expectations, and dependencies of both parties. By maintaining a communication schedule, you can ensure that you have regular and timely updates on the progress, issues, and feedback of the integration.
You can also use communication tools, such as email, chat, or video conferencing, to facilitate the communication and collaboration between your Appian team and the third-party resources.
* Break down the item into smaller stories. Breaking down a large and complex story into smaller and simpler stories can help to make the development process more manageable and efficient. By breaking down the item into smaller stories, you can reduce the scope and complexity of each story, and focus on delivering one feature or functionality at a time. You can also prioritize and assign the stories to different developers, and track their status and completion more easily.
The other options are not as effective. Option A, acquiring testing steps from QA resources, is not a step to ensure that the story can be developed effectively, but rather a step to ensure that the story can be tested effectively. Option B, identifying subject matter experts (SMEs) to perform user acceptance testing (UAT), is also not a step to ensure that the story can be developed effectively, but rather a step to ensure that the story can be validated effectively. Option E, adding a view that joins the customer data to the data used in calculation, is not a step to ensure that the story can be developed effectively, but rather a design decision that may or may not be appropriate for the integration.