Meeting types
Every ceremony has outputs. Here is what each produces.
A retro does not produce user stories and a refinement session does not produce a process model. Backlog.cloud is meeting-type aware: tell it what kind of session it is joining, or what kind of transcript you are pasting, and it listens for the artefacts that ceremony actually generates. These pages break down the main ones.
The main ceremonies, in depth
Backlog refinement
The ceremony that feeds the sprint. Stories sharpened, acceptance criteria pinned down, estimates challenged. The densest source of backlog items there is.
Sprint planning
Commitments, capacity and scope decisions. Produces stories, tasks, the odd bug that jumps the queue, and decisions worth writing down.
Discovery
Workshops and interviews at the fuzzy front end. Feeds the Discovery Pack: stakeholders, pain points, personas and open questions in one living document.
Process mapping
Walk through how the work actually flows and get a BPMN 2.0 process model out the other side, as-is or to-be.
Also understood
Each of these has its own extraction profile too. An incident review yields action items and RAID entries, a stand-up yields blockers and tasks, a steering committee yields decisions.
- Sprint retrospective
- Sprint review
- Daily stand-up
- User research
- Bug triage
- Incident review
- Post-mortem
- Project kickoff
- PI planning
- Steering committee
Point it at your next ceremony
Paste a meeting link or a transcript, pick the meeting type, and review what comes out. 3 free generations, no card.