Technology and Innovation

Earned Value through IT Software and Hardware Project Management

1. Introduction
   1. How Earned Value is Support Through Project Management
   2. The Real Value of Earned Value


2. Earned Value in Project Management
   1. Genesis of the Concept
   2. It's More Than Just Closing the File as Complete
   3. What it Can do for an Organization Today
   4. Relationship with C/SCSC (Cost/Schedule Control Systems Criteria)
   5. Connecting this to IT Acquisitions


3. Project Scope Relative to Deliverables
   1. What Are We Really After?
   2. Using a Work Breakdown Structure (WBS) to Scope the Project
   3. Sample WBS for IT Contractor-Software
   4. Applying Make-vs-Buy Analysis
   5. How the WBS Support Earned Value
   6. Schedule Support is Essential
   7. IT-Implementation Schedule: Hardware & Software


4. Estimates and Budgetary Plans
   1. Overlaying Project Scope with Cost Schedules
   2. Earned Value with Control Accounts
   3. Financial Considerations
      1. Estimates
      2. Budgets
      3. Management Reserves
   4. Defining the Earned Value Project Baseline
   5. Techniques Employed to Measure Earned Value
   6. Samples/Article


5. Monitoring Performance to Baseline
   1. The Performance Measurement Foundation
   2. Applications in Materials and Subcontractors
   3. Determining Final Project Summation
   4. IT Turnkey Application
   5. Actual Costs to Budget/Contract
   6. Actual Time to Forecasted Time to Complete
   7. Samples/Article


6. The Fiduciary Responsibility Connected to Earned Value
   1. Applying EV to the Public Sector
      1. Sample IT-Software Contractor
      2. Sample IT-Hardware Acquisition
   2. Applying EV to the Private Sector
      1. Sample IT-Software Contractor
      2. Sample IT-Hardware Acquisition
   3. Mandates for EV in Federal Acquisitions
   4. Samples/Articles


7. The Earned Value Platform for IT Acquisitions
   1. Organization Charting
   2. Planning
   3. Scheduling
   4. Budgeting
   5. Assessment
   6. Revision
   7. Return-on-Investment


8. Conclusion