Blizzard Dev Case Study

Diablo IV DLC Scope & Complexity Estimator

"Diablo Himself Didn't Get Dedicated Diablo 4 DLC Because 'Diablo's Very Demanding', Devs Say" — Kotaku

Scoping Workbench

Adjust pipeline allocation
92
Multi-joint bone hierarchies, tail collision physics, horned mesh collision, destructive terrain bounds.
85
Pre-rendered cutscenes, dynamic light probes, specialized facial capture, and volumetric hellfire shaders.
90
Telegraph wind-ups, phase transitions, dynamic cloth flaps, and procedural quad-leg locomotion.
78
Targeted Uber Uniques, affix pool balancing, class balance checks, and legacy system interaction testing.

Studio Telemetry

Real-Time Risk Engine
Scope Creep Index 345
Est. Prod Months 28.5
Dev Burnout Risk Critical
Scoping Verdict
Demands Exceed Safe Scope
Simulated demands trigger extreme technical debt in character rigging and cinematic pipeline. Blizzard would require multiple staggered cycles to deliver this without critical studio crunch.
Generated Brief Handoff (Durable Record)
Enjoy this tool? Build your own with Super