Distinctions
Is
Is Not
Boundary
Systems
Leverage Points
| Level | Rationale |
|---|
| 01. Transcending Paradigms | N/A |
| 02. Paradigms | N/A |
| 03. Goals | N/A |
| Self-Organization | Backlog refinement lets the team shape their work—clarifying requirements and negotiating boundaries instead of following top-down directives. |
| Rules | Ex: Split Stories > 8 story points |
| Information Flows | Moves information earlier so developers understand scope, constraints, and expectations. |
| 07. Reinforcing Feedback Loops | N/A |
| Balancing Feedback Loops | Maintains the backlog. Typically, seek to prevent either feast or famine. |
| Delays | Reduces discovery delays that would otherwise occur during implementation. |
| 10. Stock-and-Flow Structures | N/A |
| Buffers | Backlog Capping (limiting the maximum size of the backlog) would apply at this level. |
| Numbers | Sizing and splitting stories. |
Relationships
Perspectives