Backlog Refinement Agenda and Definition of Ready
Run refinement sessions that produce work items the team can pick up.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Create a refinement session plan for Azure DevOps boards. Team and cadence: [TEAM_AND_CADENCE]. Types of work items (epic, feature, user story, bug): [WORK_ITEM_TYPES]. Common problems at sprint planning: [PLANNING_PROBLEMS]. Write a 60-minute agenda with time boxes that add up, roles (facilitator, product owner, scribe), how to select items, the discussion prompts for each item (value, acceptance criteria, risks, dependencies, size), and the outcome recorded in fields (acceptance criteria, effort or story points, tags). Define a Definition of Ready checklist of eight to ten criteria and a rule for items that fail it. Add a way to track ready backlog depth (for example two sprints of ready items) and a table of metrics with the arithmetic. Include a facilitation guide for estimating with planning cards in plain words and a post-session routine. Mark Azure DevOps field names, process templates and features [VERIFY]; do not assume a particular process. Add a worked Definition of Ready of eight items (clear value, acceptance criteria, dependencies identified, sized, designs attached, test approach noted, small enough for one sprint, owner named) and an example of a story that fails two of them with the fix.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.