Guides
Guides written for practitioners, not for word count.
These are references on the craft behind the artefacts: how to write a user story worth building, gather requirements that survive contact with delivery, keep a backlog healthy, and read a BPMN diagram. Opinionated where the evidence supports it, honest about trade-offs where it does not.
The long-form guides
User stories
INVEST, story mapping, acceptance criteria that actually gate work, and the failure modes that turn stories into tickets nobody reads.
Requirements gathering
Elicitation techniques, how to run the conversations, and how to turn what you hear into requirements a stakeholder will sign.
Product backlog
Refinement, prioritisation, Definition of Ready, and keeping a backlog healthy instead of letting it become a graveyard.
BPMN
The BPMN 2.0 notation explained for people who map processes, not for standards committees. Elements, gateways, pools and when to stop.
The question-craft series
Shorter pieces on the questions that make delivery meetings produce better raw material. Better questions in, better artefacts out.
Good questions for user stories
What to ask before a story is written, so the story is worth writing.
Good questions for bug reports
The questions that separate a reproducible bug from "it broke".
Good questions for task notes
Turning a hallway commitment into a task someone can actually pick up.
Good questions for epics
Scoping questions that keep an epic an outcome rather than a folder.
Good questions for spikes
Framing the unknown sharply enough that the time-box can end.
Reading about the craft is optional. Doing it by hand is too.
Backlog.cloud writes the artefacts these guides describe, from your actual meetings. 3 free generations, no card.