- Get link
- X
- Other Apps
+-----------------------------------------------------------------------+
| FUTURE LAYER |
| - Estimated Time of Obstacle ARRIVAL (ETOA) |
| - Estimated Time of Obstacle-Respond DEPARTURE (ETOD) |
+-----------------------------------------------------------------------+
^
| Forward Projections & Dependencies
v
+-----------------------------------------------------------------------+
| PRESENT LAYER |
| - WORK IN PROGRESS (WIP) |
| - Active Execution & Real-Time Monitoring |
+-----------------------------------------------------------------------+
^
| Baseline Data & Historical Inputs
v
+-----------------------------------------------------------------------+
| PAST LAYER |
| - ACHIEVED ACCOMPLISHMENT |
| - Verified Baseline & Retrospective Metrics |
+-----------------------------------------------------------------------+
Layer 1: Past (The Foundation & Baseline)
- Core Focus: Proven capabilities, completed milestones, and historical velocity.
- Primary Metric: Achieved Accomplishment
- Role in the Architecture:
- Serves as the single source of truth for completed deliverables.
- Provides baseline data (cycle time, past blocker resolution rates, velocity) required to calculate accurate future estimations.
- Establishes reference points for quality, compliance, and auditing.
Layer 2: Present (The Execution Context)
- Core Focus: Active operational throughput, active state tracking, and resource allocation.
- Primary Metric: Work in Progress (WIP)
- Role in the Architecture:
- Tracks tasks currently undergoing execution.
- Measures operational capacity and constraints (limiting WIP to prevent bottlenecks).
- Continuously logs live execution metrics against the Past baseline to detect potential deviations early.
Layer 3: Future (The Predictive Risk & Resolution Window)
- Core Focus: Risk modeling, predictive scheduling, and contingency response planning.
- Primary Metrics:
- Estimated Time of Obstacle ARRIVAL (ETOA): The calculated point in time or milestone when a predictable risk, dependency failure, resource constraint, or technical debt will intersect and block active progress.
- Estimated Time of Obstacle-Respond DEPARTURE (ETOD): The target time or duration required to execute a mitigation strategy, clear the blocker, and resume normal operational flow.
- Role in the Architecture:
- Establishes a Risk Window (\text{ETOD} - \text{ETOA}) that quantifies expected downtime or overhead.
- Triggers automated or preemptive mitigations before the obstacle impacts Layer 2 (Present WIP).
- Uses feed-forward loops to adjust operational expectations based on historical resolution capability (Layer 1).
Comments