2020 Best CIO Acceptance Speech (penned in 2010)

[article]
Summary:
In the 2010 article, ThoughtWorks consultant Tiffany Lentz pens the speech a successful CIO might write ten years hence in 2010. She talks about the ways that agile principles had become the norm in development and spread beyond software teams in into IT and corporate planning and project execution.

For people who do not know me, it must be difficult to comprehend how I became the CIO of this mega multinational conglomerate. It has been an uphill task to move from the server rooms to this boardroom; believe me that technology skills alone were not good enough to make this gradual but sure leap. Looking back, I give credit to a heady concoction of portfolio management experience, stead fast communication, and adoption of agile principles and practices across all the IT divisions that made this happen. And also a lot of good old luck.

When I joined this organization as the VP of Engineering, 10 years back, agile was still in its teens. Many of my fellow managers had heard of rapid release capabilities, but had never seen a company really do it. I knew from my experience in media start-ups that Agile would be mainstream in a few short years; it was just a matter of time. And there are obvious benefits in doing iterative development to incrementally build software products. Besides, Agile with its ‘inspect and adapt’ philosophy chimed well with the PDCA (plan-do-check-act) paradigm of lean operations. However it was hard for me to sell this apparently obvious concept of evolutionary software product development to the bosses.

The idea of “iterating” over a concept was something that only startups were doing. Those ideas somehow did not seem ‘stable’ for an organization as large as ours. In addition, we were tied to licensing large technology stacks and rigorous deployment checklist gates, making it difficult to accommodate frequent releases; we were limited to only two enterprise wide releases in a year keeping in mind the cost of integrating with the legacy systems for each such release. While my bosses understood the proposed benefits of evolutionary software product development, they were not ready or prepared to revolutionize our IT divisions. So I was up against massive organizational dissent when I started advocating change: adoption of Agile’s evolutionary concepts and using open source platforms and tools for product development.

Change is always an alien, still you see it happen! Since I believed so strongly in this vision of evolutionary software product development, I wanted to prove it to those who could fund my vision and allow me to effect change. I started small, with one project in my department. I was able to illustrate moderate success with the pilot; the business sponsor for the project was impressed with the cost control and the discipline involved in building the product iteratively. I got the go-ahead to introduce the change virus in my department, one project at a time. This took me a couple of years, but at the end of the second year I was asked to run another division and made the same changes. These divisions were releasing so frequently and their business counterparts were so involved that other divisions started referring to us as the “Business Technology” group within the next few years. Finally, I tackled the data warehousing and mainframe divisions. A Value Stream Mapping exercise pointed out the areas needing the most attention and we started the multi-year effort of reworking our mainframe.

Back in 2010, the Gartner group wrote an article that strongly impacted the way I thought about team dynamics. I was not the CIO, but thinking like one helped me further transform my teams. This article, “Leading in Times of Transition: The 2010 CIO Agenda”, called out a few key differentiators that CIOs (and managers like myself) should consider as we were moving from a time of recession to recovery. By focusing on the

About the author

Anupam Kundu's picture Anupam Kundu

Anupam Kundu is currently employed as a lead consultant with ThoughtWorks North America. In the current role, Anupam’s goal is to help clients get the most bang for their buck in developing new and innovative products following lean/agile software development principles and practices.

Anupam has more than thirteen years of experience in various stages of software development life-cycle and post-implementation activities as a programmer, business analyst, project/program manager, and change management consulting.

AgileConnection is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, TechWell.com is the place to go for what is happening in software development and delivery.  Join the conversation now!

Upcoming Events

Oct 12
Oct 15
Nov 09
Nov 09