Back to Tags

#Requirements

Edge Case Review — What Breaks Before Users Find It

Review a feature or spec for edge cases, error states, permissions, data limits, abuse and accessibility gaps before it's built, with what the product should do in each case.

Nigel Yoshida

PRD One-Pager — The Problem, the Bet and How We'll Know

Write a short product requirements document: problem, goals and non-goals, users, key requirements, success metrics, risks and open questions, ready for review.

Nigel Yoshida

User Stories — With Acceptance Criteria Engineers Can Test

Break a larger feature into small, independent user stories in build order, with testable acceptance criteria, a first thin slice and splitting suggestions.

Nigel Yoshida

Feature Spec — From Idea to Buildable Ticket

Turn a feature idea into a spec a developer can build from: the problem, user stories, acceptance criteria, edge cases, data and API changes, and the open questions to settle first.

Nigel Yoshida

Software Requirements Gathering Framework

Ein strukturierter Ansatz zur Durchführung von Anforderungsanalysen für Softwareprojekte, um die Bedürfnisse der Stakeholder zu verstehen und vollständige, validierte Anforderungen zu sammeln.

Levent Yelmen

ROVO (JIRA) Product Owner Assistant - Scenario

The Scenario setting you can use when creating a PO assistant on JIRA's ROVO.

Luke Scicluna Bedford

Create acceptance criteria for an existing user story

Luke Scicluna Bedford