Distinctions
Is
| Example / Attribute | Explanation |
|---|---|
| Recreating traditional project phases inside iterative structures | Agile constructs (like sprints) are used as containers for sequential phases such as requirements, testing, or stabilization. |
| Introducing practices that quietly restore phase gates | Mechanisms like a strict Definition of Ready act as approval checkpoints before work can begin. |
| Using agile constructs as containers for sequential delivery stages | Work still flows through requirements → development → testing → release, but those stages are hidden inside multiple sprints. |
| Maintaining the traditional lifecycle under new vocabulary | The organization claims to work iteratively while still executing the same stage-based lifecycle. |
| Creating “special sprints” that correspond to lifecycle phases | Examples include Sprint Zero, Testing Sprints, or Hardening Sprints that map directly to traditional project phases. |
| Practices that restore predictability expectations from waterfall | Techniques are added to recover the certainty that stage-gated processes once provided. |
| Preserving governance structures through agile terminology | Approval processes, sign-offs, or reporting gates remain but are embedded in agile rituals. |
| Agile rituals functioning as disguised status gates | Events like Sprint Demos become status presentations instead of feedback loops. |
| Structural reconstruction of the old lifecycle inside the new framework | The delivery model remains phase-based even though the framework appears iterative. |
Is Not
| Near Neighbor | Explanation |
|---|---|
| Simply using different terminology | Renaming things without structural impact is superficial but does not necessarily recreate lifecycle phases. |
| Legitimate workflow policies | Practices like backlog refinement or WIP limits coordinate work but do not recreate stage gates. |
| Sequential work caused by technical dependencies | Some work must occur in sequence due to architecture or external systems; this does not imply a hidden lifecycle. |
| Teams still experimenting with practices | Early adoption often includes imperfect implementation without intentionally restoring phase structures. |
| Occasional stabilization work within a sprint | Addressing defects or performance issues as part of normal iteration is different from dedicating entire phases to it. |
| Incremental delivery with continuous quality activities | Teams integrating testing, review, and integration inside each sprint are operating iteratively. |
| Explicit hybrid lifecycle models | Some frameworks openly define phases; lifecycle smuggling specifically refers to covert reconstruction of phases. |
| Stakeholder reviews intended for feedback | A genuine review event focuses on learning and adaptation rather than approval gates. |
| Surface-level framework theater | Framework theater focuses on appearance; lifecycle smuggling specifically reconstructs delivery phases within the framework. |
Boundary
Lifecycle Smuggling occurs when the structure of a traditional delivery lifecycle is covertly reconstructed inside an iterative framework, allowing legacy phase gates and sequencing to persist under new terminology.
| If the practice… | Then it is… |
|---|---|
| Reintroduces sequential lifecycle stages disguised as agile practices | Lifecycle Smuggling |
| Supports iterative flow without reconstructing phase gates | Not Lifecycle Smuggling |
Systems
Relationships
| Relationship | Concept | Rationale |
|---|---|---|
| Enabled by | Cargo Cult Adoption | Lifecycle Smuggling commonly emerges when practices are copied without understanding their underlying principles, allowing traditional lifecycle structures to be recreated inside agile terminology. |
| Manifests as | Sprint Zero | Sprint Zero recreates the traditional project initiation and upfront planning phase before iterative development begins. |
| Manifests as | Definition of Ready | When used as a strict readiness gate, the Definition of Ready restores the traditional requirement approval phase before work can begin. |
| Manifests as | Testing Sprints | When used as a strict readiness gate, the Definition of Ready restores the traditional requirement approval phase before work can begin. |
| Manifests as | Hardening Sprint | Hardening Sprints recreate the stabilization phase typically performed before release in traditional project lifecycles. |
| Manifests as | Sprint Demo | When used primarily as a status presentation or approval checkpoint, Sprint Demos replicate the stakeholder sign-off gates common in traditional project governance. |