Offshore Management Framework: The key to managing outsourced IT projects across time, distance and cultures.

« January 2007 | Main | March 2007 »

February 23, 2007

Additional notes on Agile Offshoring

Continuing my earlier thread on managing Agile Offshore Development, a few notes from my recent reading on the topic:

It was interesting to scan the articles in this month’s Agile Journal focused on “Offshore Agile Development”. The editor leads by stating:
Offshore Agile development - no longer an anomaly but an increasingly attractive option for developers and consultants alike. Most companies start with some co-located Agile experience and then transition to offshore teams. However, others jump right into distributed Agile projects, and then factor in the time and cultural differences when involving teams in different countries or companies. Regardless of the approach, the numbers are growing. Successful offshore Agile teams have begun to discuss their experiences and share best practices for these challenging projects.

On a similar thread, it was interesting to read about “Primavera sends agile development to India” The computerworld article says “The company is using the offshore model to develop a new version of Primavera Enterprise, its flagship product suite. It is also considering the outsourcing of other product development to India.”

Interesting British Computer Society (BCS) website features Chinese Academy of Sciences' analysis of agile software development processes. The article begins by analysying "The phenomenon of global software development has intensified more than ever before, resulting in an increasing dispersion of software development activities across geographies."

Which seems to bring us closer to the point I was making earlier . . . Agile Offshore does not sound like an Oxymoron. Right?

February 21, 2007

Is IT-Business/Domain Knowledge overrated?

I was reading an interesting article on “America's 400 Best Big Companies” in a recent issue of Forbes magazine featuring “The Best Of The Best” and began musing: is the knowledge of “business domain” and experience overrated in the media and popular IT press.

To set the context for an argument: Most technology consultants, especially management consultants with an IT focus tend to emphasize the need for ‘Business IT Alignment,’ and rightly so. I will not argue against the need for businesses driving IT; business strategy, and requirements do drive much of IT needs. The business needs (aka requirements) for IT systems, in turn are driven by a fundamental business driver: make more money; a.k.a maximize shareholder wealth. Hundreds of books, articles and papers have been published on the topic with a variety of flavors.

No doubt that knowledge of the business domain is as significant as knowledge of technology, and a key success factor for project managers.  While Program Managers and leaders will generally depend on business analysts and domain experts for guidance, any knowledge of the functional area will go a long way.

However, my musing was about how overrated the knowledge of business context (and business domain knowledge) is, especially in an offshored context. Because of the complexity of businesses systems, it is hard to expect an individual to gain expertise in the different functional areas in a reasonable amount of time.

And there is the cultural context of business. Let me explain my thought with two examples: Corrections Corp. Of America, featured in the Forbes article that briefly describes the ‘business model’ 

Crime pays. At least for John Ferguson, chief of $1.3 billion (sales) Corrections Corporation of America (nyse: CXW), the nation's largest privatized prison operator. If there's one thing Ferguson can rely on, it's that criminals are never in short supply and there aren't enough bars to put them behind. Ferguson's 23-year-old firm, in Nashville, Tenn., is the oldest company of its kind. And it has cells to spare. "We have seen this percolating demand for many years that we didn't sense other people saw," he says. "This company has prepared itself." Earnings per share are up 130% over the last 12 months.

Service Corporation International: North America’s largest provider of funeral and cemetery services. [Incidentally, Infosys did some key legacy-modernization work for SCI]. The company’s website says

“Through our network of more than 2,000 funeral homes and cemeteries, we serve hundreds of thousands of families each year at their time of need or on a preneed basis. As North Americas leading provider of death care services, SCI is poised to fulfill the needs of a population that now includes more persons over age 65 than at any time in history.”

Back to where I began musing. Most of us in the ‘white collared’ IT and consulting world would not know the intricacies of a ‘corrections system’ or their customers. Now, who exactly are the customers here: is it the guests of the state [prisioners], the state/Federal Government or both, I wonder? Same is the argument for the intricacies of a funeral / death care services business.

Just a thought: how many Management Consultants / Business Consultants from pure-play consulting firms would have experiential knowledge of the intricacies of the “Business” in the examples above. By the same argument, one could be intrigued about how one would explain the ‘Business’ of the illustrated organizations to an offshore team.

Morbid as the client’s business sounds, an Infosys team leveraged the GDM to successfully implement the program for SCI. One could argue that in the case in example quoted, was more of a ‘technical’ project, migrating applications to a .Net based solution.

Makes one wonder: are “business knowledge” “domain expertise” etc a bit more overrated than needed?

February 17, 2007

Open Source and Offshoring: Two Disruptive Forces Begin to Converge?

I was reading an interesting blog note Open source meets off-shoring where Steve Hamm comments on the recent announcement by the database company Ingress to go offshore “I think this is a significant announcement. It will make other players take heed--both on the open source software side and within the Indian tech industry.” Tom Berquist, CFO for Ingress is equally upbeat about the trend in his blog stating how the “Two Disruptive Forces Begin to Converge” Tom says:

When they work with our products they can get started immediately using the open source GPL license, without having to procure a commercial license. After they build and test the application (and fully understand the load characteristics) they can purchase database support subscriptions from us that tie directly to the number of servers they need to purchase. Nothing is wasted, and the software-related costs are deferred to the end of the project. This is a huge advantage to the customer and the services firm, and we believe that over the course of time all development will be done on open source technology even though some of the production deployment will continue to be done on commercial software.

Satyam's Sadagopan is naturally upbeat about the viewpoint. He blogs 'I particularly like the way Tom has captured the rationale behind the rise of the offshore service firms.'

Agreed that Open Source and Offshoring is a "potent combination" for businesses to pursue. However, I wonder what’s new in this announcement?

A few examples of how Infosys is managing and working on Open Source projects leveraging on the offshoring strengths:

On a personal note, I have also been working with clients in customizing open source solutions for their specific needs, in one instance helping cutting edge deployment of ServiceMix Enterprise Services Bus (ESB) and Apache Geronimo web server. I was ably supported by our offshore research team from SETLabs specializing in these and other technologies.

At the end of the day offshoring and open source frameworks are ‘business enablers’ that can help organizations leverage technologies to meet business goals. How you leverage the “Disruptive Forces” depends…Press releases and hoopla over offshoring and opensource aside…Proof of the pudding, as the adage goes, lies in the eating.

February 16, 2007

Outsourcing: Growing strong despite some weaknesses

Outsourcing is growing strong and organizations involved in this practice either want to maintain their sourcing level or want to increase it, according to a KPMG’s recent study, Strategic Evolution, based on responses from more than 650 organizations (both customers and services providers) from 32 countries.

Eighty-nine percent of respondents to the study say they plan to maintain or increase their present level of sourcing. “This industry is going to go much beyond where it is today” says Pradeep Udhas, Global Head, KPMG Advisory Services.

On contributions of service providers, customer respondents believe that service providers generally make positive contributions to the success of their organizations. Forty-seven percent of customers consider that their service providers brought experience to their business that they previously did not have.

Reflecting on the statement “as many as half of sourcing deals fail,” 62% believe that the statement is a gross or mostly an over simplification; 25% believe the statement is “not an oversimplification but nor entirely appropriate” and only 13% believe that it is an appropriate view.

But, interestingly, 72% of surveyed customers said that either they do not have a defined list of measurement criteria for evaluating success or they do not share them with their service providers.

On common problems in sourcing, interestingly, both customers and service providers said most problems are related to people. About 60% of respondents (customers and service providers) believe almost or mostly always problems are people related. Only 30% believe about half the problems are people related and half technology related; about 10% believe almost always or mostly problems are technology related.

While the survey reveals some positive aspects, it also exposes two significant weaknesses:

-  Lack of appropriate criteria or measures for assessing success of an outsourcing project

-  Problems in IT outsourcing mostly people related, not technology related

I believe both customers and service providers need to address these two weaknesses to make outsourcing/offshoring IT projects even more successful. So,

1.    What are the criteria for assessing success of an outsourced/offshored IT project, from customers’ as well as vendors’ perspectives? In other words, what are the measures of success?

2.   Which people-related problems are most common, and how those problems could be addressed?

Before we discuss these issues further in later blogs, let us gather your views: Do you generally agree with the survey findings? How would you address these issues?

Professor San Murugesan, Australia

February 14, 2007

Onsite Engagement Managers: Secrets of Offshoring Success?

In my previous job, working for a S&P 500 software company years ago, colleagues and I used to have a very nonchalant view of the job of account managers (alternatively known as Client Relationship Executives, Client Partners or Relationship Managers). The general perception among my techie colleagues was that those few roles at vendor organizations were a “known devil” whose main task was to renegotiate contract and rates with client managers, which in turn would translate to our bonuses. Of course that mindset was more prevalent in pure-play consulting -- a.k.a contracting / staff supplementation – and to some extent true of even turnkey contract projects.

Of course, the actual job involved much more than that. They also took on an element of P&L (Profit and Loss) responsibilities for accounts from the vendor’s end. The job also involved assisting HR with hiring consultants, ensuring that the fitment of consultants skills and clients needs was right and ensuring “customer satisfaction.” 

As years have gone by, and offshoring became more mainstream, the role of onsite Engagement Manager (EM) [a.k.a Account Manager, Relationship Manager] has undergone a big transition. Now, the role is being recognized as being nodal to success of offshore sourcing engagements.

My earlier blog on a similar topic -- “The Hottest Jobs in Information Technology: Offshore Project Manager” – generated a few comments and perspectives from folks in the field.

It is interesting how academic analysts are also beginning to articulate the value of this role in organizations. In answering a query on the “investment worth making” in bringing an engagement manager over from the vendor, Prof. Joseph Rottman, was quoted in a recent CIO magazine article [Secrets of Offshoring Success] stating

For many engagements it's a necessity. [The engagement manager] is the primary point of contact for the client's project managers. That person will work with both the onshore and offshore development teams. They can help mitigate some of the time zone risks, the knowledge transfer risks, the cultural risks. That person is a key piece to all of this.

But an engagement manager is an expensive employee to have onsite. It's usually a person with four to six years of experience managing projects and a lot of customer-facing duties. When managers are looking only at labor arbitrage and the delta between onshore and offshore rates, they don't want to throw in that onsite engagement manager.

The way I look at it, the role of a good EM is not that of just a Project Manager…their job is more akin to that of IT-Directors….-essentially Program Leaders who take ownership of the "Profit and Loss" (P&L). They are onsite leaders who take "bottom-line" on large offshored initiatives and engagements. 

February 13, 2007

Join the AD Forum on Offshoring IT

The conference series ENASE (Evaluation of Novel Approaches to Software Engineering)  attracted my attention. Its objective is to evaluate the claims made by new approaches to and schools of thought on software development, such as such as agile software development, aspect-oriented software development, component software, service-oriented architectures, evolutionary design, intentional software, and example centric programming. The conference series, in essence, provides a platform to ascertain whether their claim of novelty of these approaches is legitimate or just a new hype.

A special feature of the ENASE conferences is Advocatus Diaboli Forum (ADF)

The ADF is “directly inspired by an ancient, now discarded, mechanism within the Catholic Church whereby a so-called "Devil's Advocate" (AD) would assemble a prosecution case against candidates for canonization to sainthood. The AD was not required to necessarily believe the prosecution case they prepared, but was required to list every possible reason to reject the candidate's elevation. Proponents for canonization would then mount a defense, addressing each of the points raised by the AD. Likewise, in the ENASE AD Forum sessions, novel approaches to software engineering are tried in the Forum 'court' (Ref: CFP, Requirements Engineering Special Issue).”

I believe it would be both helpful and interesting to open an ADF forum on IT Offshoring.

You, as an "Devil's Advocate" (AD), may assemble prosecution case against one or more key issues or concerns on IT offshoring, or against various aspects of Offshored IT projects, on which the bloggers, collectively, can mount a defense, addressing each of the points raised by the AD. 

Your prosecution case, please!

 By Professor San Murugesan, Australia


February 12, 2007

Softer side of managing Software professionals

An article in today’s Wall Street Journal -- M.B.A. Programs Hone 'Soft Skills' – set me thinking about an aspect of managing software professionals. The article focuses extensively on "soft skills" and leadership for future managers, a topic that is very relevant for global IT managers too.

This is a topic I have mused about in the past. I had written about it in a column for Express Computers a few years ago and also dealt with extensively in my book. An abstract from my earlier article, that are still relevant today:

Apart from the technical skills and knowledge of IT systems, consultants need special focus in the following areas:
• Core technology skills: Most technology companies try to equip their employees with a variety of technologies and tools. By doing so, they can easily shift people around, based on project contingencies and business needs.  
• Team player and team management skills: Almost all IT projects require groups of people to work in a tandem, coordinating the efforts of team members spread across functional, technical, even geographic areas. This is especially true for projects worked for clients in the onsite/offshore model where a few people working at client sites co-ordinate the efforts of their peers halfway across the globe. Personal issues, differences in personalities and other issues have a way of creeping up if not identified and arrested. All members of the projects need to be trained to handle such issues, and communicate fluently and clearly.
• Project, program and systems management: Although project management is a specialised function in most organisations, with specialists working to co-ordinate projects, deadlines, etc; all members of IT teams need to be aware of the basics of project, program and systems management. Having an overview of the business process and the different pieces that need to fit in order to make a project successful, helps each member of the team to work towards the unified goals.
• Communications and cultural sensitivity: One of the most important aspects of working with people involves communication and cultural sensitivity. Communication includes oral, written and non-verbal communication, including body-language etc. This also includes moderating verbal accents and understanding accents of people from across the globe who speak English in different ways!
Most experts suggest that training be considered a continuous process and could involve a mix of some of the ideas suggested. Also, depending on the needs of the situation, specific training packages can be tailored to address the issues involved.

Obviously the points I made a few years ago continue to be an area of focus. And surely this is not going to be the last word.

February 9, 2007

Silver Bullet or not... XBRL is here

I have been following the trends in XML standardization with more than a bit of passing interest, especially as a number of organizations -- including our clients – continue to adopt standards for data interchange, including financial reporting and management.

Case in point is the Securities and Exchange Commission’s (SEC) announcement to invest $54 million to transform the agency’s 1980s-vintage public company disclosure system, that comes as a shot in the arm to organizations looking to bring further standardization to financial reporting. SEC’s release states “By moving to interactive data using the XBRL computer language, the SEC will be joining the FDIC, the Federal Reserve, and the Comptroller of the Currency, which already require banks to use it.”

Interestingly, although the move towards XBRL is going to be a technology focused initiative -- especially for organizations with more archaic IT systems -- business leaders are also taking note. In the Feb 2007 issue of Harvard Business Review featuring “Breakthrough Ideas for 2007,” the authors focus on talking up the trend, stating “Here Comes XBRL” [HBR says that the list is free to read for all of February]

What does this mean to us? Watch out for lot more business and tech leaders asking about XBRL (remember what SoX did to IT compliance?)

Bloggers are upbeat about the trend:
“I am a huge proponent of standards-based systems, including standardized computer languages.  XBRL will be just one more standard that resilient enterprises will put in their kit.” writes Enterprise Resilience Management Blog
Tech analyst Tom Foremski blogs about the HBR analysis stating “I also found #2, #9, #10, #11 and #14 fascinating.”

Of course, a note of caution to all techies and managers looking to jump on to the XBRL bandwagon….The authors of the HBR article themselves temper some moderation stating “by significantly reducing the amount of effort needed to change and integrate business reporting systems, XBRL will make digesting acquisitions, shedding businesses, reorganizing, and adding new products and business units far less difficult. All this undoubtedly sounds too good to be true to managers who are rightfully jaded after decades of false promises that the next IT silver bullet is (this time, really!) just around the corner.”
To this, I can almost hear my Architect colleagues murmur: is XBRL yet another Snake Oil Applied (SOA)?

While one can debate over the pace of adoption of XBRL, Infosys is certainly eating its own cooking, as the adage goes [Infosys participates in SEC's XBRL Voluntary Financial Reporting Program]: "Infosys is to be commended for its participation in the SEC's XBRL Voluntary Financial Reporting Program. The XBRL format enables investors to more effectively consume and analyze information in financial reports, providing enhanced report transparency and greater clarity in communications." said Mike Willis, Founding Chairman, XBRL International and Partner, PricewaterhouseCoopers

Footnote: For those curious about XBRL, check out further reading:
XBRL - Extensible Business Reporting Language: A royalty-free, open specification to describe financial information for public and private companies and other organizations.
Wikipedia: XBRL (eXtensible Business Reporting Language) is an emerging XML-based standard

February 3, 2007

Globalization and Offshoring of R & D .. further notes

A recent Hindustan Times headline proclaimed how "India centre engineers played key role, filed 40 patents for Vista" The article said:
While Bill Gates and his global team celebrated the launch of Microsoft Corp's much awaited Vista operating system in the Times Square and elsewhere in the world, the city of Charminar had its own reasons to exult.
Some 330 engineers in Microsoft's India Development Centre at Hyderabad engineered some of the most important features of the software — and filed 40 patents to prove that. Chief Executive Officer Steve Ballmer had during his visit to India in November taken time off to party with the engineers based in the Hi-Tec City complex. Five years ago,when Windows had launched Windows XP with 40 people involved from Hyderabad, it was a case of developing individual technologies in parts (for e.g. Internet Explorer) in India and integrating them with the global team from Redmond.

Well, articles like this just reinforce the point I was trying to make in my earlier blog  on how large organizations are globalizing research and development, leveraging skills and talent cutting across ‘time and space’ boundaries.

On a similar note, the recent Computerworld article on how ‘Microsoft, Infosys team on software engineering research’ makes a similar point:
“Infosys and Microsoft Research Lab India have already identified some areas for their joint research. The companies will, for example, work on tools and methodologies related to systems integration, said Sriram K. Rajamani, research manager at Microsoft Research Lab India, who heads the RSE group. Another area identified for research is tools to measure the performance of enterprise software even before it is built, he added.”  

If Microsoft goes global, you can bet Google is there too. A blogger observes how "Google has opened 30 R&D Centers in 3 Years(Wow!!!) which span across Europe, Russia, Eatern Europe, Israel, US, Canada, Australia, India, Japan and China"

Of course, not everyone sees the writing on the wall.  James McGovern, blogs about the Chinese angle, while Sharad Sharma is a more vocal in lamenting about how India shoring of R&D is going through a “trough of disillusionment” 

In my mind, the "India vs. China" arguments is moot since global business leaders care more about results ("what" and "how") and less about the location ("where"). The debate should be about the merits of offshoring R&D. The way I look at it, Globalization of R&D is enabling software and services companies to provide better solutions at a lower cost in the least time to market, leveraging a global skill pool.  Now, isn’t this at the heart of offshoring too?  Why get constrained by time-and-space boundaries, When ideation can happen anytime, anywhere?  

Given my past association with Infosys’ research collaboration with Microsoft [at SETLabs], you will continue to hear more on my two cents on this topic.

Parallel Development, Managing Version Control and Offshoring

Here is a challenge typical of that of many teams embarking on a globalization and offshoring journey.

The client is looking at having a low-cost but robust (around 400 developers would be working world-wide) solution primarily supporting the following features:
a. Parallel development by multiple teams
b. Remote check-out and check-in
c. Automatic Merge capabilities
d. Supporting automatic build and deployment processes
e. etc.

Though not exactly a ‘project management challenge,’ it is certainly the responsibility of the managers to ensure strong processes around source code management. As the Software Guru Martin Flower in his article  “Using an Agile Software Process with Offshore Development” states: I always advise teams to check their documents into a version control system so people can easily get the most up to date material. This is particularly important when you are doing remote work. Mark Murphy also articulates the "The Challenges of Remote Collaboration" in his blog, highlighting some key challenges:
Social issues also come into play. If the teams adopt an us versus them mindset, they might well wind up working at cross-purposes, with Team A being slow to adopt Team B's work due to distrust or outright disdain for who Team B is and what they are working upon. This is exacerbated by time zone and language differences that make real-time communication difficult.

A few version control tools - CVS, ClearCase, SubVersion, Microsoft Visual SourceSafe (and a remote access solution for VSS, SourceOffSite) come to mind. Of course, one can begin with a Wikipedia scan  or Software_Configuration_Management

Technology and nature of code and artifacts being versioned will determine selection of the tool, and of course a preference based on existing framework would be a key driver. But what tool is appropriate for Offshore development, or multi-site application development? Answer may be “it depends,”  especially since most offshore software development will also leverage remote access to common servers or repositories. This said, tools that have built-in remote access, tracking and management capabilities may lead the pack.

Before I open this thread for debate, here is an input from James Farley, a Principal Architects:
In terms of the client's requirements, I'd advise them that "automatic merge capabilities" are a pipe dream.  In my opinion, there's no such thing. It's almost like asking for a tool to automatically merge two documents edited by two people. Some person is going to have to do the merge, with assistance from the tool in terms of delta views, etc.

Well, is the client going to get a), b), c) and d)?