Know what to build before you commit to the build.

What needs to be possible for your next pilot, release or customer? Establish the users, business objective and constraints, then separate essential functionality from the later backlog.

The scope of the sprint is agreed before it starts. Its outputs are designed to make the implementation decision clearer.

• Product objectives and prioritized workflow
• Architecture direction and integration boundaries
• Scope, exclusions and key dependencies
• Milestones and proposed acceptance criteria
• Risks, open questions and an implementation estimate

Scoping is a standalone engagement. The conclusion may be to build a smaller release, change an assumption, use an existing tool or wait. Implementation is proposed separately; any credit for reused planning work is agreed in that proposal.

A short brief, prototype, repository overview or existing product is enough to begin the discussion. Do not send credentials or private customer data in an initial inquiry.