Agile Demand Management: Product Backlog, Work Item List, and Option Pool

1. Product Backlog: Simple

Agile teams aim to deliver high‑quality, high‑value software by first implementing the highest‑priority requirements, maximizing stakeholder ROI. In Scrum, the prioritized stack of requirements is called the "product backlog".

New requirements are prioritized by stakeholders and inserted at the appropriate position in the stack.

The ultimate authority on prioritization is the Product Owner, who represents all stakeholders.

The backlog is initially populated with envisioned requirements at project start ("backlog grooming").

Each sprint, the team pulls work from the top of the stack and commits to delivering it by sprint end.

Stakeholders can add, modify, or reorder requirements at any time.

Non‑requirement work items are prioritized either through team‑stakeholder negotiation or as part of planned idle time.

Figure 1 illustrates Scrum demand management.

2. Work Item List: Disciplined Agile

Beyond functional requirements, teams also handle non‑feature work such as training, defect fixing, and cross‑team reviews. Disciplined Agile Delivery (DAD) extends Scrum by incorporating risk‑value methods and forward‑looking modeling.

Risk‑value approach: early identification of technical risks (e.g., architecture validation) and prioritizing high‑risk items to the top of the stack.

Forward modeling: complex work items are examined in advance (backlog refinement) to reduce overall project risk.

Figure 2 shows the disciplined agile work‑management flow.

3. Option Pool: Lean

Lean teams treat work items as optional solutions rather than mandatory tasks, managing them in a pool and pulling the most valuable items just‑in‑time (JIT) based on stakeholder input.

Options are categorized (e.g., standard, fixed‑date, urgent, intangible) to aid prioritization.

Limiting Work‑In‑Progress (WIP) improves predictability, quality, and productivity.

Old items are aged out of the pool if they remain unselected for a defined period.

Figure 3 depicts the lean work‑management process.

4. Which Strategy Is Right for You?

No single approach fits all situations; you must evaluate and select the strategy that best matches your project context. Table 1 compares the three methods.

Source: https://pub.intelligentx.net/node/709

Discussion: Join the Knowledge Planet or the "Chief Architect" circles for deeper conversation.

Thank you for following, sharing, and liking.