UX And Agile Methodologies

As a Business Analyst, How do you write your "Acceptance Criteria" effectively? Great requirements mean nothing if they can’t be tested. That’s where Acceptance Criteria (AC) come in! Clear AC ensures everyone—developers, testers, and stakeholders—is on the same page about what "done" looks like. But how do you write effective AC? Here’s my go-to approach: 1️⃣ Keep It Clear and Measurable Vague AC leads to confusion. Instead of: ❌ "The page should load quickly." Write: ✔️ "The page should load within 2 seconds on a 4G network." 2️⃣ Use the Given-When-Then Format This structure makes AC easy to understand and test: 🔹 Given – Precondition (What’s the setup?) 🔹 When – Action (What triggers it?) 🔹 Then – Expected outcome (What should happen?) Example: ✔️ Given the user is logged in, ✔️ When they enter an incorrect password three times, ✔️ Then their account should be locked for 10 minutes. 3️⃣ Cover Both Functional & Non-Functional Aspects It’s not just about features—consider security, performance, and usability. Example: ✔️ "The system should log out inactive users after 15 minutes for security." Why This Matters? - Developers know exactly what to build - Testers can validate if it works correctly - Stakeholders get what they expect How do you ensure your AC is rock solid? Share your thoughts! #businessanalyst #productowner

🚀 Salesforce Business Analyst Series 🚀 ✨ User Stories: The Blueprint for Success in Salesforce Projects ✨ As a Salesforce Business Analyst, one of our core responsibilities is translating business needs into actionable user stories. 🔹 It starts with a clear and concise user story — “As a [user], I want to [do something] so that [I achieve a value].” 🔹 Then comes the Acceptance Criteria, where we define exactly what success looks like. 🔹 Once the story and criteria are solid, it's ready to be handed off to developers and QA for build and testing. 💡 The clearer the user story and acceptance criteria, the closer the solution will align with the business requirements. A strong user story: ✅ Prevents rework ✅ Saves time in UAT ✅ Ensures developers and testers are aligned ✅ Builds trust with stakeholders 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ 🔍 So What Is a User Story? User stories are simple descriptions of a feature told from the user’s point of view. 📝 Format: As a < who >, I want < what > so that < why > 💡 Example: As a Sales Manager, I want opportunities over $100,000 to go through an approval process, So that I can review and approve them before they move to "Closed Won." 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ ✅ What Are Acceptance Criteria? Acceptance criteria are clear, pass/fail statements that define when a user story is done. They should be: 🔹 Easy to understand 🔹 Specific and testable 🔹 Focused on intent, not implementation 🛑 Bad: "A district manager can click an Approve/Disapprove button to approve a discounted product price." ✅ Good: "A district manager can approve or disapprove a discounted product price." 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ 〰️ ⚠️ Common Mistakes to Avoid When Writing User Stories 1- Not involving the project team in writing the story 🧨 Result: The story misses important perspectives and needs rewriting. 💡 How to avoid: Hold a story-writing session early and keep reviewing with the team. 2- User in the story is not clearly defined 🧩 Result: Developers won’t understand who the user is or what they need. 💡 How to avoid: Create clear user personas before writing stories. 3- The “why” focuses too much on features ⚙️ Result: Story becomes too technical and doesn’t reflect real user needs. 💡 How to avoid: Keep the user’s goals in mind and review stories for clarity. 4- Vague acceptance criteria ❓ Result: It’s hard to know when the story is complete or testable. 💡 How to avoid: Make sure criteria are clear, specific, and pass/fail. 5- Assigning stories without team discussion 🤷♂️ Result: Stories may be misunderstood, leading to incorrect results. 💡 How to avoid: Review stories as a team to align on goals and expectations. Let’s write user stories that make life easier for the entire project team! #SalesforceBASeries #BusinessAnalyst #BABA #Salesforce #Learning #ProjectManagement #SalesforceBA

How I write Acceptance Criteria (without them becoming vague or useless) One of the biggest causes of rework in delivery is acceptance criteria that are too vague. You’ll see AC like: → “Works as expected” → “User friendly” → “Loads quickly” → “Shows available times” The issue is simple: none of that is testable. So devs interpret it one way, testers interpret it another way, and sign-off turns into opinion. Here’s how I approach it 👇 1️⃣ Start with the user story AC are always linked to a story. If the story isn’t clear, the AC won’t be either. 2️⃣ Ask a small set of prompt questions (only use what’s relevant) → What does success look like? → What inputs does the user provide? → What rules/validations apply? → What can go wrong / no result scenarios? → What must be saved/retained/updated? 3️⃣ Write the AC in Given / When / Then → Given (setup) → When (action) → Then (observable outcome) The outcome? → Clear, testable AC the whole team can align on → Less guesswork in build + test → Cleaner sign-off If you found this useful, consider giving me a follow Matthew Thomas Holliday and reshare to your network ♻️ Want to build confidence in your BA career? Feeling stuck? Wanting extra guidance? Wanting to learn simple, repetable steps that will make you stand out?? That's exactly what our BA mentoring community helps you with (link in bio). #businessanalyst #acceptancecriteria

As a Business Analyst, Developer or Tester, have you faced frustration with not clear requirements in User Stories? It might happen for different reasons. Here are the most common ones and how to mitigate them. 1️⃣ Lack of Stakeholder Clarity ❌ Issue: stakeholders provide vague, conflicting, or incomplete requirements. ✅ Solution: 🔹 Conduct workshops, interviews, or surveys to extract clear requirements. 🔹 Use prototypes or wireframes to validate understanding. 🔹 Ask "Why?" repeatedly to uncover the real need (Root Cause Analysis). 2️⃣ Unclear Business Goals ❌ Issue: the business does not have a clear vision or measurable objectives. ✅ Solution: 🔹 Align user stories with business objectives and key metrics. 🔹 Use a Product Vision Board or Impact Mapping to clarify goals. 🔹 Ensure each story delivers business value (no unnecessary features). 3️⃣ Poorly Defined User Personas ❌ Issue: if user roles and behaviors are unclear, stories may lack relevance. ✅ Solution: 🔹 Define user personas with goals, pain points, and motivations. 🔹 Conduct user research (interviews, usability testing, analytics). 🔹 Ensure each story is written from a real user's perspective. 4️⃣ Missing Acceptance Criteria ❌ Issue: stories lack clear "Done" conditions, leading to misinterpretation. ✅ Solution: 🔹 Use Given-When-Then (Gherkin format) for testable acceptance criteria. 🔹 Collaborate with QA and Developers to define realistic conditions. 🔹 Ensure stories follow the INVEST principle (Independent, Negotiable, Valuable, Estimable, Small, Testable). 5️⃣ Overcomplicated or Ambiguous Language ❌ Issue: stories are too technical, too long, or filled with jargon. ✅ Solution: 🔹 Use simple, business-friendly language. 🔹 Avoid assumptions—clarify everything explicitly. 🔹 Keep stories small and focused on one objective. 6️⃣ Unstable or Changing Requirements ❌ Issue: continuous changes make it hard to finalize user stories. ✅ Solution: 🔹 Use a prioritized backlog (MoSCoW, WSJF scoring). 🔹 Have progressive elaboration—refine stories iteratively. 🔹 Maintain a traceability matrix to track changes and impacts. 7️⃣ Lack of Collaboration with the Development Team ❌ Issue: if BAs work in isolation, stories may be misunderstood or unfeasible. ✅ Solution: 🔹 Conduct refinement (grooming) sessions with developers and testers. 🔹 Encourage feedback loops (early validation & iteration). 🔹 Use story mapping to visualize end-to-end functionality. 8️⃣ Not Considering Edge Cases & Exceptions ❌ Issue: stories cover only the happy path, leading to surprises later. ✅ Solution: 🔹 Ask: "what could go wrong?" and include error scenarios. 🔹 Define alternate flows and edge cases in acceptance criteria. 🔹 Work with testers to include negative test scenarios. As a BA, Dev, or QA, it's important to collaborate with each other to have clear user stories! #businessanalysis #userstories #refinementsession

🚨 A Hard Truth: Acceptance Criteria and Definition of Done are NOT the same. Too many teams blur them together. Here’s the difference 👇 📝 Acceptance Criteria (AC) Unique to each Product Backlog Item. They describe what must be true so the Scrum Team and Product Owner share the same understanding of what delivering that PBI means. AC Example: As an online customer who forgot my password, I want to reset my login quickly, So that I can regain access to my account without calling customer support. Acceptance Criteria: - Forgot password link is visible on the login screen - Clicking the link prompts the customer to enter their registered email - A reset email is sent within 1 minute - Reset link expires in 10 minutes for security ✅ Definition of Done (DoD) Applies to every PBI and the Increment. It’s the Scrum Team’s commitment to quality and non-functional requirements. Examples: Codebase Quality - Code is written, peer-reviewed, and merged into the main branch - All unit, integration, and functional tests are automated and passing - Static code analysis shows no critical vulnerabilities or code smells - Security scanning (e.g., OWASP, dependency checks) shows no high-severity issues Performance & Reliability - Meets agreed non-functional requirements (e.g., page loads <1s, API responds <200ms) - Application monitored for errors, with no failing health checks - Backward compatibility verified (no breaking changes to existing consumers) Integration & Deployment - Integrated into the main branch without conflicts - Deployed to Production environment and verified - Deployment scripts and infrastructure-as-code updated where needed Documentation & Transparency - End-user documentation updated (help files, FAQs, release notes) - Technical documentation updated (API docs, architecture diagrams if changed) - Product Backlog updated to reflect new state of work Defect Management - No open critical or high-severity bugs - Medium/low-severity defects reviewed and either fixed or added to the Product Backlog 🔑 The distinction: AC = Do we have a shared understanding of the right thing to build for this PBI? DoD = Did we build it the right way, and does the whole Increment meet our quality standard? 👉 Think of it like a hotel: AC = checklist for one type of room. DoD = the safety, cleanliness, and quality standard for the entire hotel. 💬 What’s the biggest mix-up you’ve seen between AC and DoD?

Pickle Your Acceptance Criteria No, this post isn’t about soaking acceptance criteria in brine, but it is about Gherkins. Not the small cucumber, but the structured format for writing acceptance criteria (AC). No story should enter a sprint without clear AC. Otherwise, teams risk ambiguity, misaligned expectations, poor estimation, and inaccurate forecasts. AC clarify scope, facilitate splitting, and foster a shared understanding of what "done" means. What’s Gherkin? Gherkin is a plain-text format that makes AC clear, testable, and automation-friendly using simple keywords: Feature: Describes functionality Scenario: Defines a specific system behavior Given: Establishes preconditions When: Describes an action Then: Defines expected outcome And/But: Extends steps for readability Ex 1: Withdraw Cash w/ Sufficient Funds Story: As a bank customer, I want to withdraw cash from an ATM so I can access my funds. Gherkin AC: Feature: ATM Cash Withdrawal Scenario: Successful withdrawal w/ sufficient funds Given the user has a balance of $50 And they have inserted their debit card When they enter their PIN correctly And they request to withdraw $20 Then the ATM should dispense $20 And the balance should be updated to $30 This is a testable definition of a successful withdrawal. Ex 2: Failed Withdrawal of More Than Available Balance Story: As a bank customer, I want to be prevented from overdrawing my account so I don't incur fees Gherkin AC: Feature: ATM Cash Withdrawal Scenario: Withdrawal request exceeds balance Given the user has a balance of $50 And they have inserted their debit card When they enter their PIN correctly And they request to withdraw $80 Then the ATM should display an "Insufficient Funds" message And the transaction should be declined And no money should be dispensed This removes ambiguity about how the system should handle insufficient funds. Gherkin Tips 1) Each scenario should test one behavior. 2) Avoid jargon. Use familiar business stakeholder terms. 3) Avoid redundancy by using a Background section for shared steps: Feature: ATM Transactions Background: Given the user has inserted their debit card And they have entered their PIN correctly Scenario: Checking balance When they select "Check Balance" from the menu Then the ATM should display their current balance 4) Write objectively testable (pass/fail) criteria based on clear outcomes. 5) Review AC with team to eliminate misunderstandings before a story enters a sprint Don’t Settle For Vague AC Clear AC reduce ambiguity, improve estimation, and support accurate planning. The Gherkin format provides a structured way to clearly define behavior that benefits developers, testers, users, and stakeholders. Gherkins help foster a shared understanding across the team; reduce ambiguity, leading to better estimations and more accurate forecasts; create testable requirements that prevent defects; and facilitate test automation, reducing manual regression effort.