Distinctions

Is

Identity (IS)Explanation
Process OrthodoxyTreating the official version of a method as the only legitimate way to work.
Method DogmatismInsisting that rules of a framework must be followed strictly regardless of context.
Framework FundamentalismBelief that deviation from the prescribed process corrupts the method.
MethodolatryElevating the method itself above the outcomes it was meant to produce.
Ceremony ComplianceMeasuring success by adherence to rituals (meetings, artifacts, roles).
Practice LiteralismApplying practices exactly as written rather than adapting them to circumstances.
Tool-Driven BehaviorAllowing the framework or tooling to dictate work instead of the problem being solved.
Ritual PreservationProtecting rituals because they belong to the process, not because they add value.
Purist InterpretationRejecting pragmatic adaptations as “not real Scrum / Kanban / Lean.”
Mechanical Process ApplicationExecuting the steps of a method without regard to purpose or outcomes.
Ritual over ReasonProcess rituals are followed because they belong to the method, even when they no longer serve the situation or objective.

Is Not

Other (IS NOT)Explanation
Principle-Driven AdaptationAdjusting practices while preserving the underlying principles.
Pragmatic Process UseTreating frameworks as tools rather than rules.
Continuous ImprovementChanging the process based on learning and feedback.
Contextual TailoringModifying practices to fit the team’s environment or constraints.
Outcome OrientationEvaluating practices by the value they produce rather than fidelity to the method.
Empirical Process ControlAdjusting behavior based on observation and experimentation.
Lean ThinkingEliminating practices that do not contribute to value delivery.
Situational LeadershipChoosing practices appropriate to the problem rather than the framework.
Framework LiteracyUnderstanding the intent behind practices and applying them intelligently.
Principle-First ThinkingStarting with goals and principles before selecting practices.

Boundary

Process Purity occurs when adherence to a prescribed process becomes more important than achieving the outcomes the process was designed to enable.

Process Purity optimizes for fidelity to the method, while adaptive practice optimizes for effectiveness in the real world.

Systems

Relationships

Perspectives


Works Consulted

  1. Driving Value With Sprint Goals