Define Acceptance Criteria
Acceptance criteria are a pivotal aspect of the solution development process, serving as a clear delineation of what must be met for the solution to be deemed as successfully developed. This criterion provides dual advantages:
Refinement of Requirements: The criteria give further insights that aid in honing the requirements.
Basis for Shared Understanding: It sets the stage for mutual understanding between stakeholders regarding the deliverables.
Acceptance Criteria in Different Contexts
In the context of portfolios or programs, the acceptance criteria usually remain at a more generalized level, focusing primarily on the broad objectives. The acceptance criteria here derive from several sources:
- Goals and Objectives: What the project or program aims to achieve.
- Key Performance Indicators (KPIs): Metrics that evaluate the performance of an activity.
- Project Metrics: Measures associated with the project's performance.
- Customer Metrics: Indicators related to customer satisfaction and feedback.
- Sales and Marketing Metrics: Measures related to sales performance and marketing effectiveness.
- Operational Metrics: Metrics that gauge the efficiency and effectiveness of operations.
These sources are elaborated upon in Section 6.5.3 of the Business Analysis for Practitioners: A Practice Guide.
Formats and Approaches
In adaptive methodologies, acceptance criteria commonly adopt a behavior-driven development format. However, the format is not set in stone and can vary based on consensus between stakeholders and developers.
Inputs
Analysis Approach
The Analysis Approach is a method or structured way to analyze the gathered data and information. This input provides guidance on how the requirements and other relevant product information should be analyzed, helping to ensure that the acceptance criteria are derived from valid and verifiable data sources.
Analysis Models
Analysis Models are representations of requirements or product information. These models could include flow diagrams, data models, or other types of diagrams that provide a visual representation. They serve as references for understanding requirements in a structured manner and help in deriving acceptance criteria that align with the requirements.
Requirements and Other Product Information
Requirements and other product information refer to the detailed descriptions of what the product should do and how it should perform. This input is crucial as the acceptance criteria are directly derived from these requirements ensuring that the end product meets the intended specifications.
Solution Evaluation Approach
The Solution Evaluation Approach is a structured method to assess the solution against the set requirements and acceptance criteria. By having this approach in place, one can ensure that the acceptance criteria set is both measurable and achievable within the solution's constraints.
Tools and Techniques
Behavior-Driven Development
Behavior-Driven Development (BDD) is a software development approach that promotes collaboration between developers, QA, and non-technical participants in a software project. BDD focuses on defining behaviors or actions of a system and then developing the software to meet those behaviors. This technique helps in defining clear acceptance criteria based on expected behaviors.
Definition of Done
The Definition of Done provides clear criteria for when a task or requirement is considered complete. It ensures consistency in understanding the completion state across stakeholders. When defining acceptance criteria, the Definition of Done helps in ensuring clarity and precision.
Story Elaboration
Story Elaboration is the process of breaking down user stories or requirements into detailed tasks or sub-tasks. This tool helps in understanding the depth of a requirement and ensures that all aspects are covered when setting acceptance criteria.
Outputs
Acceptance Criteria
Acceptance Criteria are the specific conditions that a product or feature must satisfy to be accepted by stakeholders. It acts as a checklist ensuring all requirements are met and provides a clear understanding of expectations to the development team.