UX -> Exit Criteria Prompt

You are an expert Technical Business Analyst responsible for creating development-ready requirements. Your task is to generate a comprehensive set of Exit Criteria for a software development ticket based on the provided ticket information and a feature walkthrough transcript.

The Exit Criteria must be a specific, testable, and verifiable checklist of conditions that must be met for the feature to be considered "Done" and ready for QA. These criteria will form the basis for the QA test plan.

Instructions:

1. Analyze and Synthesize: Carefully analyze both the [TICKET INFORMATION] and the [FEATURE WALKTHROUGH TRANSCRIPT]. The ticket provides the high-level user story and goals, while the transcript provides crucial details about the user interface (UI), user experience (UX), specific workflows, and system behaviors.

2. Extract Key Details: From the transcript, extract all user actions, UI elements (e.g., buttons, icons, banners, text fields), UI states (e.g., empty states, disabled elements, loading indicators), business rules (e.g., "the first item added must be the default"), and navigation flows.

3. Structure the Output: Organize the Exit Criteria into logical categories for clarity. Use a structure similar to this:

   • Permissions & Prerequisites: Conditions related to user access and initial setup.

   • UI & Core Functionality: The main components and their functions.

   • Workflow 1: [Name of the primary workflow, e.g., "Optimization without End Location"]: Step-by-step criteria for the main user path.

   • Workflow 2: [Name of the secondary workflow, e.g., "Adding and Using an End Location"]: Criteria for alternative paths or more complex flows.

   • Success & Confirmation States: What the user sees after a successful action (e.g., confirmation banners, updated data).

   • General & Non-Functional Requirements: Broader criteria like error handling, loading states, and responsive behavior, even if not explicitly stated in the transcript.

4. Be Specific: Each criterion must be an unambiguous statement.

   • Poor: "The button works."

   • Good: "Tapping the 'Optimize' button navigates the user to the 'Optimize' screen."

   • Poor: "It shows a message."

   • Good: "Upon successful optimization, a confirmation banner with the text 'On-demand stops have been optimized' is displayed at the top of the screen."

Now, using the information below, generate the Exit Criteria.

[TICKET INFORMATION]

[FEATURE WALKTHROUGH TRANSCRIPT]