Page 341 - Global Project Management Handbook
P. 341

16-28         MANAGEMENT OF GLOBAL PROGRAMS AND PROJECTS

           One effective way to overcome these problems and produce successful VGS projects
        is to build a system of critical success factors that is sufficiently flexible to account for
        the specifics of the various projects. This system consists of eight interdependent strate-
        gic success factors, each of them including several tactical factors. The point of the
        strategic factors is that in successful VGS projects one needs to perform the alignment
        (strategic factor one) of VGS projects with the business strategy, which will direct the
        shaping of the project strategy (strategic factor two), which, then, will drive the project
        organization, people, and culture (strategic factors three, four, and five). These three dic-
        tate the design of the project process (strategic factor six) that shapes up the use of project
        tools and metrics (strategic factors seven and eight). Together these eight strategic suc-
        cess factors, supported by 20+ tactical success factors, deliver successful VGS projects.




        REFERENCES

        Allen TJ. 1997. Managing the Flow of Technology. Cambridge, MA: MIT Press.
        Baskerville R, Pries-Heje J. 1999. Knowledge capability and maturity in software management.
         Database Adv Inform Syst 30(2):26–43.
        Battin RD, Crocker R. Kreidler J. et al. 2001. Leveraging resources in global software develop-
         ment. IEEE Software 18(2):70–77.
        Behravesh N. 2004. The Impact of Offshore IT Software and Services Outsourcing on the U.S.
         Economy and the IT Industry. Information Technology Association of America (ITAA).
         Arlington, Virginia.
        Berinato S. 2001. The secret to software success. CIO 14(18):76–82.
        Bowen S, Maurer F. 2002. Using Peer-to-peer Technology to Support Global Software
         Development: Some Initial Thoughts. Orlando, FL: International Workshop on Global Software
         Development.
        Brooks FP. 1987. No silver bullet: essence and accidents of software engineering. IEEE
         Computer 20(4):10–19.
        Carmel E. 1999. Global Software Teams. Upper Saddle River, NJ: Prentice-Hall.
        Carmel E, Agarwal R. 2001. Tactical approaches for alleviating distance in global software
         development. IEEE Software 18(2):22–29.

        Clark KB, Wheelwright SC. 1993. Managing New Product and Process Development Text and
         Cases. San Francisco: Free Press.
        Cooper RG. 1994. Debunking the myths of new product development. Res Technol Manag
         37(4):40–50.
        Curtis B, Krasner H, Iscoe N. 1988. A field study of the software design process for large systems.
         Commun ACM 31(11):1268–1287.
        Damian D. 2002. The Study of Requirements Engineering in Global Software Development: As
         Challenging as Important. Orlando, FL: International Workshop on Global Software
         Development.
        Dow Jones & Co., Inc. 2003. High-tech sector reduced work force by 10 percent in 2001–2002.
         Wall Street Journal, March 19, p. 1.
        Findley DA. 1998. Controlling Costs for a Software Development Project (No. PC.04).
         Morgantown, WV: AACE International.
        Gorton I, Motwani s. 1996. Issues in co-operative software engineering using globally distributed
         teams. Inform Software Technol 38:647–655.
        Gupta AK, Wilemon DL. 1990. Accelerating the development of technology-based new prod-
         ucts. Calif Manag Rev Winter:24–44.
   336   337   338   339   340   341   342   343   344   345   346