Delivery · Intake Queue
Intake requirements
Read the requirements handed over from planning and place each one in the work stream that will deliver it.
When planning hands a feature concept over to delivery, its requirements come with it. Each requirement has to be delivered by exactly one work stream, so part of shaping an intake item is deciding where every requirement goes.
Placing requirements matters for two reasons. An item cannot be promoted while any requirement is without a work stream, and Next drafts each stream’s tasks from the requirements in it.
Before you start
Open the intake item from the Intake Queue, then select the Requirements tab on the overview.
- Leads can place and move requirements.
- Work stream owners can hand back a requirement from their stream that does not belong there. See Setting up a work stream.
- Everyone else sees the requirements read-only.
Understanding the requirements table
| Column | What it shows |
|---|---|
| ID | The requirement’s short code from planning. |
| Requirement | The requirement’s title. If an owner handed it back, the reason appears underneath, for example Handed back by Sam: “This belongs with the API stream”. |
| Work stream | The stream that will deliver it. Requirements without a stream, or handed back, are shown in amber with Choose a work stream. |
| Tasks | How many draft tasks cover the requirement. |
Select a row to open the requirement in full.
Place a requirement in a work stream
- Select the requirement’s Work stream cell. Move requirement opens.
- Choose a work stream from the list. Or, to create a new stream, type its name and choose New work stream “…”.
The requirement now shows its work stream. The amber warning beside the tabs, for example 2 requirements need a work stream, counts down as you place requirements.
You can also move a requirement from the stream’s own requirements list. See Setting up a work stream.
Read a requirement in full
Select a requirement to open it. You see:
| Part | What it shows |
|---|---|
| Title and description | The requirement as planning wrote it. |
| Work stream chip | The stream that will deliver it. Leads can select it to choose a different stream, or Add to a work stream if it has none. |
| Set | The requirement set it belongs to in planning. Set in planning and can’t be changed here. |
| Category | The requirement’s category from planning, such as a MoSCoW or priority-tier value. Set in planning and can’t be changed here. |
| Acceptance criteria | What has to be true for the requirement to count as met. |
| Rationale | Why the requirement matters, as planning recorded it. |
| Evidence | The sources behind the requirement. |
Move between requirements
The top bar shows where you are, for example 4 of 11.
- Select the up and down arrows, or press K and J, to move to the previous or next requirement.
- Press Esc to return to the overview.
What happens next
Once every requirement is in a work stream, the Requirements assigned check is met. Owners can then draft tasks from their stream’s requirements. See Draft tasks.
After promotion, each work stream’s requirements are listed on its References tab. See References.
Good to know
- To change a requirement’s wording, criteria or category, change it in planning. See Requirements step.
- When a lead deletes a work stream that covers requirements, they must choose another stream to move those requirements to.