DICE framework for IT: project risk assessment

DICE Framework: Predicting IT Project Success from Day One

The DICE framework by Boston Consulting Group enables quantitative assessment of an initiative’s success probability before launch. The formula accounts for four key factors: Duration (D), Integrity (I), Commitment (C1 and C2), and Effort (E). The final score determines the risk zone: 7–13 = success, 14–17 = caution, 18+ = failure.

Each parameter is scored on a scale from 1 (optimal) to 4 (critical). The formula is: DICE = D + 2×I + 2×C1 + C2 + E. The high weight assigned to I and C1 underscores the critical impact of team capability and leadership support.

Parameter Breakdown

Duration (D): Frequency of Check-ins

This measures how regularly progress, issues, and deadlines are reviewed. Frequent check-ins improve control without falling into micromanagement.

| Score | Condition |

|-------|-----------|

| 1 | Every 1–2 weeks |

| 2 | Every 3–4 weeks |

| 3 | Every 2 months |

| 4 | Less frequently |

Integrity (I): Team Competence

Assesses hard skills, experience, and seniority of team members, including the lead. The ×2 multiplier reflects its dominant role: weak teams dramatically increase risk, but improvements yield strong positive effects.

| Score | Condition |

|-------|-----------|

| 1 | Professionals |

| 2 | Mostly yes |

| 3 | Mostly no |

| 4 | Weak competencies |

Commitment (C): Alignment and Support

Split into C1 (leadership) and C2 (team). C1 carries double weight—top-down backing protects against distractions.

C1 (Leadership):

| Score | Condition |

|-------|-----------|

| 1 | Fully supportive |

| 2 | Neutral |

| 3 | Secretly opposed |

| 4 | Openly opposed |

C2 (Team):

• Willingly embrace.
• No objections.
• Resist (sabotage via delays).
• Strongly oppose.

Effort (E): Workload Pressure

Percentage of time spent beyond core responsibilities.

| Score | Condition |

|-------|-----------|

| 1 | ≤10% or primary task |

| 2 | 11–20% |

| 3 | 21–40% |

| 4 | >40% |

Real-World Case: Test Automation Initiative

A QA team implements a test automation framework. Timeline: one quarter, 30% extra effort, no prior experience, lead convinced, high enthusiasm, no regular syncs.

Initial assessment:

• D=4 (no syncs)
• I=4 (no experience)
• C1=2 (neutral)
• C2=1 (enthusiastic)
• E=3 (30%)

DICE = 4 + 8 + 4 + 1 + 3 = 20 (failure).

Root causes: underestimated effort, unresolved issues piling up, lack of protection from bugs.

Mitigation steps:

• Introduce weekly syncs: D=1 → DICE=17.
• Extend timeline to two quarters: E=2 → DICE=16.
• Secure lead’s active support: C1=1 → DICE=14.
• Add mentor/expert: I=2 → DICE=10.
• Bring in experienced team: I=1 → DICE=8 (success).

Monitoring & Application

Recalculate DICE when changes occur: key person shift, new tasks. Conduct reviews during syncs (D). Post-mortems reveal estimation errors.

Use DICE for:

• Cross-team initiatives.
• Process or architecture changes.
• Initiatives requiring behavioral shifts.
• Projects lasting over one month.

IT use cases: CI/CD pipelines, system migrations, new testing models, cultural transformation.

Collective scoring reduces subjectivity—disagreements highlight hidden risks.

Key Takeaways:

• High weight on I and C1: Invest in team strength and leadership buy-in.
• Frequent syncs (D=1) quickly move projects from failure to caution zone.
• Team resistance (C2=3–4) signals covert sabotage.
• Workload >20% without priority = top trigger for project failure.
• Post-analysis is mandatory for calibration and learning.

— Editorial Team