Performance-based earned value

Performance-Based Earned Value

Volumn , Issue , 2007, Pages 1-300

  Solomon, Paul J ^a   Young, Ralph R ^a  

^a NORTHROP GRUMMAN CORPORATION   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

BUDGET CONTROL; MANAGERS; QUALITY CONTROL; RISK ASSESSMENT; RISK MANAGEMENT; SOFTWARE ENGINEERING; SYSTEMS ENGINEERING; VALUE ENGINEERING;

EARNED VALUE MANAGEMENT; GOVERNMENT ACQUISITION POLICY; MONITORING AND CONTROLLING; PERFORMANCE MEASUREMENTS; PROJECT MANAGEMENT BODY OF KNOWLEDGE; PROJECT MANAGEMENT PROCESS; SOFTWARE AND SYSTEMS ENGINEERINGS; TECHNICAL PERFORMANCE MEASURES;

PROJECT MANAGEMENT;

EID: 85041069115     PISSN: None     EISSN: None     Source Type: Book    
DOI: 10.1109/9780470084663     Document Type: Book

References (75)

1. U.S. Federal Acquisition Regulations, Appendix D, paragraph 2.101.
2. Project Management Institute. Practice Standard for Earned Value Management. Upper Darby, PA: Project Management Institute, 2004.
3. Project Management Institute. A Guide to the Project Management Body of Knowledge (PMBOK® Guide), 3rd ed. Upper Darby, PA: Project Management Institue, 2004 (ANSI/PMI 99-001-2004).
4. Solomon, Paul. “Integrating Systems Engineering with Earned Value Management.” Defense Acquisition, Technology, & Logistics Magazine, May 2004 (see www.dau.mil/pubs/damtoc.asp).
5. Executive Office of the President. OMB Circular No. A-ll, Part 7, Section 300.5, Planning, Budgeting, Acquisition and Management of Capital Assets, July 2004 (see www.whitehouse.gov/omb/circulars/all/cpgtoc.html).
6. Wynne, Michael [Acting Undersecretary of Defense, Acquisition, Technology and Logistics (AT&L). Memorandum, Policy for Systems Engineering in DoD, February 20, 2004.
7. Wynne, Michael and Schaeffer, Mark. “Revitalization of Systems Engineering in DoD.” Defense Acquisition, Technology, & Logistics Magazine, March/April 2005 (see www.dau.mil/pubs/damtoc.asp).
8. DoD. Defense Acquisition Guidebook, http://akss.dau.mil/dag/.
9. Office of the Under Secretary of Defense for Acquisition, Technology, and Logistics Defense Systems, Systems Engineering, Enterprise Development (OUSD(AT&L)DS/SE/ED). Systems Engineering Plan (SEP) Preparation Guide. Version 1.0, November 15, 2005. see http://www.acq.osd.mil/ds/se/publications/pig/sep_prepguide_vl.pdf.
10. DoD Handbook Work Breakdown Structure. See https://acc.dau.mil/CommunityBrowser.aspx?id=17642
11. DoD. Integrated Master Plan and Integrated Master Schedule Preparation and Use Guide. See https://acc.dau.mil/CommunityBrowser.aspx?id=19559.
12. National Defense Industrial Association (NDIA) Program Management Systems Committee (PMSC). ANSI/EIA-748-A, Standard for Earned Value Management Systems Application Guide. Working Release for User Comment, Arlington, VA, 2005.
13. Institute of Electrical and Electronics Engineers (IEEE). IEEE Std 1220™-2005, IEEE Standard for Application and Management of the Systems Engineering Process. New York, 2005.
14. Electronic Industries Alliance (EIA). ANSI/EIA 632, Processes for Engineering a System. Arlington, VA: EIA, 1998.
15. Software Engineering Institute (SEI). Capability Maturity Model Integration, Version 1.1. Pittsburgh, PA: SEI, Carnegie Mellon University, March 2002.
16. U.S. Department of Defense (DoD). DoD Directive 5000.1, The Defense Acquisition System. May 12, 2003.
17. U.S. Department of Defense (DoD). DoD Instruction 5000.2, Operation of the Defense Acquisition System. May 12, 2003.
18. U.S. Department of Defense (DoD) and U.S. Army. Practical Software and Systems Measurement. See www.psmsc.com.
19. Solomon, Paul. “B-2 Bomber Team’s EVM Innovations Make Program Soar.” Agile Acquisition, the Air Force Acquisition Newsletter (formerly Aerospace Acquisition). January-February 2000.
20. Solomon, Paul. “Practical Software Measurement, Performance-Based Earned Value.” CrossTalk: The Journal of Defense Software Engineering. September 2001, pp. 28-29. See www.stsc.hill.af.mil/crosstalk/2001/09/index, html.
21. Solomon, Paul. “Using CMMI to Improve Earned Value Management” (CMU/SEI-2002-TN-016). Carnegie Mellon University/SEI, October 2002. See www.sei.cmu.edu/pub/documents/02.reports/pdf/02tn016.pdf.
22. Software Engineering Institute (SEI). Capability Maturity Model Integration, version 1.1. Pittsburgh, PA: SEI, Carnegie Mellon University, March 2002.
23. Project Management Institute. A Guide to the Project Management Body of Knowledge (PMBOK® Guide), 3rd ed. Upper Darby, PA; Project Management Institute, 2004 (ANSI/PMI 99-001-2004).
24. Antanitus, Dave. “The Business of Metrics-Measuring the Product of the Plan.” Program Manager (now Defense AT&L), March-April, 2003, p. 11.
25. Baxter, Peter. “Focusing Measurement on Managers’ Informational Needs.” CrossTalk: The Journal of Defense Software Engineering. July 2002, pp. 22-55.
26. Young, Ralph R. Effective Requirements Practices. Boston, MA: AddisonWesley, 2001. This book provides a set of recommended requirements practices based on a comprehensive review of industry literature and practical experience (see also www.ralphyoung.net).
27. The determination of the appropriate number of system-level requirements is a function of the complexity of the system being developed. A requirement density of one requirement per thousand lines of code of a planned system is the approximate order of magnitude to capture the vision of the stakeholders and to estimate the cost and schedule to build the system.
28. Young, Ralph R. Project Requirements: A Guide to Best Practices. Vienna, VA: Management Concepts, 2006. A sample Project Vision and Scope Document template is provided in Appendix C.
29. Electronic Industries Alliance (EIA).ANSI/EIA 632, Processes for Engineering a System, Arlington, VA: EIA, 1998.
30. Institute of Electrical and Electronics Engineers (IEEE). IEEE Std 1220™-2005, IEEE Standard for Application and Management of the Systems Engineering Process. New York, 2005.
31. Gilb, Tom. Competitive Engineering. Burlington, MA: Elsevier Butterworth-Heinemann, 2005.
32. Systems and Software Consortium, Verification and Validation Website, Topic:Validation. http://www.software.orgIPUBNNV/. Special permission to reproduce material from the Systems and Software Consortium (SSCI) website is granted by SSCI.
33. See Young, Ralph R. Project Requirements: A Guide to Best Practices. Guidance concerning requirements traceability is provided in AppendixA.
34. Refer to Specific Practice (SP) 1.4 of the Requirements Management (REQM) Process Area (PA) of the CMMI. See Capability Maturity Model Integration, version 1.1. Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, March 2002.
35. IEEE. IEEE Standard 1233-1998, Guide for Developing System Requirements Specifications. New York: IEEE, 1998.
36. Gilb, Tom. Principles of Software Engineering Management. Harlow, UK: Addison-Wesley, 1988.
37. Terninko, John. Step-By-Step QFD: Customer-Driven Product Design. Boca Raton, FL: St. Lucie Press, 1997.
38. See Young, Ralph R. The Requirements Engineering Handbook. Boston, MA: Artech House, 2004, p. 8, for a discussion of these criteria.
39. See Constantine, Larry L. and Lockwood, Lucy A. D. Software For Use: A Practical Guide to the Models and Methods of Usage-Centered Design. ACM Press, 1999.
40. Project Management Institute. A Guide to the Project Management Body of Knowledge (PMBOK Guide), 3rd. Ed. Upper Darby, PA: Project Management Institute, 2004.
41. Institute of Electrical and Electronics Engineers (IEEE). IEEE Std 1220™-2005, IEEE Standard for Application and Management of the Systems Engineering Process. New York: IEEE, 2005.
42. Electronic Industries Alliance (EIA). ANSI/EIA 632, Processes for Engineering a System. Arlington, VA: EIA, 1998.
43. Software Engineering Institute (SEI). Capability Maturity Model Integration, version 1.1. Pittsburgh, PA: SEI, Carnegie Mellon University, March 2002.
44. Solomon, Paul. “Using CMMI to Improve Earned Value Management.” (CMU/SEI-2002-TN-016). Carnegie Mellon University/SEI, October 2002 (see www.seLcmu.edu/pub/documents/02.reports/pdf/02tn016.pdf).
45. Baxter, Peter. “Focusing Measurement on Managers’ Information Needs.” CrossTalk: The Journal of Defense Software Engineering. July 2002, pp. 22-25.
46. Calaprice, Alice. The Expanded Quotable Einstein. Princeton, NJ: Princeton University Press, 2000.
47. Solomon, Paul. “Integrating Systems Engineering with Earned Value Management.” Defense Acquisition, Technology, & Logistics Magazine, May/June 2004 (see www.dau.mil/pubs/damtoc.asp).
48. Young, Ralph R. Effective Requirements Practices. Boston, MA: Addison-Wesley, 2001.
49. Kitterman, Dick. “A Structured Method for Generating, Evaluating and Using Metrics.” Proceedings of the International Symposium of the International Council on Systems Engineering, July 2005.
50. International Council on Systems Engineering (INCOSE). INCOSE Systems Engineering Handbook, Version 3, June 2006, p. 7.11. See www.incose.org.
51. Electronic Industries Alliance (EIA). ANSI/EIA 632, Processes for Engineering a System. Arlington, VA, EIA, 1998.
52. Kompella, Lakshminarayana. “Earned Value Management for Software Products: An Approach.” Souvenir of the PMIPCC-Asia Pacific Conference, April 2005.
53. Fleming, Quentin and Koppelman, Joe. “The Curse of EVM, LOE-Always Quantify and Quarantine LOE.” The Measurable News, June 2002.
54. National Defense Industrial Association (NOIA) Program Management Systems Committee (PMSC). NDIA PMSC ANSI/EIA-748-A. Standard for Earned Value Management Systems Application Guide, 2005.
55. Leffingwell, Dean and Don Widrig. Managing Software Requirements, A Unified Approach. Reading, MA: Addison-Wesley, 2000, pp. 210-211.
56. U.S. Air Force Space and Missile Systems Center (SMC). SMC Systems Engineering Primer and Handbook. Los Angeles Air Force Base, CA: SMC, 2004, p. 71.
57. Durante, Blaise. “Agile Acquisition-Acquisition Streamlining—No Substitute for Solid Program Planning.” Agile Acquisition, the Air Force Acquisition Newsletter. August-September 2004.
58. Cockburn, Alistair. “Learning from Agile Software Development—Part One.” Cross Talk: The Journal of Defense Software Engineering, October 2002.
59. U.S. Department of Defense (DoD). DoD Earned Value Management Implementation Guide (EVMIG). April, 2005, Section 2-4.e.
60. Balaji, T. Quantitative Software Project Management—A Simplified Approach. Tutorial, The Software Engineering Process Group (SEPG) Conference in Asia 2001, February 2001.
61. Baxter, Peter. “Focusing Measurement on Managers’ Informational Needs.” CrossTalk: The Journal of Defense Software Engineering, July 2002, pp. 22-25.
62. Solomon, Paul. “Using Earned Value to Track Requirements Progress.” Proceedings of the International Symposium of the International Council on Systems Engineering (INCOSE), July 2006.
63. Systems and Software Productivity Consortium. Verification and Validation Website, Topic: Validation. http://www.software.org/PUB/VNV/. 2006.
64. U.S. Naval Air Systems Command (NAVAIR). Using Software Metrics & Measurements for Earned Value Toolkit. Lexington, MD: Department of the Navy, 2004. See https://acc.dau.mil/CommunityBrowser.aspx?id=1959/.
65. Cockburn, Alistair. Crystal Clear. Boston, MA: Addison-Wesley, 2004, pp. 99-102.
66. Cockburn, Alistair. “A Governance Model for Incremental, Concurrent, or Agile Projects.” Cross Talk: The Journal of Defense Software Engineering. February 2006, pp. 13-17.
67. Wilson, Peter. “Sizing Software Using Testable Requirements.” Available at www.testabierequirements.com.
68. Solomon, Paul. “Practical Software Measurement, Performance-Based Earned Value.” Cross Talk: The Journal of Defenses Software Engineering. September 2001, pp. 28-29 (see www.stsc.hill.af.mil/crosstalk/2001/09/index.html).
69. Staley, M., Oberndorf, P., and Sledge, C. Using EVMS with COTS-Based Systems. SEI Technical Report CMU/SEI-2002-TR-022, June 2002.
70. U.S. Department of Defense (DoD). Work Bruakdown Structures for Defense Materiel Items. MIL-HDBK-881A, 30 July 2005. See http://dcarc.pae.osd.mil/88/handbook/index.html.
71. Executive Office of the President. OMB Circular No. A-ll, Part 7, Section 300.5, Planning, Budgeting, Acquisition and Management of Capital Assets, July 2004 (see www.whitehouse.gov/omb/circulars/all/cpgtoc.html).
72. U.S. Federal Acquisition Regulation. See www.acqnet.gov/far/.
73. Software Engineering Institute (SEI). CM MI Acquisition Module (CMMl-AM). Version 1.1. Technical Report CMU/SEI-2005-TR-011. Pittsburgh, PA: SEI, 2005. See www.sei.cmu.edu/publications/documents/05.reports/05tr011.html.
74. Solomon, Paul. “Using CMMI to Improve Earned Value Management” (CMU/SEI-2002-TN-016). Carnegie Mellon University/SEI, October 2002 (see www.sei.cmu.edu/pub/documents/02.reports/pdf/02tn016.pdf).
75. Solomon, Paul. “Practical Software Measurement, Performance-Based Earned Value.” CrossTalk: The Journal of Defense Software Engineering. September 2001, pp. 25-29 (see www.stsc.hill.af.mil/crosstalk/2001/09/index.html).