This paper examines how information technology and digital consulting firms can manage the shift from traditional, siloed project-tracking models toward product-based value-delivery models built on scaled agile practices. It argues that no single change-management framework is sufficient on its own. Lewin's three-stage model offers a valuable psychological foundation but its "refreeze" stage is impractical in environments requiring continuous releases and rapid regulatory adaptation. The McKinsey 7S Framework is effective at exposing latent structural misalignments, yet functions as a diagnostic tool rather than an execution roadmap. Kotter's eight-step model and the ADKAR model together provide both enterprise-level execution architecture and individual adoption mechanics, but risk becoming rigid and provoking defensive behavior among solution architects and senior developers unless adapted to accommodate decentralized agile ownership.
The paper then addresses how change type and leadership approach should be selected according to organizational context. Transformations of this kind are typically revolutionary in substance — redesigning the commercial and architectural model — while requiring evolutionary execution through short sprint cycles to avoid destabilizing active delivery portfolios. Drawing on Dunphy and Stace's continuum and the Change Kaleidoscope of Balogun and Hope Hailey, the analysis favors a participatory approach over directive intervention, particularly where regional talent shortages make attrition costly and where legacy engineering teams begin with low readiness. Leadership is positioned as the primary change agent, responsible for absorbing organizational tension, establishing psychological safety, reframing team separation as a protective mechanism rather than a loss of autonomy, and embedding governance controls directly into tracking systems and workflow automation rather than relying on written policy alone.
Cultural and political dimensions receive equally close attention. Using Schein's three levels of culture, the paper traces how artifacts, espoused values, and underlying assumptions must be addressed simultaneously, shifting teams from the assumption that success means delivering a fixed scope within protected boundaries toward one in which software capability flows continuously in response to changing requirements. On the political side, it proposes a dual-role integration model in which traditional project managers retain formal authority over client interfaces and contractual commitments while serving as Scrum Masters within protected engineering streams, converting potential blockers into change champions. Sustainability is framed through Senge's learning-organization disciplines, with continuous professional-development tracks and multidisciplinary agile streams turning performance data such as sprint velocity, defect density, and cycle time into a shared learning asset. The paper concludes that successful transformation depends not on choosing one model but on intelligently combining several according to context, and on treating change management as a long-term strategic investment in organizational adaptability rather than a time-limited transition project.
By Research and Development Department
