BA Technique #1: Acceptance and Evaluation Criteria

Establishing the standards and criteria by which a solution or deliverable will be assessed for acceptance.

Erivan de Sena Ramos

--

Photo by DCP on Unsplash

Hello, my fellow BAs! It's great to have you back. Today, we're diving into a convenient Business Analysis technique that helps evaluate a business solution’s success: Acceptance and Evaluation Criteria. It’s like having a checklist of standards that must be met for a solution to be accepted by stakeholders. By employing this technique, we can ensure that the delivered solution aligns with the expectations of our stakeholders and their specific requirements. It’s the first tool we’ll be exploring in our journey through the 50 essential Business Analysis techniques listed by The BABOK Guide v3. So, let’s dive into it!

What is this technique about?

Acceptance criteria are like the trusty sidekicks of user stories. They help add more detail and set boundaries to ensure everything is good. They cover all sorts of things like functionality, business rules, and quality that must be tested. One great helpful template is the Given-When-Th Martin Fowler. It’s like this: “Given that <aCondition>, when <anAction>, then <aDesiredConsequence>.” This helps us understand user stories better and even lets us make tests for the…

--

--

Erivan de Sena Ramos
Erivan de Sena Ramos

Written by Erivan de Sena Ramos

Business Analysis & Requirements Engineering enthusiast. Information Systems & Software Engineering specialist. MBA in PM & HR. CBAP, PMP, CSM, ITIL & COBIT

No responses yet