Our 'User Stories' articles
The Cost of Missing Acceptance Criteria

QA and development teams waste a lot of time, money and effort if requirements don’t have enough acceptance criteria. Read here how to avoid this situation.
Turning Requirements into User Stories

Many projects start with traditional requirements. Then, a decision is made to be more agile. Turning requirements into user stories can be a daunting task.
Writing Test Cases from User Stories & Acceptance Criteria

Well thought out acceptance criteria can be a tester’s best friend. We look at how to write test cases from the user stories and acceptance criteria.
User Story vs Requirement – What’s The Difference?

User story vs requirement... while similar in nature and often used interchangeably, user stories and requirements are different.