Managing and Leading Software Projects

Managing and Leading Software Projects

Volumn , Issue , 2008, Pages 1-492

  Fairley, Richard E ^a  

^a NONE

Author keywords

[No Author keywords available]

Indexed keywords

EID: 84889408135     PISSN: None     EISSN: None     Source Type: Book    
DOI: 10.1002/9780470405697     Document Type: Book

References (145)

1. Brooks, F. P. The Mythical Man-Month. Addison Wesley, 1995.
2. SEI. CMMI ® Models and Modules. http://www.sei.cmu.edu/cmmi/models/, 2006.
3. IEEE Std 1058 ™-1998 IEEE Standard for Software Project Management Plans. IEEE Press, New York, 1998. Also in Engineering Standards Collection. IEEE Product: SE113. Institute of Electrical and Electronic Engineers, August 2003.
4. Industry Implementation of International Standard ISO/IEC 12207:1995 Standard for Information Technology-Software Life Cycle Processes. IEEE/EIA 12207.0/.1/.2-1996 (March), IEEE Press, New York, 1996. Also in Engineering Standards Collection. IEEE Product: SE113. Institute of Electrical and Electronic Engineers, August 2003.
5. Jackson, M. Descriptions in Software Development. Lecture Notes in Computer Science. Springer Verlag, 2002.
6. PMI, A Guide to the Project Management Body of Knowledge, 3rd ed. (PMBOK ® Guide). Project Management Institute, 2004.
7. Youker, R. Organizational alternatives for project managers. Project Management Quarterly, Vol. VIII, No. 1, (March 1977).
8. Bass, L., P. Clements, and R. Kazman. S oftware Architecture in Practice, 2nd ed. Addison-Wesley, 2003.
9. Boehm, B., and R. Turner. Balancing Agility and Discipline. Addison Wesley, 2004.
10. Boehm, B. Software Engineering Economics. Prentice Hall, 1981, p. 40.
11. Boehm, B. A Spiral model of software development and enhancement. Computer, May 1988, IEEE. SEI. CMMI ® Models and Modules, http://www.sei.cmu.edu/cmmi/models/, 2006.
12. IEEE Std 1058 ™-1998 IEEE Standard for Software Project Management Plans. Engineering Standards Collection. IEEE Product: SE113. Institute of Electrical and Electronic Engineers, August 2003.
13. IEEE/EIA 12207.0/.1/.2. Industry Implementation of International Standard ISO/IEC 12207:1995 Standard for Information Technology-Software Life Cycle Processes. Engineering Standards Collection. IEEE Product: SE113. Institute of Electrical and Electronic Engineers, August 2003.
14. PMI. A Guide to the Project Management Body of Knowledge, 3rd ed. (PMBOK ® Guide). Project Management Institute, 2004.
15. Royce, W. Managing the development of large software systems: Concepts and techniques. IEEE WESCON, 1970 ; reprinted in the Proceedings of the 9th International Conference on Software Engineering, Monterey, CA. ACM Press, 1987.
16. Schwaber, Ken. Agile Project Management with Scrum. Microsoft Press, 2004.
17. CMMI for Acquisition, Version 1.2 Model. http://www.sei.cmu.edu/publications/documents/07.reports/07tr017.html.
18. Boehm, B. Software Engineering Economics. Prentice Hall, 1981.
19. CMMI ® Models and Modules. http://www.sei.cmu.edu/cmmi/models/, 2006.
20. CMMI Acquisition Module (CMMI-AM), Version 1.1. http://www.sei.cmu. edu/publications/documents/05.reports/05tr011.html.
21. Software Acquisition Maturity Model, Version 1.03, http://www.sei.cmu.edu/arm/SA-CMM.html, 2002.
22. Cohen, L. Quality Function Deployment. Prentice Hall, 1995.
23. Davis, A. The art of requirements triage. IEEE Computer, March 2003.
24. Hayes, J. Building a requirement fault taxonomy: Experiences from a NASA verification and validation research project. Proceedings of the IEEE International Symposium on Software Reliability Engineering (ISSRE). Denver, CO, November 2003 IEEE Computer Society.
25. IEEE Std 830 ™-1998. IEEE Recommended Practice for Software Requirements Specifications. IEEE Software Engineering Standards Collection. IEEE Product SE113. Institute of Electrical and Electronic Engineers, August 2003.
26. IEEE Std 1362 ™-1998. IEEE Guide for Information Technology-System Definition-Concept of Operations (ConOps) Document. Software Engineering Standards Collection. IEEE Product SE113. Institute of Electrical and Electronic Engineers, August 2003.
27. IEEE/EIA 12207.0/.1/.2. Industry Implementation of International Standard ISO/IEC 12207:1995 Standard for Information Technology-Software Life Cycle Processes. Engineering Standards Collection. IEEE Product SE113. Institute of Electrical and Electronic Engineers, August 2003.
28. Leffingwell, D., and D. Ledwig. Managing Software Requirements: A Use Case Approach. Addison-Wesley, 2003.
29. The Delphi Method, Mindtools, 1995. http://www.mindtools.com/pages/article/newTMC_95.htm.
30. PMI. A Guide to the Project Management Body of Knowledge, 3rd ed. (PMBOK ® Guide). Project Management Institute, 2004.
31. Robertson, S., and J. Robertson. Mastering the Requirements Process. Addison-Wesley, 2006.
32. Rumbaugh, J., I. Jacobson, and G. Booch. The Unified Modeling Language Reference Manual. Addison-Wesley, 1998.
33. Saaty, T. T heory and Applications of the Analytic Network Process: Decision Making with Benefits, Opportunities, Costs, and Risks. RWS Publications, 2005.
34. Weigers, K. Software Requirements. Microsoft Press, 2003.
35. Boehm, B., and R. Turner. Balancing Agility and Discipline. Addison Wesley, 2004.
36. SEI, CMMI ® Models and Modules. http://www.sei.cmu.edu/CMMI/models/, 2006.
37. IEEE Std 1058 ™-1998. IEEE Standard for Software Project Management Plans. Engineering Standards Collection. IEEE Product: SE113. Institute of Electrical and Electronic Engineers, August 2003.
38. IEEE/EIA 12207.0/.1/.2. Industry Implementation of International Standard ISO/IEC 12207:1995 Standard for Information Technology-Software Life Cycle Processes. Engineering Standards Collection. IEEE Product: SE113. Institute of Electrical and Electronic Engineers, August 2003.
39. A Guide to the Project Management Body of Knowledge, 3rd ed. (PMBOK ® Guide). Project Management Institute, 2004.
40. SEI, Software Acquisition Capability Maturity Model (SA-CMM), Version 1.03. http://www.sei.cmu.edu/publications/documents/02.reports/02tr010.html
41. Bass, L., P. Clements, and R. Kazman. S oftware Architecture in Practice, 2nd ed. Addison Wesley, 2003.
42. SEI, CMMI ® Models and Modules. http://www.sei.cmu.edu/CMMI/models/, 2006.
43. Conway, M. E. " How Do Committees Invent? " Datamation (April 1968). Vol. 14, No. 4, pp. 28-31.
44. IEEE Std 1058 ™-1998. IEEE Standard for Software Project Management Plans. Engineering Standards Collection. IEEE Product: SE113. Institute of Electrical and Electronic Engineers, August 2003.
45. IEEE/EIA 12207.0/.1/.2. Industry Implementation of International Standard ISO/IEC 12207:1995 Standard for Information Technology-Software Life Cycle Processes. Engineering Standards Collection; IEEE Product: SE113. Institute of Electrical and Electronic Engineers, August 2003.
46. A Guide to the Project Management Body of Knowledge, 3rd ed. (PMBOK ® Guide). Project Management Institute, 2004.
47. Walz, D. B., J. Elam, and B. Curtis. Inside a software design team: Knowledge acquisition, sharing, and integration. Communications of the ACM, 36 (October 1993). pp. 63-67.
48. Albrecht, A. J. Measuring application development productivity. Proceedings of the IBM Application Development Symposium, Monterey, California, October 1979, pp. 83-92.
49. Boehm, B. Software Engineering Economics. Prentice Hall, 1981.
50. Boehm, B., and W. Royce. TRW IOC Ada COCOMO: Definitions and Refinements. Proceedings of the Third International COCOMO Users Group. Software Engineering Institute, 1987.
51. Boehm, B. et al. Software Cost Estimation with COCOMO II. Prentice Hall, 2000.
52. Brooks, F. The Mythical Man-Month. Addison Wesley, 1995.
53. SEI. CMMI ® Models and Modules. http://www.sei.cmu.edu/cmmi/models/, 2006.
54. DeMarco, T., and T. Lister. Peopleware, 2nd ed. Dorset, 1999.
55. Fairley, R. Making accurate estimates. IEEE Software. 19 (November-December): 61-63.
56. Fairley, R. The influence of COCOMO on software engineering education and training. Journal of Systems and Software 80 (August 2007): pp. 1201-1208.
57. Forrester, J. W. Industrial Dynamics. Pegasus Communications, 1961.
58. Abdul-Hamid, T. K., and Madnick, S. E. Software Project Dynamics. Prentice Hall, 1991.
59. IEEE Std 1058 ™-1998. IEEE Standard for Software Project Management Plans. Engineering Standards Collection. IEEE Product: SE113. Institute of Electrical and Electronic Engineers, August 2003.
60. IEEE/EIA 12207.0/.1/.2. Industry Implementation of International Standard ISO/IEC 12207:1995 Standard for Information Technology-Software Life Cycle Processes. Engineering Standards Collection. IEEE Product: SE113. Institute of Electrical and Electronic Engineers, August 2003.
61. www.ifpug.org.
62. Jalote, P. Software Project Management in Practice. Addison Wesley, 2002.
63. Jones, T. C. The SPR feature point method. Software Productivity Research, Inc., 1986.
64. Jones, C. Software cost estimation in 2002. Crosstalk. Software Technology Support Center, June, 2002.
65. Norden, P. Useful tools for project management. Operation Research in Research and Development, edited by B. V. Dean. Wiley, 1963.
66. PMI. A Guide to the Project Management Body of Knowledge, 3rd ed. (PMBOK ® Guide) Project Management Institute, 2004.
67. Putnam, L., and W. Myers. Measures for Excellence. Yourdon Press, 1992.
68. Sackman, H., W. Erikson, and E. Grant. Exploratory Experimental Studies Comparing On-line and Off-line Performance. Communication of the ACM. 11 (January 1968). pp. 93-105.
69. Symons, C. R. Function point analysis: Difficulties and improvements. IEEE Transactions in Software Engineering. 14 (January 1988). pp. 2-11.
70. Basili, V., G. Caldiera, and H. D. Rombach. The goal question metric approach. Encyclopedia of Software Engineering. Wiley, 1994, pp. 528-532.
71. Bass, L., P. Clements, and R. Kazman. S oftware Architecture in Practice, 2nd ed. Addison Wesley, 2003.
72. Belady, L., and M. Lehman. A model of large program development. IBM Systems Journal 15 (3): 225-252, 1976.
73. Boehm, B., C. Abts, A. Brown, S. Chulani, B. Clark, E. Horowitz, R. Madachy, D. Reifer, and B. Steece. S oftware Cost Estimation with COCOMO II. Prentice Hall, 2000
74. Bush, M. Inspection results at JPL. Proceedings of 10th International Conference on Software Engineering. IEEE Computer Society Press, 1998.
75. IEEE Std 1058 ™-1998. IEEE Standard for Software Project Management Plans. Engineering Standards Collection, IEEE Product: SE113. Institute of Electrical and Electronic Engineers, August 2003.
76. IEEE/EIA 12207.0/.1/.2. Industry Implementation of International Standard ISO/IEC 12207:1995 Standard for Information Technology-Software Life Cycle Processes. Engineering Standards Collection. IEEE Product: SE113. Institute of Electrical and Electronic Engineers, August 2003.
77. Kulak, D., and E. Guiney. U se Cases: Requirements in Context, 2nd ed. A ddison Wesley, 2003.
78. McCabe, T. A complexity measure. IEEE Transactions on Software Engineering 2 (December 1976): 308-320.
79. Mala, Y. K., and J. Denton. What do the software reliability growth model parameters represent? Proceedings of the 8th International Symposium on Software Reliability Engineering. IEEE Press, November 1997.
80. Myers, G., and L. Constantine. Structured design. IBM Systems Journal 13 (February 1974): 115-139.
81. PMI. A Guide to the Project Management Body of Knowledge, 3rd ed. (PMBOK ® Guide). Project Management Institute, 2004.
82. Roedler, G. J., and C. Jones. Technical Measurement: A Collaborative Report of PSM, INCOSE, and Industry. INCOSE-TP-2003-020-01, Version 1.1 (27 December 2005). Available at http://www.psmsc.com/Downloads/Technology Papers/TechnicalMeasurementGuide_v1.0.pdf.
83. Rumbaugh, J., I. Jacobron, and G. Booch. The Unified Modeling Language Reference Manual, 2nd ed. Addison Wesley, 2005.
84. Russell, G. Experience with inspection in ultralarge-scale developments. IEEE Software vol. 8, No. 1. (January 1991). pp. 25-31.
85. Basili, V., and S. Green. Software process evolution at the SEL. IEEE Software (July 1994): 58-66.
86. Boehm, B., and V. Basili. Software defect reduction top 10 list. Computer (January 2001): 135-137.
87. DeMarco, T. Controlling Software Projects. Yourdon Press, 1982.
88. Fairley, R. E., and M. J. Willshire. Iterative rework in software development: The good, the bad, and the ugly. IEEE Computer (September 2005). Vol. 38, No. 9. pp 34-41.
89. IEEE Std 1058 ™-1998. IEEE Standard for Software Project Management Plans. Engineering Standards Collection. IEEE Product. SE113. Institute of Electrical and Electronic Engineers, August 2003s.
90. IEEE/EIA 12207.0/.1/.2. Industry Implementation of International Standard ISO/IEC 12207:1995 Standard for Information Technology-Software Life Cycle Processes. Engineering Standards Collection. IEEE Product: SE113. Institute of Electrical and Electronic Engineers, August 2003.
91. Boehm, B. W. Software risk management: Principles and practices. IEEE Software (January 1991). vol. 8, No. 1. pp 32-41.
92. Carr, M. J., et al. Taxonomy-Based Risk Identification. www.sei.cmu.edu/pub/documents/93.reports/pdf/tr06.93.pdf, 1993.
93. SEI. CMMI ® Models and Modules. http://www.sei.cmu.edu/cmmi/models/, 2006.
94. Davis, A. The art of requirements triage. IEEE Computer (March 2003). Vol. 32, No. 3. pp 42-49.
95. Fairley, R. E. Risk management for software projects. IEEE Software (May 1994). vol. 11, No. 3, pp 57-67.
96. Fairley, R., and P. Rook. Risk management for software development. IEEE Tutorial on Software Engineering. IEEE Computer Society, 1996. pp 387-400.
97. Fairley, R. E. Software risk management glossary. IEEE Software (May/June 2005). Vol. 22, No. 3, pp 101.
98. IEEE Std 1058 ™-1998. IEEE Standard for Software Project Management Plans. Engineering Standards Collection. IEEE Product: SE113. Institute of Electrical and Electronic Engineers, August 2003.
99. IEEE/EIA 12207.0/.1/.2. Industry Implementation of International Standard ISO/IEC 12207:1995 Standard for Information Technology-Software Life Cycle Processes. Engineering Standards Collection. IEEE Product: SE113. Institute of Electrical and Electronic Engineers, August 2003.
100. IEEE Std 1540 ™-2001. IEEE Standard for Software Life Cycle Processes-Risk Management, Engineering Standards Collection. IEEE Product: SE113. Institute of Electrical and Electronic Engineers, August 2003.
101. PMI. A Guide to the Project Management Body of Knowledge, 3rd ed. (PMBOK ® Guide). Project Management Institute, 2004.
102. http://www.value-eng.org/.
103. Boeree, G. C. Assessment. Personality Theories. http://www.ship.edu/%7Ecgboeree/jung.html, 2006.
104. Brooks, F. W. No silver bullets: Essence and accidents of software engineering. IEEE Computer (April 1987) Vol. 20, No. 4. pp 10-19.
105. Brooks, F. W. The Mythical Man-Month. Addison Wesley, 1995.
106. SEI. CMMI ® Models and Modules. http://www.sei.cmu.edu/cmmi/models/, 2006.
107. Curtis, B., H. Krasner, and N. Iscoe. A field study of the software design process for large systems. CACM. Vol. 31, No. 11, November 1988. pp 1259-1267.
108. Curtis, B., W. Hefley, and S. Miller. People Capability Maturity Model Guidelines for Improving the Workforce. Addison Wesley, 2001.
109. DeMarco, T. Controlling Software Projects. Yourdon Press, 1982.
110. Demarco, T., and T. Lister. Peopleware, Productive Projects and Teams, 2nd ed. Dorset Publishing, 1999.
111. Grove, A. S. High Output Management. Vintage Books, 1995.
112. Hammer, A. L. Myers-Briggs Type Indicator Work Styles Report. Consulting Psychologists Press. 2001. http://www.cpp.com/images/reports/smp261182. pdf.
113. Hardiman, L. T. Personality types and software engineers. IEEE Computer (October, 1997) Vol. 30, No. 10. pp 10.
114. Hershey, P., and K. H. Blanchard. Leadership and the One Minute Manager. William Morrow, 1999.
115. Humphrey, W. S. Introduction to the Personal Software Process. Addison Wesley, 1997.
116. Humphrey, W. S. Introduction to the Team Software Process. Addison Wesley, 2000.
117. IEEE Std 1058 ™-1998. IEEE Standard for Software Project Management Plans. Engineering Standards Collection. IEEE Product: SE113. Institute of Electrical and Electronic Engineers, August 2003.
118. IEEE/EIA 12207.0/.1/.2, Industry Implementation of International Standard ISO/IEC 12207:1995 Standard for Information Technology-Software Life Cycle Processes, Engineering Standards Collection; IEEE Product: SE113, The Institute of Electrical and Electronic Engineers, Inc. August, 2003.
119. Jung, C. W. Psychological Types. Pantheon Books, 1923 (English translation H. Godwyn Baynes).
120. Katzenbach, J., and D. Smith. The Wisdom of Teams. Harvard Business School Press, 1993.
121. Machiavelli, N. The Prince. Bantam classics, 1984.
122. McConnell, S. After the Gold Rush. Microsoft Press, 1999.
123. McGregor, D. The Human Side of Enterprise. McGraw-Hill. 1985.
124. Miller, A. Death of a Salesman. Penguin, [1949] 1998.
125. PMI. A Guide to the Project Management Body of Knowledge, 3rd ed. (PMBOK ® Guide). Project Management Institute, 2004.
126. Wideman, R. M. Project teamwork, personality profiles and population at large: Do we have enough of the right kind of people? Proceedings of the 29th Annual Project Management Institute Seminar/Symposium, Long Beach, CA, Project Management Institute 1998. Also available at http://www. maxwideman.com/papers/profiles/profiles.pdf.
127. Wilson, L. The Social Styles Handbook: Find Your Comfort Zone and Make People Feel Comfortable with You, Wilson Learning Library, 2004. Also available at http://portalcenter.wilsonlearning.com.
128. Wurster, C. W. Myers-Briggs Type Indicator: A Cultural and Ethical Evaluation. National Defense University, Washington, DC, 1993. Also available at http://www.ndu.edu/library/ic6/93S86.pdf.
129. Baker, F. T. Chief programmer team management of structured programming. IBM Systems Journal. 11 (1): 1972, pp. 56-73.
130. Boehm, B. W. Tutorial: Software Risk Management. Computer Society Press, 1989.
131. Brooks, F. W. No silver bullets: Essence and accidents of software engineering. IEEE Computer (April 1987). 20 (4), pp. 10-19.
132. SEI. CMMI ® Models and Modules. http://www.sei.cmu.edu/cmmi/models/,2006.
133. Conway, M. How do committees invent? Datamation (April): 1968. 14 (2), pp. 28-31.
134. DeMarco, T. Controlling Software Projects. Yourdon Press, 1982.
135. Demarco, T., and T. Lister. Peopleware. Dorset Publishing, 1999.
136. Fairley, R. E., and M. J. Willshire. Iterative rework in software development: The good, the bad, and the ugly. IEEE Computer (September 2005). 38 (9), pp. 34-41.
137. Fairley, R. E., Organizing and leading software engineering teams. International Perspectives in Software Engineering. Rocky Mountain Institute of Software Engineering, 1993.
138. Hardgrave, B. C., and D. J. Armstrong. Software process improvement: It ' s a journey, not a destination. Communication of the ACM. Vol. 48, No. 1, November, 2005. pp. 219-228.
139. IEEE Std 1058TM-1998. IEEE Standard for Software Project Management Plans. Engineering Standards Collection. IEEE Product: SE113. Institute of Electrical and Electronic Engineers, August 2003.
140. IEEE/EIA 12207.0/.1/.2. Industry Implementation of International Standard ISO/IEC 12207:1995 Standard for Information Technology-Software Life Cycle Processes. Engineering Standards Collection. IEEE Product: SE113. Institute of Electrical and Electronic Engineers, August 2003.
141. Katzenbach, J. R., and D. K. Smith. The Wisdom of Teams: Creating the High-Performance Organization. Harper Collins, 2003.
142. Machiavelli, N. The Prince. Bantam Classics. 1984.
143. PMI. A Guide to the Project Management Body of Knowledge, 3rd ed. (PMBOK ® Guide). Project Management Institute, 2004.
144. Stewart, T. Intellectual Capital. Doubleday Publishing, 1997.
145. Webb, A. Using Earned Value. A Project Manager ' s Guide. Gower Publishing, 2003