COMPEL Glossary / transformation-sprint
Transformation Sprint
A transformation sprint is a two-week time-boxed work period within the COMPEL Produce stage that delivers concrete outcomes across multiple pillars simultaneously.
What this means in practice
Unlike pure software development sprints, transformation sprints may include deploying a model (Technology), finalizing its impact assessment (Governance), delivering training to affected teams (People), and documenting revised workflows (Process). Each sprint follows a consistent structure: planning on day one, daily coordination through brief stand-ups, a review at the end demonstrating completed deliverables, and a retrospective examining what worked and what should change. COMPEL requires that every sprint include deliverables across multiple pillars -- no pillar may be entirely absent for more than one consecutive sprint without Steering Committee approval.
Why it matters
Transformation sprints deliver concrete outcomes across multiple organizational dimensions simultaneously, preventing the common failure of treating AI transformation as purely a technology exercise. By requiring every two-week sprint to address Technology, People, Process, and Governance, organizations build holistic capability rather than isolated technical deployments. This multi-pillar approach is what distinguishes transformation from mere adoption.
How COMPEL uses it
Transformation sprints operate within the Produce stage as two-week time-boxed work periods. COMPEL requires that every sprint include deliverables across multiple pillars, with no pillar absent for more than one consecutive sprint without Steering Committee approval. Each sprint follows a consistent structure: planning, daily coordination, review, and retrospective. Sprint outcomes feed into the Evaluate stage's performance measurement.
Related Terms
Other glossary terms mentioned in this entry's definition and context.