Business Analyst
Turning intent into requirements that are specific, testable, and traceable.
Foundations
What a Business Analyst actually does
The Business Analyst turns intent into requirements a team can build and test. The real shape of the role, what it produces, and where it goes wrong.
What a QA Engineer actually does
QA is not the last step before release. It is the discipline of deciding what evidence would prove a requirement was met, and gathering it.
Practices
Acceptance criteria examples and template
Acceptance criteria examples for login, payments and refunds: weak versus testable criteria, failure, boundary and permission cases, and a reusable template.
How to decompose an epic into user stories
How to break down an epic into user stories that ship alone: the cuts that fail, story splitting examples, and how to turn a PRD into features and stories.
Release readiness checklist and template
A release readiness checklist with owners, evidence and stop signals, test exit criteria, UAT sign-off, and a go or no-go decision record template.
Requirement quality checklist and examples
A requirement quality checklist with before-and-after examples of ambiguous, incomplete and untestable requirements, how to find gaps, and a review decision.
Requirements change impact analysis
How to analyse the impact of a requirement change: what to trace, which tests to review, how to reassess earlier results, plus a worked example and a template.
Requirements gathering tools and checklist
Requirements gathering tools grouped by the job they do, a checklist and question bank for each stage, and a handoff template for decisions and open questions.
Requirements traceability matrix template
How to create a requirements traceability matrix step by step: what to link, planned versus executed coverage, and a free Excel RTM template with an example.
Choosing a requirements management tool
How to choose a requirements management tool: a practical checklist, demo questions, a worked refund example, and a free printable evaluation sheet.
Product
Test cases from Jira and Azure DevOps
Import Jira stories or Azure DevOps work items, generate reviewed test cases from their acceptance criteria, trace results, and push them back to the ticket.
Use case template and alternate flows
A use case template, a refund example with alternate and exception flows traced to criteria and tests, use case vs user story, and how ReqLens generates them.
Generating test cases from requirements
How to generate test cases from requirements, step by step: a worked refund example from acceptance criteria to linked test cases, review and approval.
Requirement Studio: rough to testable
How elaboration works in ReqLens: what it adds to a raw requirement, why every change needs approval, and how edits propagate to everything downstream.
Breaking a requirement into features
How ReqLens finds feature boundaries in a large requirement, why boundary detection and enrichment are separate steps, and what that separation protects.
Workspaces, roles and permissions
Three roles, ranked rather than listed, and what each can do. How project access resolves, and why some things belong to the workspace rather than a person.