Lessons from India Inc.

By Gary H. Anthes, Computerworld |  Development Add a new comment

Once a sleepy pensioners' paradise, this city today is choked with traffic. Much of the greenery that gave Bangalore the nickname "Garden City" has been hacked away to make room for office towers, and people on the street cover their mouths and noses against the pollution. Telephones, water and electricity remain unreliable, and the roads and airports are decrepit, by Western standards.

But against the chaos of much of downtown Bangalore stands a shining symbol of India's aspiration to become a software superpower. The headquarters of Infosys Technologies Ltd., set on a 29-acre campus on the city's outskirts, is a group of gleaming multistory buildings containing development and test centers, classrooms, dormitories, an auditorium with a 40-screen video wall, sports facilities and two huge food courts that serve traditional southern Indian food and hot Domino's pizzas that are delivered to employees' desktops.

Founded in 1981 by six engineers armed with just $250 in loans from their wives, 8,900-employee Infosys in the first three quarters of last year earned a handsome $93 million on revenue of $293 million. The company [Nasdaq: INFY], today has a market capitalization of about $10 billion -- more than that of Computer Sciences Corp. and Sapient Corp. combined.

Infosys attributes much of its success to rigorous quality control. Indeed, software developers in India have made quality something of an obsession. Most developers here pursue and win the International Standards Organization (ISO) 9000 certification for excellence and then go on to climb the Capability Maturity Model (CMM) ladder. CMM is a product of the Software Engineering Institute (SEI), run by Carnegie Mellon University in Pittsburgh. It describes the practices that make for effective software development, and it lays out a five-level progression from ad hoc, chaotic processes to mature, disciplined approaches.

Quality at Any Cost?

There are several well-defined road maps to better software quality, such as the Capability Maturity Model (CMM) for software. But it's expensive to substantially improve existing software development processes, and sometimes U.S. managers believe the required investment just isn't worth it.

"Pragmatic executives are often reluctant to put up an investment that will take a year or two to pull off, and sometimes three or four years," says software quality expert Watts Humphrey.

Some U.S. companies have found it easier to make that investment in India rather than in the U.S., at least initially. Motorola set up a development center in India in 1993 when it found it hard to substantially improve its U.S. software practices, says Michael Cusumano, who was a consultant to Motorola at the time.

"The CMM demands lots of documentation and traceability procedures, very intensive quality assurance procedures and process support people, so there's a lot of resistance from managers," he says. "But setting up a facility from scratch and introducing the right practices from the very beginning is a good way to get a software development organization to a very high level."

A few years later, Motorola imported those high-quality practices back to its U.S. development centers, but it was slow going and required tailoring the CMM for smaller teams, says Cusumano, now a professor of management at MIT's Sloan School of Management in Cambridge, Mass.

Implementing stringent quality disciplines such as CMM isn't easy to do in large, well-established IT organizations, says Satish Bangalore, chief technology officer at Phoenix Home Life Mutual Insurance. "When you are talking of an IT organization that is 30 years old, you are talking of an organization that is carrying a lot of baggage," he says. "It's hard to instill new discipline unless there is a very strong survival necessity."

CMM principles originated at IBM for use in developing operating systems and complex applications for its Federal Systems Division, Cusumano says. "The CMM is really designed for large, bureaucratic types of industrial organizations," he says. "In a lot of software markets, time to market and process flexibility are more important than quality."

Of the 42 organizations worldwide that have reached Level 5 on the CMM scale, 25 are based in India, according to the SEI.

Relatively few software shops in the U.S. seem prepared to invest the considerable time and effort needed to reach those lofty levels, but there's much they could learn from Indian developers, such as how to improve software quality by measuring and analyzing defects, rework costs and estimation accuracy. And software quality experts say the payoff isn't just in less-buggy software but in big productivity gains as well.

    Add a comment

    Post a comment using one of these accounts
    Or join now
    At least 6 characters

    Note: Comment will appear soon after you have activated your account.
    Obscene/spam comments will be removed and accounts suspended.
    The information you submit is subject to our Privacy Policy and Terms of Service.

    ITworld LIVE

    DevelopmentWhite Papers & Webcasts

    White Paper

    HP NonStop SQL Fundamentals whitepaper

    This whitepaper offers a detailed look into the fundamentals of HP NonStop SQL solutions. See how this system delivers unprecedented levels of application availability with fail-safe data integrity and meets the needs of enterprises with large-scale business critical applications.

    White Paper

    Nebraska Medical Center case study

    See how the Nebraska Medical Center implemented a SQL solution to make information more readily available to streamline operations, improve patient care and facilitate medical research with an enterprise solution running on HP NonStop servers.

    White Paper

    Concepts of NonStop SQL/MX

    For DBAs and developers who are familiar with Oracle solutions and want to learn about NonStop SQL/MX, this whitepaper provides an overview of the similarities and differences between the two products-with a specific focus on implementation.

    White Paper

    6 Things Your CIO Needs to Know About Requirements

    If your organization is not predictably successful on technology projects, there is likely an issue in requirements. CIOs must take action and own requirements maturity improvement. There are 6 main things a CIO must know about requirements.

    Webcast On Demand

    User Experience Monitoring

    In this webinar, you will learn hints & tips for improving end-user response times from Forrester Research analyst, Jean-Pierre Garbani.

    Sponsor: Nimsoft

    See more White Papers | Webcasts

    Ask a question

    Ask a Question