Distinctions
Is
| Identity | Explanation |
|---|---|
| Repeated requirement change | Requirements are frequently revised, replaced, added, or removed during delivery |
| Instability in what is needed | The team cannot rely on the current requirement remaining valid long enough to execute predictably |
| Rework pressure | Previously completed analysis, design, implementation, or validation must be revisited |
| Planning volatility | Forecasts and commitments become less reliable because the target keeps moving |
Is Not
| Other | Why It’s Different |
|---|---|
| The Single-Request Illusion | Requirements churn describes repeated change; The Single-Story Illusion explains a specific mismatch where change is hidden by the continuity of one business objective or story |
| Scope Creep | Scope creep emphasizes expansion; requirements churn can include replacement, reversal, deletion, or redefinition without net expansion |
| Iteration | Iteration is deliberate learning through feedback; requirements churn becomes friction when learning is not bounded, visible, or incorporated into planning |
| Exploration before commitment | Early uncertainty is not churn if the work is explicitly framed as discovery |
Boundary
Requirements Churn exists when requirements change frequently enough during delivery to create rework, planning instability, or unclear accountability.
Systems
Relationships
| Relationship | Concept | Rationale |
|---|---|---|
| Related to | The Single-Request Illusion | The Single-Story Illusion is one mechanism by which requirements churn becomes contested rather than simply managed |
| Produces | Invisible Value | Rework and revalidation can disappear when only final output is visible |
| Reinforces | False Precision | Estimates become misleading when based on requirements that do not stay stable |
Perspectives
| Stance | Who (Point) | What They See (View) | Optimize For | Insight | Blind Spots |
|---|---|---|---|---|---|
| The Agile Absolver | Stakeholder, sponsor, or reactive organization | Change is just part of being agile | Keeping options open as needs evolve | Real learning should change plans | Can use agility as a cover for instability, indecision, or late discovery |
| The Rework Witness | Delivery team or IC | Each change invalidates prior analysis, implementation, or validation | Protecting focus and reducing waste | Churn is experienced as repeated rework, not just flexibility | Can become defensive toward legitimate learning |
| The Signal Seeker | Product owner, analyst, or discovery lead | Requirement changes may reveal new information about the problem | Learning what is actually valuable | Some churn is a sign the team is discovering reality | May understate the delivery cost of absorbing every new signal immediately |
| The Planning Realist | Manager, planner, or delivery lead | Forecasts degrade when the target changes faster than the team can adapt | Keeping commitments, expectations, and tradeoffs honest | Change is useful only when the system can observe, absorb, and re-plan around it | Can over-index on stability when uncertainty is genuinely high |