The Historical Shield

1. The Pre-Agile Reality: The December Promise and the October Pivot

Before Agile was institutionalized, software development operated under what veterans remember as the “Death March.”

Sales executives would sign enterprise agreements promising impossible feature sets by December. In October, halfway through the delivery calendar, executive leadership would pivot the requirements without moving the deadline.

Engineers had no formal apparatus to quantify impossibility. They slept under their desks, burnt out their personal lives, and patched together brittle, untested code that cracked under production load.

2. Story Points as a Defensive Weapon

Story points and the Definition of Done (DoD) were never intended as managerial productivity metrics. They were engineered by practitioners as a mathematical defense mechanism:

“Here is the math. Here is the size of the new scope. If we take on this pivot, it displaces that feature. Here are the exact boundary cases we must cover to declare it ‘Done’.”

This shield established three indispensable structural pillars:

1. Feasibility & Negotiation: It forced clients and executives to acknowledge the conservation of energy in engineering.
2. Contractual Clarity for QE: Quality Engineering was no longer a guessing game. It was a legally binding test of explicit assertions.
3. Resilience via Tests: Scope boundaries gave engineers the runway to write tests that survived sudden shifts in direction.

3. The Degeneration: When the Shield Became the Whip

Over subsequent decades, the administrative apparatus stripped the shield of its defensive properties. Non-technical middle management discovered that “points” could be counted, charted, and weaponized into a surveillance apparatus.

The question ceased to be “Are our outcomes sound and tested?” and became “Did this team burn enough velocity points this sprint?”

The process grew heavier than the software it was created to protect.