1. Requirements Management
  2. Process
  3. Requirement item delivery
Process · Requirement item delivery

Requirement item delivery

The item board is the team's working queue. It shows what is waiting, underway, in review or blocked, while the parent requirement carries the broader delivery state. Owners should update both levels when the underlying work changes.

Step by step

  1. Break down work Business Analyst

    Business Analyst creates an item beneath the correct requirement and records title, priority, assignee, estimate and due date.

    • Creates assigned delivery detail under the requirement.
    • Updates Requirement items, Requirements
  2. Work the items Team Member

    Team Member moves an assigned item from backlog into progress and updates its actual work and completion information.

    • Shows progress, owner, dates and effort.
    • Updates Requirement items, Team members
  3. Review the item QA Engineer

    QA Engineer checks work in review against the requirement and records a verification finding if something needs correction.

    • Records work ready for review and any finding raised.
    • Updates Requirement items, Verification findings
  4. Close the work Business Analyst

    Team Member marks the item done after review, while the Business Analyst updates the parent requirement when its full scope is complete.

    • Records completed item work and updates the parent lifecycle.
    • Updates Requirement items, Requirements

Where it usually breaks

And how to keep it from happening.

  • An item is assigned without enough description to identify the expected outcome. The Business Analyst should clarify it before work begins.
  • The board says an item is in progress while the owner has marked the parent requirement blocked. Check both records during planning.
  • A review concern is mentioned only in conversation. Record a finding with its project and owner so it remains visible.
  • An item's actual hours and submitted time differ. Review which figure the team maintains directly and which comes from time entries.
Business Analyst
Structures the items; Team Member works them; QA Engineer checks review work; Project Manager resolves blockers.

Set up Requirements Management your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started