Listening: Backlog Refinement Session

"Out of scope" is a boundary-setting term. It explicitly defines what is NOT included in a given ticket, sprint, or project phase.

Key vocabulary for scope discussions:

• "in scope" — included in this ticket; will be done
• "out of scope" — excluded from this ticket; will not be done here
• "the way I read it" — my interpretation of the requirement; signals that clarification may still be needed
• "touching [feature]" — informal for modifying or working on that part of the codebase

Why scope clarity matters in refinement: Unclear scope leads to scope creep — work expanding beyond the original intention. Explicit "in / out of scope" language prevents this and allows accurate estimation.

Vague acceptance criteria is a common refinement problem. The word "successfully" without definition leaves the team to guess what done looks like — leading to rework or disputes at review time.

Good acceptance criteria vocabulary:

• "good catch" — acknowledgement that someone spotted a real problem; common positive reinforcer
• "tighten it up" — make it more precise and specific
• "within 5 seconds" — measurable time constraint; well-formed criteria are testable
• "what the success state looks like" — engineer asking for a concrete definition of done

The INVEST model: Good acceptance criteria should be testable — you should be able to write an automated test or manual test step directly from them. Vague criteria like "works correctly" or "submits successfully" fail this test.

"Non-negotiable" in priority discussions means the item has fixed, mandatory inclusion — it cannot be traded off or moved to a later sprint regardless of capacity concerns.

Priority negotiation vocabulary:

• "non-negotiable" — must be done; not open to debate
• "blocking revenue" — the bug is preventing the business from making money; very high urgency signal
• "push X above Y" — prioritise X over Y; rank X higher in the backlog
• "compliance deadline" — an external regulatory or legal date that cannot move; creates fixed urgency
• "stretch goal" — a lower-priority item pulled in only if capacity allows after higher-priority items are done

Ordering language: Notice the SM's summary uses "so the ordering is: A, B, then C as stretch" — this is a clear, professional way to confirm priorities verbally.