Tuesday 19 June 2012

Retrospective on Agile Transformations: Challenges to Adoption - Bottom-up Approach


Challenges to Adoption - Bottom-up Approach
Agile principles and values often easily adopted by development teams if provided effective coaching. These teams also understand and adopts the technical excellence practices e.g. XP (TDD, Pair Programming, CI etc.) with some initial resistance and start seeing their benefits sooner rather than later experiencing considerable improvement in quality of deliverable, customer satisfactions and timeliness of deliverable. Teams starts getting quite motivated by delivering right business value to its customers with quality software and people see a very positive buzz around them. Although this initial initiative gives lots of agile buzz within an organization but still its benefits are limited as rest of the business (Sales, HR, Finance, sometime even Product design) doesn’t join this agile journey. Slowly-slowly the fizz goes out of this agile initiative as team starts getting demotivated due to non-involvement of   other organization functions and little or no commitment seen from middle management and CxO layer. Senior and Middle Management often don’t get the new management paradigm that is required for an enterprise agile transformation. The main bottleneck is actually around their experience of power that is almost exclusively around the notion of being in charge, whereas, in new way of working power shifts from the notion of “being in charge” to the notion of “being connected”. This means that you don’t have to be in charge to exercise power.

Bringing management layer part of overall agile transformation enables a leaner organization that multi-fold the benefits of agile in a large organization. Once management joins the agile transformation journey, bringing other functions to join becomes little easier.

 

Retrospective on Agile Organizational Transformations: challenges to adoption


Abstract:
Agile transformations often fail or don’t deliver full benefits in large organizations. Lack of understanding of agile principles especially by management team leads to thinking that agile is only for development teams rather than an enterprise thought process. Despite development team using technical excellence practices (TDD, Pair Programming, Continuous Integration etc.) to produce quality deliverable the other part of the organization limits the benefit of agile by not adopting agile mindset. Often large organizations find difficult to implement agile principle & values because of its existing corporate structure, culture, mindset and lack of commitment from executive teams to support the agile transformation. 

Agile transformation started from bottom-up get some good initial success but derails later due to organizational constraints. Organization culture that promotes deep hierarchical (and dysfunctional) structure, political environment, policies (not aligned towards employee empowerment) and individual reward structures are often main reason stated by most of the fail agile transformations teams. The successful agile transformation initiatives are led by people right from the top CxO layer by putting “commitment before success” formula and supported by middle management using servant leader relationship to bring whole organization gradually towards agility to make organizations being agile rather doing agile.  

This is a series of article that I will continue writing on my blog and in each article will target few related reason for failed Agile transformations. Please watch this space...