1. **Reactive Work**
Reactive work is driven by immediate needs within the team or external stakeholders. These tasks are often urgent, labeled as “red alerts,” and managed on a First-In-First-Out (FIFO) queuing basis with Work-in-Progress (WIP) limits. This workflow is a continuous cumulative flow without a defined beginning or end.
2. **Batched Work**
Batched work can be divided into two subcategories:
**A. Disjointed and/or Compiled Ticket Work**
- Involves cleanup tasks, small polishing tweaks, lightweight assumption tests or prototypes, and cross-team efforts within a single cycle.
- Often iterative, managed with a visual card flow model and WIP limits during cycle intervals.
**B. Strategic Feature Work**
- It encompasses feature development that is meaningfully large but contained within a single cycle.
- Typically includes incremental or new product functionalities.
- Requires framing and shaping before entering the development cycle.
- Each bet can occupy one-third, two-thirds, or an entire six-week cycle.
3. **R&D / New Product Development Work**
- Refers to larger, multi-cycle projects or experiments funded using a hybrid stop-loss budgeting model under an innovation risk portfolio allocation percentage.
- In addition to maintaining highly organized communication and a coherent vision, no additional structure is required.
- Focuses on projects with significant exploratory components that shape new products or paradigms. Risk is assumed.
It’s important to recognize these different value streams and design team topologies that address how they’ll be managed.