# Split project scope into reviewable slices

Illustrative planning brief; no automatic product import.

Illustrative case: “build a client portal” includes authentication, document viewing, uploads and billing. The first useful slice is read-only document access.

## Decision

Start with authorized read-only access; leave upload and billing decisions in separate, explicitly deferred slices.

## Owned work

- Define the first usable slice
  - Owner role: Delivery lead
  - Acceptance evidence: The brief describes one client viewing an allowed document and lists excluded actions.
- Expose the end-to-end unknown
  - Owner role: Engineer
  - Acceptance evidence: A short investigation records how document authorization will be checked across the request.
- Review the slice boundary
  - Owner role: Product owner
  - Acceptance evidence: The owner approves a demonstration plan and the deferred-work list.

## Workflow

1. Identify the smallest observable user outcome, rather than a list of technical layers.
2. Record the uncertainty that could invalidate the slice before scheduling it.
3. Review the first demonstration and use its findings to choose the next slice.

## Judgment

Do not treat independent slices as permission to skip shared authorization or data-integrity requirements.


## Filled illustrative decision

A synthetic portal review approves authenticated viewing of two sample documents. Upload controls and billing are absent from this slice. The reviewer accepts read-only access and retains separate questions about upload ownership and billing requirements; nobody reports the whole portal complete.


## Workflow questions

### Why not start with all backend work?

A purely technical partition may leave no reviewable user outcome. Use component tasks inside an end-to-end slice when needed.

### What if the first slice reveals a blocker?

Reassess the slice and its assumptions before expanding scope. Preserve the investigation evidence so the decision is traceable.

## Product connection

Prepare the thin delivery slice and exclusions before organizing the corresponding tasks in TeamBoostAI.

Confirm account availability before adopting this manual outline.