You are the project lead for an Appian project with a supportive product owner and complex business requirements involving a customer management system. Each week, you notice the product owner becoming more irritated and not devoting as much time to the project, resulting in tickets becoming delayed due to a lack of involvement. Which two types of meetings should you schedule to address this issue?

• A. A meeting with the sponsor to discuss the product owner's performance and request a replacement.
• B. A risk management meeting with your program manager to escalate the delayed tickets.
• C. A sprint retrospective with the product owner and development team to discuss team performance.
• D. An additional daily stand-up meeting to ensure you have more of the product owner's time.

You are the lead developer for an Appian project, in a backlog refinement meeting. You are presented with the following user story:
"As a restaurant customer, I need to be able to place my food order online to avoid waiting in line for takeout." Which two functional acceptance criteria would you consider 'good'?

• A. The system must handle up to 500 unique orders per day.
• B. The user will click Save, and the order information will be saved in the ORDER table and have audit history.
• C. The user cannot submit the form without filling out all required fields.
• D. The user will receive an email notification when their order is completed.

While working on an application, you have identified oddities and breaks in some of your components. How can you guarantee that this mistake does not happen again in the future?

• A. Provide Appian developers with the "Designer" permissions role within Appian. Ensure that they have only basic user rights and assign them the permissions to administer their application.
• B. Design and communicate a best practice that dictates designers only work within the confines of their own application.
• C. Ensure that the application administrator group only has designers from that application's team.
• D. Create a best practice that enforces a peer review of the deletion of any components within the application.

Your client's customer management application is finally released to Production. After a few weeks of small enhancements and patches, the client is ready to build their next application. The new application will leverage customer information from the first application to allow the client to launch targeted campaigns for select customers in order to increase sales. As part of the first application, your team had built a section to display key customer information such as their name, address, phone number, how long they have been a customer, etc. A similar section will be needed on the campaign record you are building. One of your developers shows you the new object they are working on for the new application and asks you to review it as they are running into a few issues. What feedback should you give?

• A. Create a duplicate version of that section designed for the campaign record.
• B. Point the developer to the relevant areas in the documentation or Appian Community where they can find more information on the issues they are running into.
• C. Ask the developer to convert the original customer section into a shared object so it can be used by the new application.
• D. Provide guidance to the developer on how to address the issues so that they can proceed with their work.