References
Advanced Development Methods, Inc. What is scrum? www.controlchaos.com/about/ (accessed May 31, 2009).
Ågerfalk, P. J. and B. Fitzgerald. 2006. Flexible and distributed software processes: Old petunias in new bowls. Communications of the ACM 49(10): 26–34.
Albrecht, A. J. 1979. Measuring application development productivity. Proceedings of the Joint SHARE, GUIDE, and IBM Application Development Symposium, pp. 83–92, Oct. 14–17, Monterey, CA.
Alessandra, Tony and Michael J. O’Connor. 1998. The platinum rule: Discover the four basic business personalities and how they can lead you to success. New York: Hachette Book Group-Grand Central Publishing.
ARCEP: L’Autorité de Régulation des Communications Régulation des Communications Électroniques et des Postes. www.arcep.fr/ (accessed May 22, 2009). Use Google to translate the page.
Aronoff, Stan. 1989. Geographic information systems: A management perspective. Ottawa, Canada: WDL Publications.
ASME. What’s your communication style? www.asme.org/Jobs/Manage/Whats_Communication_Style.cfm (accessed June 2, 2009).
Atkins, D., M. Handel, J. Herbsleb, A. Mockus, D. Perry, and G. Wills. 2001. Global software development: The Bell Labs collaboratory. Proceedings of the 23rd IEEE International Conference on Software Engineering, p. 0681b, May 12–19, Toronto, Canada. www.cs.uoregon.edu/~datkins/papers/icse-collab.pdf (accessed May 22, 2009).
Barbacci, M., M.H. Klein, T.A. Longstaff, and C.B. Weinstock. 1995. Quality attributes. Technical Report CMU/SEI-95-TR-021. Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University.
Baritault, Alain. 2009. Stimulating FTTH investments in France. MuniWireless, April 9. www.muniwireless.com/2009/04/09/stimulating-ftth-investments-in-france/ (accessed May 22, 2009).
Bar-On, D. and S. Tyszberowicz. 2007. Derived requirements generation: The DRAS methodology. Proceedings of the IEEE International Conference on Software-Science, Technology, and Engineering, pp. 116–126, Oct. 30–31, Herzlia, Israel.
Barry, E., C. Kemerer, and S. Slaughter. 2006. Environmental volatility, development decisions, and software volatility: A longitudinal analysis. Management Science 52(3): 448–464.
Bass, L., M. Klein, and G. Moreno. 2001. Applicability of general scenarios to the architecture tradeoff analysis method. Technical Report CMU/SEI-2001-TR-014. Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University.
Beck, Kent. 1999. Extreme programming explained: Embrace change. Boston: Addison-Wesley.
Beck, Kent, et al. 2001. Manifesto for agile software development. http://agilemanifesto.org/ (accessed May 22, 2009).
Bennatan, E.M. 2000. On time within budget: Software project management practices and techniques, 3rd ed. Hoboken, NJ: John Wiley & Sons.
Boehm, Barry W., Chris Abts, A. Winsor Brown, Sunita Chulani, Bradford K. Clark, Ellis Horowitz, Ray Madachy, Donald J. Reifer, and Bert Steece. 2000. Software cost estimation with Cococmo II. Upper Saddle River, NJ: Prentice Hall.
Borck, James R. 2006. The long road to RFID interoperability: The Gen2 standard means vendors and consumers finally have a common platform. InfoWorld, April 13. www.infoworld.com/t/platforms/long-road-rfid-interoperability-821 (accessed May 22, 2009).
Borland Software Corporation. 2006. Effective requirements definition and management: Improves systems and communication. Borland White Paper. www.borland.com/resources/en/pdf/solutions/rdm_whitepaper.pdf (accessed May 22, 2009).
Bourgault, M., N. Drouin, and E. Hamil. 2008. Decision making within distributed project teams: An exploration of formalization and autonomy as determinants of success. Project Management Journal (Special PMI Research Conference Ed.) 39(S1): S97-S100.
Brett, Jeanne M. 2001. Negotiating globally: How to negotiate deals, resolve disputes, and make decisions across cultural boundaries. San Francisco: Jossey-Bass.
British National Science Center (BNSC). 2008. Second Galileo satellite launched successfully, Ref. No. 03/08. www.bnsc.gov.uk/7235.aspx (accessed June 3, 2009).
Brooks, Frederick P. 1995. The mythical man-month: Essays on software engineering, anniversary ed. Reading, MA: Addison-Wesley.
BusinessDictionary.com. Definition of product management. www.businessdictionary.com/definition/product-management.html (accessed May 22, 2009).
Cao, L. and B. Ramesh. 2008. Agile requirements engineering practices: An empirical study. IEEE Software 25(1): 60–67.
Capretz, L. F. 2003. Personality types in software engineering. International Journal of Human-Computer Studies 58(2): 207–214.
Carmel, Erran. 1999. Global software teams: Collaborating across borders and time zones. Upper Saddle River, NJ: Prentice Hall.
Carmel, Erran and Paul Tjia. 2005. Offshoring information technology: Sourcing and outsourcing to a global workforce. Cambridge, UK: Cambridge University Press.
Carver, Charles S. and Michael F. Scheier. 2003. Perspectives on personality, 5th ed. Boston: Allyn & Bacon.
Carver, J.C., N. Naqappan, and A. Page. 2008. The impact of educational background on the effectiveness of requirements inspections: An empirical study. IEEE Transactions on Software Engineering 34(6): 800–812.
CBS Studios Inc. Star Trek Voyager. www.startrek.com/startrek/view/series/VOY/character/1112409.html (accessed May 22, 2009).
Cerf, V. G. and R.E. Kahn. 1974. A protocol for packet network intercommunication. IEEE Transactions on Communications 22(5): 637–648.
Ceschi, M., A. Sillitti, G. Succi, and S. De Panfilis. 2005. Project management in plan-based and agile companies. IEEE Software 22(3): 21–27.
ChangingMinds.org. Motivation theories. http://changingminds.org/explanations/theories/a_motivation.htm (accessed June 1, 2009).
Chapman, Chris and Stephen Ward. 2002. Managing project risk and uncertainty: A constructively simple approach to decision making. Hoboken, NJ: John Wiley & Sons.
Cleland, David and Lewis Ireland. 2007. Project manager’s handbook: Applying best practices across global industries. New York: McGraw-Hill Professional.
Clements, Paul and Linda Northrop. 2002. Software product lines: Practices and patterns. Boston: Addison-Wesley.
CMMI Product Team. 2002. Capability Maturity Model® Integration (CMMISM), version 1.1. Technical Report CMU/SEI-2002-TR-011. Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University.
Cohn, Mike. 2004. User stories applied: For agile software development. Boston: Addison-Wesley.
Ibid. 2006. Agile estimating and planning. Upper Saddle River, NJ: Prentice Hall.
Commander, Simon. 2005. The software industry in emerging markets. Cheltenham, UK: Edward Elgar Publishing.
Communications of the ACM 49(10), Oct. 2006. http://cacm.acm.org/magazines (accessed May 22, 2009).
Cox, K., J.G. Hall, and L. Rapanotti. 2005. A roadmap of problem frames research. Information and Software Technology, Special Issue on Problem Frames, eds. K. Cox and J. Hall, 47(14): 891–902.
Crosby, P.B. 1995. Quality is still free: Making quality certain in uncertain times, 2nd rev. ed. New York: McGraw-Hill.
Damian, D. 2007. Stakeholders in global requirements engineering: Lessons learned from practice. IEEE Software 24(2): 21–27.
Damian, D. and J. Chisan. 2006. An empirical study of the complex relationship between requirements engineering processes and other processes that lead to payoffs in productivity, quality, and risk management. IEEE Transactions on Software Engineering 32(7): 433–453.
Deleris, L.A., S. Bagchi, S. Kapoor, K. Katircioglu, R. Lam, and S. Buckley. 2007. Simulation of adaptive project management analytics. Proceedings of the 39th Conference on Winter Simulation: 40 years! The best is yet to come, pp. 2234–2240, Dec. 9–12, Washington, D.C.
DeMarco, Tom. 1982. Controlling software projects: Management, measurement, and estimates. Upper Saddle River, NJ: Prentice Hall.
Desouza, K.C. and J.R. Evaristo. 2004. Managing knowledge in distributed projects. Communications of the ACM 47(4): 87–91.
Dictionary.net. Definition of interaction. www.dictionary.net/interaction (accessed June 3, 2009).
Dillon, R.L. and C.H. Tinsley. 2008. How near-misses influence decision making under risk: A missed opportunity for learning. Management Science 54(8): 1425–1440.
Ebert, C. and J. De Man. 2005. Requirements uncertainty: Influencing factors and concrete improvements. Proceedings of the 27th International Conference on Software Engineering, pp. 553–560, St. Louis, MO.
Ebert, C. and A. Hickey. 2008. Requirements engineering—industry needs. Proceedings of the 16th IEEE International Conference on Requirements Engineering, p. 298, Sept. 8–12, Catalunya, Spain.
El-Azazy, Saad. Seismic bridge design improvements through research implementation. Sacramento, CA: California Department of Transportation (Caltrans). www.dot.ca.gov/hq/esc/earthquake_engineering/stap/Bridge_Design_Improvements_.pdf (accessed May 22, 2009).
Espinosa, J.A., S.A. Slaughter, R.E. Kraut, and J.D. Herbsleb. 2007. Familiarity, complexity, and team performance in geographically distributed software development. Organization Science 18(4): 613–630.
Finkenzeller, Klaus. 2003. RFID handbook: Fundamentals and applications in contactless smart cards and identification, 2nd ed. Hoboken, NJ: John Wiley & Sons.
Fowler, Martin. 2006. Using an agile software process with offshore development. www.martinfowler.com/articles/agileOffshore.html (accessed May 22, 2009).
Garfinkel, Simon and Beth Rosenberg. 2006. RFID: Applications, security, and privacy. Boston: Addison-Wesley.
Giesen, J. and A. Volker. 2002. Requirements interdependencies and stakeholders preferences. Proceedings of the IEEE Joint Conference on Requirements Engineering, pp. 206–209, Sept. 9–13.
Gluch, D. 1994. A construct for describing software development risks. Technical Report CMU/SEI-94-TR-014 Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University.
Goldratt, Eliyahu M. and Jeff Cox. 1992. The goal: A process of ongoing improvement, 2nd rev. ed. Great Barrington, MA: North River Press.
Graphical Development Process Assistant (GDPA Online). V Model of development. www.informatik.uni-bremen.de/gdpa/def/def_v/V_MODEL.htm (accessed May 22, 2009).
Gupta, Amar. 2009. Deriving mutual benefits from offshore outsourcing. Communications of the ACM 52(6): 122–126.
Gutierrez, E., O. Sandstrom, J. Janhager, and S. Ritzen. 2008. Innovation and decision making: Understanding selection and prioritization of development projects. Proceedings of the 4th IEEE International Conference on Management of Innovation and Technology, pp. 333–338, Sept. 21–24, Bangkok.
Hofstede, Geert. Cultural dimensions. www.geert-hofstede.com/ (accessed June 2, 2009).
Hull, Elizabeth, Kenneth Jackson, and Jeremy Dick. 2005. Requirements engineering, 2nd ed. London: Springer.
Humphrey, Watts S. 1989. Managing the software process. Reading, MA: Addison-Wesley.
Ibid. 2000. Introduction to the Team Software ProcessSM. Boston: Addison-Wesley.
Hussey, James M. and Steven E. Hall. 2007. Managing global development risk. Boca Raton, FL: Auerbach Publications.
IBM Systems Journal: Model-Driven Software Development, 45(3), 2006. www.research.ibm.com/journal/sj45-3.html (accessed June 17, 2009).
IEEE Std. 1058-1998. IEEE standard for software project management plans.
IEEE Std. 830-1998. IEEE recommended practice for software requirements specification.
IEEE Std.1061-1998. IEEE standard for a software quality metrics methodology – description.
IMDb.com. Groundhog Day. www.imdb.com/title/tt0107048/ (accessed May 22, 2009).
Ibid. Memorable quotes for Blazing Saddles. www.imdb.com/title/tt0071230/quotes (accessed May 22, 2009).
Ibid. Memorable quotes for Casablanca. www.imdb.com/title/tt0034583/quotes (accessed May 22, 2009).
ISO/IEC Std. 9126-1:2001. Software engineering—product quality—part 1: quality model.
Jackson, Michael. 2001. Problem frames: Analyzing and structuring software development problems. Boston: Addison-Wesley.
Ibid. 2005. Problem frames and software engineering. Information and Software Technology, Special Issue on Problem Frames, eds. K. Cox and J. Hall, 47(14): 903–912.
Jackson, M. and D. Jackson. 2006. Separating concerns in requirements analysis: An example. Springer Lecture Notes in Computer Science (LNCS), Special Issue on the Proceedings of the Workshop on the Rigorous Engineering of Fault-Tolerant Systems (REFT) 2005, eds. M. Butler, C. Jones, A. Romanovsky, and E. Troubitsyna, 4157: 210–225.
Jacobson, Ivar. 1992. Object-oriented software engineering: A use case driven approach. Reading, MA: Addison-Wesley.
Jensen, David G. Communication styles. http://searchmastersinternational.com/web/us/smi/en/pages/careers_career_dev_commun_styles.html (accessed June 2, 2009).
Johnson, Jim. 2006. My life is a failure: 100 things you should know to be a better project leader. Boston: The Standish Group.
Jones, T.O. and W.E. Sasser, Jr. 1995. Why satisfied customers defect. Harvard Business Review, Nov.–Dec.
Karolak, Dale W. 1998. Global software development: Managing virtual teams and environments. Hoboken, NJ: John Wiley & Sons.
Klein, Mark, Thomas Roya, Thomas Ralya, Bill Pollak, Ray Obenza, and Michael González Harbour. 1993. A practitioners’ handbook for real-time analysis: Guide to rate monotonic analysis for real-time systems. Boston: Kluwer Academic Publishers.
Krishnan, V. and K. Ulrich. 2001. Product development decisions: A review of the literature. Management Sciences 47(1): 1–21.
Kulak, Daryl and Eamonn Guiney. 2004. Use cases: Requirements in context, 2nd ed. Boston: Addison-Wesley.
Larman, C. and V.R. Basili. 2003. Iterative and incremental development: A brief history. Computer 36(6): 47–56.
Lee, G., W. Delone, and J. A. Espinosa. 2006. Ambidextrous coping strategies in globally distributed software development projects. Communications of the ACM 49(10): 35–46.
Leopold, George. 2000. U.S. ends degrading of GPS signals. EE Times, May 1. www.eetimes.com/story/OEG20000501S0065 (accessed May 22, 2009).
Lomer, Malcolm. 2007. Designing for a dual Galileo-based GPS system. EE Times, June 25. www.eetimes.com/showArticle.jhtml;jsessionid=0SC5IC2UFLXG2QSNDLRCKH0CJUNN2JVN?articleID=199905165 (accessed May 22, 2009).
Mangione, Carmine. 2003. Software project failure: The reasons, the costs. CIO Update, Jan. 3. www.cioupdate.com/reports/article.php/1563701/Software-Project-Failure-The-Reasons-The-Costs.htm (accessed June 3, 2009).
McConnell, Steve. 1997. Software project survival guide: How to be sure your first important project isn’t your last. Redmond, WA: Microsoft Press.
Ibid. 2006. Software estimation: Demystifying the black art. Redmond, WA: Microsoft Press.
McManus, J. 2004. A stakeholder perspective within software engineering projects. Proceedings of the IEEE International Engineering Management Conference, 2:880-884, Oct. 18–21, Singapore.
McManus, John and Trevor Wood-Harper. 2008. A study in project failure. www.bcs.org/server.php?show=ConWebDoc.19584 (accessed June 3, 2009).
Messerschmitt, D.G. 2004. Marketplace issues in software planning and design. IEEE Software 21(3): 62–70.
Microsoft Corporation. 2007. Enabling “people-ready processes” through business process management. www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=b047729c-4e94-40b1-ac55-ab728ba69921 (accessed May 22, 2009).
Mojtahedi, S.M.H., S.M. Mousavi, and A. Makoui. 2008. Risk identification and analysis concurrently: Group decision making approach. Proceedings of the 4th IEEE International Conference on Management of Innovation and Technology, pp. 299–304, Sept. 21–24, Bangkok.
Muñoz-Avila, H. and M.T. Cox. 2008. Case-based plan adaptation: An analysis and review. IEEE Intelligent Systems 23(4): 1541–1672.
National Institute of Standards and Technology (NIST). 2005. Security considerations for voice over IP systems, Special Publication 800–58. http://csrc.nist.gov/publications/nistpubs/800-58/SP800-58-final.pdf (accessed May 22, 2009).
National Park Service (US Dept. of the Interior). Glossary of common GPS terms. www.nps.gov/gis/gps/glossary.htm (accessed May 22, 2009).
Object Management Group (OMG). UML® resource page. www.uml.org/ (accessed June 17, 2009).
OGC (The U.K. Office of Government Commerce). PRINCE2. www.ogc.gov.uk/methods_prince_2__overview.asp (accessed May 22, 2009).
Overby, Stephanie. 2008. Remote controlled. CIO, April 1.
PDMA: Product Development and Management Association. 2006. The PDMA glossary for new product development. www.pdma.org/npd_glossary.cfm (accessed May 22, 2009).
Pfleeger, Shari L. and Atlee, Joanne M. 2006. Software engineering theory and practice, 3rd ed. Upper Saddle River, N.J.: Prentice Hall.
Pikkarainen, M., J. Haikara, O. Salo, P. Abrahamsson, and J. Still. 2008. The impact of agile practices on communication in software development. Empirical Software Engineering 13(3): 303–337.
Pollack-Johnson, B. and M. J. Liberatore. 2006. Incorporating quality considerations into project time/cost tradeoff analysis and decision making. IEEE Transactions on Engineering Management 53(4): 534–542.
Postel, J. 1980. IETF RFC 768: User Datagram Protocol. www.rfc-archive.org/getrfc.php?rfc=768 (accessed May 31, 2009).
Pressman, Roger S. 2004. Software engineering: A practitioner’s approach, 6th ed. New York: McGraw-Hill Science/Engineering/Math.
Princeton University. WordNet search—3.0. http://wordnetweb.princeton.edu/perl/webwn?s=estimate (accessed May 22, 2009).
Proceedings of the IEEE International Conference on RFID. http://ieeexplore.ieee.org/xpl/conhome.jsp?punumber=1001363 (accessed May 22, 2009).
Raja, U.A. 2009. Empirical studies of requirements validation techniques. Proceedings of the 2nd International Conference on Computer, Control and Communications, pp. 1–9, Feb. 17–28, Karachi, Pakistan.
Ramasubbu, N., S. Mithas, M.S. Krishan, and C. Kemerer. 2008. Work dispersion, process-based learning, and offshore software development performance. MIS Quarterly 32(2): 437–458.
Rational. 2001. Rational Unified Process: Best practices for software development teams. Rational Software White Paper TP026B, Rev. Nov. 1. www.ibm.com/developerworks/rational/library/content/03July/1000/1251/1251_bestpractices_TP026B.pdf (accessed May 22, 2009).
Reinhold, R. Articles on MBTI® applications & personality types: Practical business applications of the MBTI Myers-Briggs personality type model. www.personalitypathways.com/article/applications.html (accessed June 3, 2009).
RFID Journal. Glossary of RFID terms. www.rfidjournal.com/article/glossary/3 (accessed May 22, 2009).
Roberts, C.J., M.G. Richards, A.M. Ross, D.H. Rhodes, and D.E. Hastings. 2009. Scenario planning in dynamic multi-attribute tradespace exploration. Proceedings of the 3rd Annual IEEE Systems Conference, pp. 366–371, Mar. 23–26, Vancouver, B.C.
Rönkkö, K., Y. Dittrich, and D. Randall. 2005. When plans do not work out: How plans are used in software development projects. Computer Supported Cooperative Work 14(5): 433–468.
Rovira, Alex and Fernandos Trias de Bes. 2004. Winners make their own good luck. BusinessWeek, July 26. www.businessweek.com/smallbiz/content/jul2004/sb20040726_7503_sb022.htm (accessed May 22, 2009).
Royce, W.W. 1970. Managing the development of large software systems. Proceedings of IEEE WESCON, pp. 1–9, Aug., Monterey, CA.
Ibid. 1987. Managing the development of large software systems: Concepts and techniques. Proceedings of the 9th International Conference on Software Engineering, pp. 328–338, March 30–April 2, Monterey, CA.
Ruhe, G. and S.L. Pfleeger. 2007. Software engineering decision support. Proceedings of the 40th Annual Hawaii International Conference on Software Systems, p. 282, Jan. 3–6, Waikoloa, HI.
Ruhe, G. and M. Saliu. 2005. The art and science of software release planning. IEEE Software 22(6): 47–53.
Sangwan, Raghvinder, Matthew Bass, Neel Mullick, and Daniel J. Paulish. 2006. Global software development handbook. Boca Raton, FL: Auerbach Publications.
Schmidt, J.B., M.M. Montoya-Weiss, and A.P. Massey. 2001. New product development decision-making effectiveness: Comparing individuals, face-to-face teams, and virtual teams. Decision Sciences 32(4): 575–600.
Schneider, Geri and Jason P. Winters. 2001. Applying use cases: A practical guide, 2nd ed. Boston: Addison-Wesley.
SearchMobileComputing.com. Definitions: GPS (global positioning system). http://searchmobilecomputing.techtarget.com/sDefinition/0,,sid40_gci213986,00.html (accessed May 22, 2009).
SearchNetworking.com. Definitions: GNSS (global navigation satellite system). http://searchnetworking.techtarget.com/sDefinition/0,,sid7_gci827051,00.html (accessed May 22, 2009).
Ibid. Definitions: OSI reference model. http://searchnetworking.techtarget.com/sDefinition/0,,sid7_gci212725,00.html (accessed May 22, 2009).
Ibid. Definitions: packet-switched. http://searchnetworking.techtarget.com/sDefinition/0,,sid7_gci212737,00.html (accessed May 22, 2009).
Shakespeare, William. The tragedy of Hamlet: Prince of Denmark, Act 1, Scene 4. Original electronic source is Complete Moby Shakespeare. http://shakespeare.mit.edu/hamlet/hamlet.1.4.html (accessed May 28, 2009).
Shore, B. 2008. Systematic biases and culture in project failures. Project Management Journal 39(4): 5–16.
Software Engineering Institute. Software product lines. www.sei.cmu.edu/productlines/framework.html (accessed June 23, 2009).
Stellman, Andrew and Jennifer Greene. 2005. Applied software project management. Sebastopol, CA: O’Reilly.
Taimour, Al Neimat. 2005. Why IT projects fail. The Project Perfect White Paper Collection. www.projectperfect.com.au/info_it_projects_fail.php (accessed June 3, 2009).
Takeuchi, H. and I. Nonaka. 1986. The new new product development game. Harvard Business Review, Jan.1.
Tannen, Deborah. https://www9.georgetown.edu/faculty/tannend/ (accessed June 2, 2009).
TheFreeDictionary by Farlex. Definition of desirement. http://encyclopedia2.thefreedictionary.com/desirement (accessed May 22, 2009).
Ibid. Definition of plan. www.thefreedictionary.com/plan (accessed May 22, 2009).
Ibid. Definition of project. www.thefreedictionary.com/project (accessed May 22, 2009).
Thurston, Jeff. 2002. Galileo, GLONASS, and NAVSTAR: A report on GPS for GIS people. www.integralgis.com/pdf/GALILEO.pdf (accessed May 22, 2009).
T-REGS. 2008. France: FTTH law adopted and new ARCEP decisions, new access obligations. www.t-regs.com/content/view/395/1/ (accessed May 22, 2009).
Ullah, M.I. and G. Ruhe. 2006. Towards comprehensive release planning for software product lines. International Workshop on Software Product Management, pp. 51–56, Sept., Minneapolis, MN.
U.S. Department of Defense. 2007. DoD permanently discontinues procurement of global positioning system selective availability. News Release No. 1126–07, Sept. 18. www.defenselink.mil/releases/release.aspx?releaseid=11335 (accessed May 22, 2009).
U.S. Department of the Navy. EVM glossary. http://acquisition.navy.mil/acquisition_one_source/cevm/evm_glossary (accessed May 22, 2009).
Verine, Lev and Michael Trumper. 2007. Project decisions: The art and science. Vienna, VA: Management Concepts.
Verner, J.M. 2008. Quality software development: What do we need to improve in the software development process? Proceedings of the 6th International Workshop on Software Quality, pp. 1–2, Leipzig, Germany.
Wagstrom, P. and J. Herbsleb. 2006. Dependency forecasting in the distributed agile organization. Communications of the ACM 49(10): 55–56.
Wang, L. and L. Liu. 2007. Cultural barriers to the use of Western project management in Chinese enterprises: Some empirical evidence from Yunnan Province. Project Management Journal 38(3): 61–73.
Wang, Y., S.A. Mcllraith, Y. Yu, and J. Mylopoulos. 2007. An automated approach to monitoring and diagnosing requirements. Proceedings of the 22nd IEEE/ACM International Conference on Automated Software Engineering, pp. 293–302, Atlanta, GA.
Warkentin, M., R.S. Moore, E. Bekkering, and A.C. Johnston. 2009. Analysis of systems development project risks: An integrative framework. ACM SIGMIS Database 40(2): 8–27.
Wideman, Max. Max’s: Wideman comparative glossary of project management terms v3.1. www.maxwideman.com/pmglossary/PMG_E02.htm (accessed May 20, 2009).
Wiegers, Karl E. 2003. Software requirements, 2nd ed. Redmond, WA: Microsoft Press.
Ibid. 2006. More about software requirements: Thorny issues and practical advice. Redmond, WA: Microsoft Press.
Williams, R.C., G.J. Pandelios, and S.G. Behrens. 1999. Software Risk Evaluation (SRE) method description (version 2.0). Technical Report CMU/SEI-99-TR-029 Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University.
Xu, K. and H. Muñoz-Avila. 2008. CaBMA: A case-based reasoning system for capturing, refining, and reusing project plans. Knowledge and Information Systems 15(2): 215–232.