-
Using AI to support backlog refinement: questions before acceptance criteria
Review an existing backlog item with AI, expose missing behaviour and draft acceptance examples without inventing product policy or estimates.
-
Hiding a button is not access control: write a permission rule you can test
Turn a vague access requirement into a clear permission rule, with a fictional request tracker, five proposed checks and a reusable note for your next feature.
-
Your app says ‘file deleted’. What does that actually mean?
Separate expired access, removed active files and recoverable copies, then use a practical worksheet to check what your product can honestly promise.
-
Better requirements: working with developers, standards and suppliers
Learn how to clarify requirements with developers and suppliers, make standards usable and plan for the failures an integration must handle.
-
How to Run an Effective Backlog Refinement Session
Backlog refinement is one of the most underrated Agile practices. When done well, it helps your team arrive at Sprint Planning with a clearer understanding of the work, the questions still to answer…
-
What Is Gherkin Style? A Simple Guide for Product Owners and Agile Teams
If you work with Agile teams, you have probably seen acceptance criteria written using the words Given, When and Then. That structure comes from Gherkin, a plain-language way to describe how a feature…
-
How to write useful user stories: examples and acceptance criteria
Write user stories that lead to useful conversations and testable outcomes, with original examples, acceptance criteria and practical ways to split work.
