[bib01_001] Austin, Robert D. 1996. Measuring and Managing Performance in Organizations. New York: Dorset House Publishing.

[bib01_002] Basili, Victor R., and H. Dieter Rombach. 1988. "The TAME Project: Towards Improvement-Oriented Software Environments." IEEE Transactions on Software Engineering. 14(6): 758–773.

[bib01_003] Boddie, John. 1995. "Growing Better Managers by Doing Nothing." American Programmer, 8(1): 21–27.

[bib01_004] Boehm, Barry. 1981. Software Engineering Economics. Englewood Cliffs, NJ: Prentice Hall.

[bib01_005] Boehm, Barry, and Ronnie Ross. 1989. "Theory-W Software Project Management: Principles and Examples." IEEE Transactions on Software Engineering, 15(7): 902–916.

[bib01_006] Boehm, Barry W., ed. 1989. Software Risk Management. Washington, D.C.: IEEE Computer Society Press.

[bib01_007] Brackett, John W. 2001. "Planning and Executing Second-Generation E-Projects." Cutter Consortium E-Project Management Advisory Service Executive Report, 2(6).

[bib01_008] Brooks, Jr., Frederick P. 1995. The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition. Boston, MA: Addison-Wesley.

[bib01_009] Brown, Norm. 1996. "Industrial-Strength Management Strategies." IEEE Software, 13(4): 94–103.

[bib01_010] Brown, Norm. 1999. "High-Leverage Best Practices: What Hot Companies Are Doing to Stay Ahead." Cutter IT Journal, 12(9): 4–9.

[bib01_010a] Brown, William J., Raphael C. Malveau, Hays W. McCormick III, and Thomas J. Mowbray. 1998. AntiPatterns: Refactoring Software, Architectures, and Projects in Crisis. New York: John Wiley & Sons.

[bib01_011] Campanis, Nicholas A. 1997. "Delphi: Not the Greek Oracle, but Close." PM Network, 11(2): 46–49.

[bib01_012] Carr, Marvin J., et al. 1993. "Taxonomy-Based Risk Identification," Technical Report CMU/SEI-93-TR-6. Pittsburgh, Penn.: Software Engineering Institute.

[bib01_013] Collier, Bonnie, Tom DeMarco, and Peter Fearey. 1996. "A Defined Process for Project Postmortem Review." IEEE Software, 13(4): 65–72.

[bib01_014] Covey, Stephen R. 1989. The 7 Habits of Highly Effective People. New York: Fireside.

[bib01_015] Daskalantonakis, Michael K. 1992. "A Practical View of Software Measurement and Implementation Experiences Within Motorola." IEEE Transactions on Software Engineering. 18(11): 998–1010.

[bib01_016] DeMarco, Tom. 2001. Slack: Getting Past Burnout, Busywork, and the Myth of Total Efficiency. New York: Broadway Books.

[bib01_017] DeMarco, Tom, and Timothy Lister. 2003. Waltzing with Bears: Managing Risk on Software Projects. New York: Dorset House Publishing.

[bib01_018] Derby, Esther, and Diana Larsen. 2006. Agile Retrospectives: Making Good Teams Great. Raleigh, N.C.: The Pragmatic Bookshelf.

[bib01_019] Fisher, Roger, William Ury, and Bruce Patton. 1991. Getting to Yes: Negotiating Agreement Without Giving In, Second Edition. New York: Penguin Books.

[bib01_020] Fogle, Sam, Carol Loulis, and Bill Neuendorf. 2001. "The Benchmarking Process: One Team’s Experience." IEEE Software, 18(5): 40–47.

[bib01_021] Foody, Michael A. 1995. "When Is Software Ready for Release?" Unix Review, 13(3):35–41.

[bib01_022] Gilb, Tom. 2005. Competitive Engineering: A Handbook for Systems Engineering, Requirements Engineering, and Software Engineering Using Planguage. Burlington, MA: Butterworth-Heinemann.

[bib01_023] Goldratt, Eliyahu M. 1997. Critical Chain. Great Barrington, MA: The North River Press.

[bib01_024] Gottesdiener, Ellen. 2001. "Decide How to Decide." Software Development, 9(1): 65–70.

[bib01_025] Grady, Robert B. 1992. Practical Software Metrics for Project Management and Process Improvement. Englewood Cliffs, NJ: PTR Prentice Hall.

[bib01_026] Grady, Robert B., and Deborah L. Caswell. 1987. Software Metrics: Establishing a Company-Wide Program. Englewood Cliffs, NJ: Prentice-Hall.

[bib01_027] Highsmith, Jim. 2004. Agile Project Management: Creating Innovative Products. Boston, MA: Addison-Wesley.

[bib01_028] Humphrey, Watts. 1995. A Discipline for Software Engineering: Reading, MA: Addison-Wesley.

[bib01_029] Humphrey, Watts. 1997. Managing Technical People: Innovation, Teamwork, and the Software Process. Reading, MA: Addison-Wesley.

[bib01_030] IEEE. 1999. "IEEE Standard for Software Project Management Plans, Std 1058-1998." IEEE Standards Software Engineering 1999 Edition. Volume 2: Process Standards. New York: The Institute of Electrical and Electronics Engineers, Inc.

[bib01_031] III. 2001. "Immunizing Against Predictable Project Failure." STQE, 3(1): 32–39.

[bib01_032] International Function Point Users Group (IFPUG). 2002. Function Point Counting Practices Manual, Version 4.2. Princeton Junction, NJ: International Function Point Users Group.

[bib01_033] Jeffery, D. R., and M. J. Lawrence. 1985. "Managing Programming Productivity." Journal of Systems and Software, 5(1): 49–58.

[bib01_034] Jeffries, Ron, Ann Anderson, and Chet Hendrickson. 2001. Extreme Programming Installed. Boston, MA: Addison-Wesley.

[bib01_035] Jones, Capers. 1996. Applied Software Measurement, Second Edition. New York: McGraw-Hill.

[bib01_036] Jones, Capers. 2000. Software Assessments, Benchmarks, and Best Practices. Boston, MA: Addison-Wesley.

[bib01_037] Karten, Naomi. 1994. Managing Expectations: Working with People Who Want More, Better, Faster, Sooner, NOW! New York: Dorset House Publishing.

[bib01_038] Kerth, Norman L. 2001. Project Retrospectives: A Handbook for Team Reviews. New York: Dorset House Publishing.

[bib01_039] Leach, Lawrence P. 2000. Critical Chain Project Management. Norwood, MA: Artech House.

[bib01_040] Lewis, James P. 2000. The Project Manager’s Desk Reference, Second Edition. Boston, MA: McGraw-Hill.

[bib01_041] May, Lorin J. 1998. "Major Causes of Software Project Failures." CrossTalk, 11(7): 9–12.

[bib01_042] McConnell, Steve. 1996. Rapid Development: Taming Wild Software Schedules. Redmond, WA: Microsoft Press.

[bib01_043] McConnell, Steve. 2006. Software Estimation: Demystifying the Black Art. Redmond, WA: Microsoft Press.

[bib01_044] McManus, John. 2005. Managing Stakeholders in Software Development Projects. Oxford, England: Elsevier Butterworth-Heinemann.

[bib01_045] Moore, Geoffrey A. 1991. Crossing the Chasm: Marketing and Selling High-Tech Products to Mainstream Customers. New York: HarperBusiness.

[bib01_046] Musa, John D., Anthony Iannino, and Kazuhira Okumoto. 1987. Software Reliability: Measurement, Prediction, Application. New York: McGraw-Hill.

[bib01_047] Parkinson, C. Northcote. 1979. Parkinson’s Law and Other Studies in Administration. New York: Ballantine Books.

[bib01_048] Paulk, Mark, et al. 1995. The Capability Maturity Model: Guidelines for Improving the Software Process. Reading, MA: Addison-Wesley.

[bib01_049] Project Management Institute. 2004. A Guide to the Project Management Body of Knowledge, Third Edition. Newtown Square, PA: Project Management Institute.

[bib01_050] Rogers, Everett M., and Shoemaker, F. Floyd. 1971. Communication of Innovation: A Cross-Cultural Approach. New York: The Free Press.

[bib01_051] Rothman, Johanna. 1999. "Determining Your Project’s Quality Priorities." Software Development, 7(2): 22–25.

[bib01_052] Rothman, Johanna. 2002. "Is This Software Done?" STQE, 4(2): 30–35.

[bib01_053] Sassenburg, Hans. 2003. "When Can the Software Be Released?" Proceedings of the European SEPG, London.

[bib01_054] Schragenheim, Eli, and H. William Dettmer. 2001. "Does Your Internal Management Meet Expectations?" CrossTalk, 14(4): 19–25.

[bib01_055] Simmons, Erik. 2001. "From Requirements to Release Criteria: Specifying, Demonstrating, and Monitoring Product Quality." Proceedings of the Pacific Northwest Software Quality Conference. Portland, OR.

[bib01_056] Smith, Larry W. 2000. "Project Clarity Through Stakeholder Analysis." CrossTalk, 13(12): 4–9.

[bib01_057] Stellman, Andrew, and Jennifer Greene. 2006. Applied Software Project Management. Sebastopol, Calif.: O’Reilly Media.

[bib01_058] Verner, June M., and William M. Evanco. 2005. "What Project Management Practices Lead to Success?" IEEE Software, 22(1): 86–93.

[bib01_059] Voas, Jeffrey. 2001. "Faster, Better, and Cheaper." IEEE Software, 18(3): 96–97.

[bib01_060] Walsh, James. 1993. "Determining Software Quality." Computer Language, 10(4): 57–65.

[bib01_061] Weinberg, Gerald M. 1985. The Secrets of Consulting: A Guide to Giving & Getting Advice Successfully. New York: Dorset House Publishing.

[bib01_062] Whitten, Neal. 1995. Managing Software Development Projects: Formula for Success, Second Edition. New York: John Wiley & Sons.

[bib01_063] Wiegers, Karl E. 1996. Creating a Software Engineering Culture. New York: Dorset House Publishing.

[bib01_064] Wiegers, Karl. 1999. "Process Improvement That Works." Software Development, 7(10): 24–30.

[bib01_065] Wiegers, Karl E. 2002. Peer Reviews in Software: A Practical Guide. Boston, MA: Addison-Wesley.

[bib01_066] Wiegers, Karl E. 2003. Software Requirements, Second Edition. Redmond, WA: Microsoft Press.

[bib01_067] Wiegers, Karl E. 2006. More About Software Requirements. Redmond, WA: Microsoft Press.

[bib01_068] Wysocki, Robert K., and Rudd McGary. 2003. Effective Project Management: Traditional, Adaptive, Extreme, Third Edition. New York: Wiley Publishing, Inc.

[bib01_069] Zultner, Richard E. 1999. "Project Estimation with Critical Chain: Third-Generation Risk Management." Cutter IT Journal, 12(7): 4–12.