EVM Analysis

EVM and Unified Risk Management

, , , ,

Working with numerous clients, H&A earned value consultants have observed many instances where project management teams consider the risk and opportunity (R&O) management process to be something technical in nature, run by engineers and focused on the technical aspects of the project’s product. Meanwhile, there is often a separate risk process going on much less formally to consider risks in terms of the project’s schedule and cost goals. This bifurcated approach is a source of risk itself.

Procuring agencies such as the DoD, NASA, DOE, and others have published their own risk management guides. The Government Accountability Office (GAO) has various reports on this topic including examples of their findings. DCMA mentions risk in their Business Practice 4  Guideline Evaluation Template (GET) Process/Implementation Verification Points often used by contractors to check whether their earned value management system (EVMS) meets the intent of the EIA-748 Standard for EVMS guidelines. The exact questions asked by DCMA are important but the overall idea that risk and EVMS are co-dependent is the critical aspect. This is also true for the DOE. They identify risk management as one of the 10 subprocesses necessary for an EVMS.

Setting the Stage

Risk is defined as a factor, element, constraint, or course of action that introduces an uncertainty of outcome that should it occur, could negatively impact the ability to meet the project’s planned technical, schedule, or cost objectives. Negative impacts are sometimes called a threat where the objective is to mitigate the risk. A realized risk becomes an issue that must be resolved to minimize the impact. An opportunity is defined as a positive risk where the objective is to capture the beneficial impacts. Opportunities are not as common as threats.

R&O management is defined as the process of identifying, assessing, and responding to risks and opportunities throughout the project’s life cycle. The goal of R&O management is to identify potential risks and opportunities, determine the likelihood or probability the risk or opportunity will occur, and determine the impact should a risk be realized, or an opportunity is captured. Risks and opportunities are prioritized so that those with greater impact and a higher probability of occurring receive a greater share of resources and attention.

In this blog, we are using the term risk with a focus on the negative impacts or threats to a project.

Example of Common Project Risks and Risk Assessment Approach

H&A’s senior management routinely reviews literature, considers our work with clients, and discusses with our earned value consultants the main contributors to project failure. These findings are updated regularly and presented in H&A training materials as an Ishikawa Fishbone Cause and Effect diagram. Figure 1 is an example of this type of diagram. 

Figure 1: Example of an Ishikawa Fishbone Case and Effect Diagram

Figure 1: Example of an Ishikawa Fishbone Case and Effect Diagram

When this approach is used for risk assessments, each contributing risk is assessed, and the response documented. An example of a risk/response table is shown below for the first three identified risks.

Risk ItemGood Example of a Real Project Response to an Identified Risk
Poor communicationsGoals are known and documented. Communications plan is in place. Have an established cadence for weekly internal and customer meetings to quickly resolve issues. An internal project performance management dashboard is updated daily with current data. Updated IMS and risk register are broadcast weekly to the team. A strong business rhythm has been established.
Scope creepWork scope (requirements and SOW) are well defined and a change control process is in place. Performers are trained in spotting scope creep and how to handle potential changes in scope.
Inaccurate cost estimateImplemented a process enabling cost estimators to search historical actual cost data, identify analogous tasks, substantiate, and document the basis of estimate. For high risk areas, techniques such as the Delphi method, SMEs, and non-advocate reviews are used. Performance is constantly monitored to spot work elements where the actual costs do not align with the budgeted costs or the estimate at completion (EAC) is triggering internal variance at completion (VAC) thresholds. 

This same type of approach can be used by the project control team to create risk Ishikawa diagrams to identify technical risks that could impact the ability to achieve schedule and cost goals. Likewise, risk Ishikawa diagrams can be used to identify risks in the integrated master schedule (IMS) and time phased budget or estimate to complete (ETC) and EAC.

A Unified Approach to Risk

A unified approach includes technical, schedule, cost, and other risk identification and assessment that is an integral part of a contractor’s EVMS. R&O management should be integrated into the EVMS subsystems including work organization, planning and scheduling, work authorization and budgeting, management analysis and reporting, and change management. 

Identified risks are analyzed and quantified to develop a risk handling strategy. Where applicable, risk mitigation tasks have been entered into the IMS. Ideally a schedule risk assessment (SRA) has been completed to gain an understanding of duration risks that can help to improve the accuracy of the schedule. Assuming the IMS is resource loaded and leveled, the result is a more accurate time phased budget plan as it incorporates the risk handling strategies when the performance measurement baseline (PMB) is established. The R&O process also provides the necessary rationale for determining the budget amount set aside for management reserve (MR).

The R&O assessments should be a normal part of generating the Variance Analysis Reports (VARs) and updating the ETC and EAC. These assessments can also drive the need for processing baseline change requests (BCRs) as well as determining the best approach for corrective actions. 

Using Directed Searches of Identified Risks

To facilitate a unified approach, we recommend establishing a cadence of standing risk review sessions that are conducted in a methodical way to ensure the project manager, integrated product team (IPT) leads, control account managers (CAMs), schedulers, and financial analysts routinely walk through the identified risks that have the potential to impact the project’s IMS or time phased cost.

The intent is to establish a framework such as Ishikawa diagram to guide the risk review session, a directed search of the identified risks should anything further need to be addressed. It is important that a “does anyone have a risk to suggest” approach is not used. Every topic should be covered in every session by walking the Ishikawa risk items. Most of the time it will be a quick “no change” response. Separate Ishikawa diagrams could be used to guide the discussions for the contributing technical, schedule, and cost risks. The meeting room should have the ability to view the live IMS, cost data, and performance analysis data. Team members should be prepared to take notes during the meeting to compile action items.

Figure 2 is an example of a basic Ishikawa diagram of IMS risks the project control team could focus on for the risk review session. This would reflect the project control team’s identified risks to the IMS they routinely monitor.

Figure 2: Example of an IMS Ishikawa Fishbone Case and Effect Diagram

Figure 2: Example of an IMS Ishikawa Fishbone Case and Effect Diagram

For example, updating the current schedule every reporting period has the potential to compromise the integrity of the IMS to provide accurate forecast information about the project’s remaining work. Perhaps the project control team has identified a list of contributing schedule status risks, risk response, and example directed questions for each review meeting. These questions could be focused at the CAM level. The following table is a simple example. 

Risk ItemRisk ResponseExample Directed Questions
IMS critical or driving pathsVerify logic. Verify traceability exists and has not been damaged by updates. Review constraints, deadlines, and milestones. Perform data quality check, correct errors.Did milestones move? Did the end date move? What were the baseline dates for starts or finishes that fall into the period?What were the forecasted dates for starts and finishes that fall into the period?What did not happen? Why?
RealismCalculate and assess the Baseline Execution Index (BEI) and Current Execution Index (CEI). Compare the ratio of actual performance to the ratio of future performance.Is the BEI/CEI result within goals? Are there performance discrepancies? Does the forecast need to be updated to align with reality? Is the forecast showing the performance the team can achieve based on what has been achieved?
Quality of ETC/EACVerify updates are occurring. Compare current ETC/EAC to previous ETC/EAC.Has the ETC been updated? What changed and why? For example, for activities with material requirements, price or usage variances may impact the ETC/EAC. For activities with labor requirements, availability or personnel changes may impact future work effort ETC/EAC.

The same approach would be used for guided budget and cost risk discussions. Tailored cause and effect diagrams should be created for a company business environment and each project’s unique characteristics.

Interested in learning more?

H&A’s training courses purposely include content on R&O management and integrating it into the EVMS. H&A’s Project Scheduling as well as Advanced Earned Value Management Techniques (AEVMT) workshops in particular include more discussion on R&O topics.

A company’s EVMS should be designed to aid the identification and management of risks and opportunities. For example, during the process of developing the schedule and budget baseline, activity durations, resource requirements, and budget distribution can be refined to reflect identified and assessed risks. Proactively identifying and managing risks improves project performance. The expectation of specific risks occurring leads to contingency plans that lower the likelihood and impact of risks as well as the establishment of schedule margin and MR to address identified and assessed risks.

Call us today at (714) 685-1730 to get started.

EVM and Unified Risk Management Read Post »

EVM Consulting – Modeling & Simulation

, , , , , , , , ,

Fighter Jet Air Plain Flying in Front of Moon

Forewarned is Forearmed

Forewarned is forearmed. John Farmer, of New Hampshire, said that in a letter in 1685. But that advice is most likely biblical and very much older. No matter the source of the thought, we should take it as divine guidance if we are project managers. Maybe we should have it cut into a stone tablet, so we can share it with our team members.

Most of our work as project managers is spent in the “controlling” phase which is made up of the three steps “measure, analyze, act.” Our EVMS and IMS exist to be able to support this management function. The measuring part is done very well in our EVMS and our IMS; we know where we are and how we got there. The analyzing is equally well handled in the IMS and EVMS. Only the management task of acting is not well supported. Generally, we lack decision making support and tools.

EVM Consulting - Measure, Analyze, Act

Deterministic Path

No matter how well constructed and how healthy our IMS is, it has a deterministic path forward. The logic links between the activities are there because we expect them to be fulfilled. Indeed, if activity “B” is a finish-to-start successor to activity “A” we fully expect that at some point activity “A” will finish and will provide its output to activity “B”. That is a single path forward and it is a deterministic path. It is also a somewhat simplistic model.

EVM Consulting - Deterministic Relationships in EVMS

Multiple Outcomes

Our management system asks us to perform root cause analysis followed by corrective action. But what if there is more than one corrective action to be taken. And worse; what if the corrective actions can have multiple outcomes with each enjoying its own probability. That means multiple choices and multiple outcomes. How would we show that in our plan? How would we analyze the multiple possible futures that such a situation presents?

Happily, there are ways to model a future without a set path. And once we have the future model, there are also ways to simulate the outcomes to give the probabilities we need to decide which actions to take. We are talking about probabilistic branching, and we are saying that we can build a probabilistic map of the future to use in making decisions; especially making decisions on corrective actions.

Take a simple example of running a test on the project. The expectation is that eventually we will pass the test. We will keep trying until we do. In the IMS deterministic model the test portion of the IMS might look like this:

EVM Consulting - Run the Test then Use the Product

Simulation

We can simulate this situation with different expected durations for the test. That is helpful information, but it does not explain or even capture what is going on in those different durations. It looks like we are just taking longer to do the testing but is that really what is happening? What is going on here? We certainly don’t show that.

In the real world, this simple model might have three potential outcomes. There might be three paths we can take to get to the point where we use the product. Each path has a time and money cost. We might run the test and find that we passed. Or we might have to stop the test for issues on the item or the test setup. We might even fail the test and must correct something about the product to improve our chances of passing a rerun. Eventually we will get to a usable product. But what do we put in our estimate and our plan? What do we tell the resources we need? What do we tell the boss? The customer?

EVM Consulting - Real World Testing

Full Future Model

We now have a much better understanding of the future and can explain the situation. We also can simulate the situation to find out the most likely time and cost outcomes, so we can explain the future without any histrionics or arm waving.
If the issue is important enough we can build out the full future model and simulate it.

EVM Consulting - Full Future Model and Simulation

No matter how far we pursue the model of the future, having a valid model and being able to stand on solid ground are very valuable to us as project managers.

This is not to say that we should model out complex situations as a routine in the IMS. That would be impossible, or at least prohibitively costly. We are saying that when situations arise, we need to be able to use the IMS to help us make decisions.

This type of probabilistic modeling of the future is particularly useful in defining major decision points in our plan. When we reach a decision point the IMS may have multiple branches as successors but that implies we take every branch and that is not valid. Modeling each branch and its probabilities is valid. In the example below, where the milestone represents a decision point, we have shown three possible paths to take. If each were modeled out into the future with time and cost data, we should have the information we need to choose the path we wish to pursue. Without processes and tools like this, we would be flying blind.

Future Blog Posts

This discussion will be continued in future blogs to develop a better foundational understanding of the process and power of probabilistic modeling in our EVMS.

EVM Consulting - Decision Point

Good information sets the stage for good decisions. The IMS and the EVMS have sufficient information to help us model the pathways ahead of our critical decisions. We just need to learn to take advantage of what we have available to us.

Find out how an experienced Humphreys & Associates EVM Consultant can help you create a full future model and simulation of your most vital EVMS Systems. Contact Humphreys & Associates at (714) 685-1730 or email us.

EVM Consulting – Modeling & Simulation Read Post »

EVMS Variance Analysis — EVMS Analysis and Management Reports

, , , ,

A Variance Analysis Report (VAR) that includes specific information about the cause, impact, and corrective action “provides management with early insight into the extent of problems and allows corrective actions to be implemented in time to affect the future course of the program” [reference: NDIA, IPMD EIA-748 (Revision D) EVMS Intent Guide]. Unfortunately, variance analysis is an easy target for criticism during EVMS reviews. There are many examples of inadequate variance analysis to choose from, but what they all have in common is the lack of specific information on the “why, what, how, when, and who” of any variance. The variance analysis reporting requirements are found in the EIA-748 (Revision D) Guidelines in Section IV., Analysis and Management Reports, Guidelines 22-27.

EIA-748 Guidelines
Section IV. Analysis and Management Reports
22 2-4a Control Account Monthly Summary, Identification of CV and SV
23* 2-4b Explain Significant Variances | Earned Value Management
24 2-4c Identify and Explain Indirect Cost Variances
25 2-4d Summarize Data Elements and Variances thru WBS/OBS for Management
26* 2-4e Implement Management Actions as Result of EVM Analysis
27* 2-4f Revise EAC Based on Performance Data; Calculate VAC


A VAR that includes specific information and data about a problem will allow management to make informed decisions and mitigate project risk. Getting specific about variance analysis reporting includes the following elements.

Overall:

  • Emphasis on the quantitative, not qualitative
  • Emphasis on the specific, not the general
  • Emphasis on significant problems, not all problems
  • Define abbreviations and acronyms at first use
  • The Control Account Manager (CAM) is the most knowledgeable person to write the variance analysis report but will need information from the business support team

Cause:

  • Isolate significant variances
  • Discuss cost and schedule variances separately
  • Clearly identify the reason (root cause) for the variance (ties to the corrective action plan)
  • Clear, concise explanation of the technical reason for the variance
  • Provide cost element analysis
    • Labor – hours, direct rates, skill mix, overtime (rate & volume)
    • Material – unplanned requirements, excess quantities, unfavorable prices (price & usage)
    • Subcontracts – changing requirements, additional in-scope work, schedule changes
    • Other Direct Costs – unanticipated usage, in-house vendor
    • Overhead (indirect) – direct base, rate changes
  • Identify what tasks are behind schedule and why

Impact:

  • Describe specific cost, schedule, and technical impact on the project
  • Project future control account performance (continuing problem)
  • Address effect on immediate tasks, intermediate schedules, critical path, driving paths, risk mitigation tasks
  • Describe erosion of schedule margin, impacts to contractual milestones or delivery dates, and when the schedule variance will become zero (this may only mean the work getting completed late (BCWPcum =BCWScum); and does not necessarily mean getting “back on schedule”
  • Describe any impact to other control accounts
  • Assess the need to revise and provide rationale for the Estimate at Completion (justify ETC realism – CPI to TCPI comparison, impacts of corrective action plan, risk mitigation, open commitments, staffing changes, etc.)
  • Note: If there is a root cause, there will be an impact. It could be related to cost, schedule, lessons learned to be applied to future activity, an update required to a process to support the corrective action or a re-prioritization of resources to meet a schedule.

Corrective Action Planning:

  • Describe specific actions being taken, or to be taken, to alleviate or minimize the impact of the problem
  • Include the individual or organization responsible for the required action
  • Include schedules for the actions and estimated completion dates (ECD)
  • If no corrective action is possible, explain why
  • Include results of corrective action plans in previous VARs.

Ask yourself, is the analyses presented in a manner that is understandable? Does the data support the narrative? Does the variance explanation provide specifics of:

why” the problem occurred,
what” is impacted now or in the future,
how” the corrective action is being taken,
when” the corrective actions will occur,
when” the schedule variance will become zero, and/ or the work gets “back on schedule”
who” is responsible for implementing the corrections?

Remember, a well-developed Variance Analysis Report can reduce the risk of a Corrective Action Request (CAR) during an EVMS review.

EVMS Variance Analysis — EVMS Analysis and Management Reports Read Post »

7 Principles of Earned Value Management Tier 2 System Implementation | EVM Analysis

, , ,

Updated: Watch our review video of 7 Principles of Earned Value Management Tier 2 System Implementation Intent Guide



7 Principles of Earned Value Management Intent GuideThe Assistant Secretary for Preparedness and Response (ASPR) issued the “7 Principles of Earned Value Management Tier 2 System Implementation Intent Guide,” 21 December 2011.  Since most of BARDA acquisitions are unique in that they are not Information Technology (IT) projects or Construction projects, they developed a tiered approach to applying EVMS. Tier 1 are construction and IT contracts and will require full ANSI/EIA-748 compliance. Tier 2 contracts are defined as countermeasure research and development contracts that have a total acquisition cost greater than $25 million and have a Technical Readiness Level of less than 7. Tier 2 contracts will apply EVM principles that comply with the 7 Principles of EVM Implementation. Tier 3 are countermeasure research and development contracts between $10 million and $25 million and will require EVM implementation that is consistent with the 7 Principles approach. The focus of this implementation guide is on the Tier 2 contracts.

The Intent Guide contains explanations for each Principle, a Glossary of Terms, a Supplemental EVM Implementation Guideline, and Sample EVM Documents. The Supplemental EVM Implementation Guideline contains recommendations regarding EVM process flows, tools, the necessity to integrate the EVM engine with the accounting system, basic documentation requirements, ranges of implementation costs, recommendations on requirements for support personnel, and use of the 7 Principles on Tier 3 programs.

The Intent Guide defines Tier 2 as: “For countermeasure research and development contracts that have total acquisition costs greater than or equal to $25 million and have a Technical Readiness Level (TRL) of less than 7 will apply EVM principles for tracking cost, schedule and technical performance that comply with the 7 Principles of EVM Implementation.”

The 7 Principles of Earned Value Management

1. Plan all work scope to completion.

This Principle includes development of a Work Breakdown Structure (WBS) and WBS Dictionary that includes all of the work scope.  It is also recommended that detailed scope definition be accomplished at the work package level.

2. Break down the program work scope into finite pieces that can be assigned to a responsible person or organization for control of technical, schedule and cost objectives.

This Principle defines the schedule requirements.  Most scheduling functions are required including network scheduling, horizontal and vertical traceability, forecasting schedule start and complete dates, and critical path analysis.  The contract milestones must also be included in the schedule.

This Principle also discusses the organizational requirements.  The Control Account Manager must be identified but there is no requirement for the costs to roll up through organizational elements; this, and development of an Organization Breakdown Structure (OBS) is recommended if it can be done in a cost effective manner.

3. Integrate program work scope, schedule, and cost objectives into a performance measurement baseline plan against which accomplishments can be measured. Control changes to the baseline.

This Principle is discussed in the Intent Guide in two parts.  The first, 3a, regards integration of scope, schedule, and cost objectives into a performance measurement baseline. The schedule can be either resource loaded or the budgets loaded into a cost tool and a time-phased control account plan generated.  The cost tool must be linked to the schedule tool to ensure baseline integration.  The planning includes both direct and indirect dollars.

This Principle also defines the use of undistributed budget and management reserve.

The second part of this Principle, 3b, is the requirement to control changes to the baseline. This requires that contractual changes be incorporated to the baseline in a timely manner.

Budget logs are to be used to track both external and internal changes. All changes are to have documentation that explains the rational/justification for the change and the scope, schedule and budget for that change.

4. Use actual costs incurred and recorded in accomplishing the work performed.

This Principle requires that actual costs be accumulated in a formal accounting system consistent with the way the work was planned and budgeted.  A work order or job order coding system must be used to identify costs to the control account and allow summarization through higher levels of the Work Breakdown Structure.  The use of estimated actuals is also required for material and subcontractors to ensure that earned value data is not skewed.

5. Objectively assess accomplishments at the work performance level.

This Principle requires that schedule status and earned value assessment must occur at least monthly.  The allowable earned value techniques are discussed as well as the requirements of for the use of each.

6. Analyze significant variances from the plan, forecast impacts, and prepare an estimate at completion based on performance to date and work to be performed.

This principle is also divided into two parts.  The first, 6a, regards the analysis of variances from the plan.  The earned value system must be able to calculate cost and schedule variances, at least cumulatively, on a monthly basis.  The system should also be able to provide the Cost Performance Index (CPI), the Schedule Performance Index (SPI), and the use of the To-Complete Performance Index (TCPI) is also encouraged.  Variances that exceed the contract variance thresholds must be explained in terms of the cause, impact and corrective action.  Although this Principle does not discuss the preparation of a Variance Analysis Report (<abbr=”Variance Analysis Report”>VAR) by the CAM, Principle 7 does require that Program Managers hold their CAMs accountable to write a proper Variance Analysis Report (Earned Value Management Analysis).

The second part of this Principle, 6b, requires that an Estimate at Completion (EAC) be prepared based on performance to date and the work remaining to be performed.

7. Use earned value information in the company’s management processes.

This Principle regards Program Management use of the earned value data to manage the program’s technical, schedule and cost issues and how that data is used in the decision making process.

Although much of the language in the Intent Guide is similar to that of typical guidance documents for the EVMS requirements, it must be remembered that the EVMS Guidelines are not being implemented, only the 7 Principles.  The Principles define an approach to managing programs with the basic requirements of Earned Value; such that the cost of the system is minimized, but only those elements necessary to manage these types of programs are necessary.  This allows for further system flexibility and reduces the documentation needed.  For instance, in Principle 1, the requirements of the WBS Dictionary could be expanded to contain the information that would normally be included on the Work Authorization Document.  If this were done, Work Authorization Documents are not necessary because the WAD content normally contained would be embodied in the WBS dictionary; and the associated cost is reduced over the life of the program.

With the 7 Principles there is no need for an EVM compliance review.  An Integrated Baseline Review (IBR), also known as a Performance Measurement Baseline Review (PMBR), could be required.

The 7 Principles Comparison to the EIA-748 32 Guidelines

For those who are more accustomed to the EVMS Guidelines as described in the EIA Standard, EIA-748, in the table below the 7 Principles are loosely identified to the 32 Guidelines and Guideline areas.  This does not mean that all of the requirements must be met with the 7 Principles only that they can be cross-referenced.  Several of the Guidelines are not specifically identified but could be considered as incorporated by reference. The indirect cost requirements are incorporated by planning the work with both direct and indirect dollars; therefore, it is implied that budget, earned value, and actual costs would also include both direct and indirect costs.

The appendix also contains the requirement that the EVM Engine needs to be integrated with the company’s accounting system.  Further, some programs may also be required to be compliant with the Cost Accounting Standards.  Guideline 20, “Identify unit costs, equivalent units costs, or lot costs when needed” is not included; this more than likely would not be a requirement for HHS or BARDA programs.

Earned Value Analysis: 7 Principles of EVM Tier 2 System Implementation Cross-Reference to the EVMS Guidelines

7 Principles of EVM Tier 2 System Implementation Cross-Reference to the EVMS Guidelines
Principle Number Principle Title EVMS Guidelines Guidelines not Specifically Indentified ANSI/EIA-748 Areas
Principle 1 Plan all Work Scope 1 Organization
Principle 2 Break Work into Finite Pieces and Define Person/Organization Responsible for Work 2, 5, 6 4
Principle 3a
Integrate Scope, Schedule and Budget into a Performance Baseline 3, 7, 8, 9, 10, 11, 14 13 Planning & Budgeting
Principle 3b
Control Changes to the Baseline 15, 28, 29, 30, 31, 32 Revision & Data Maintenance
Principle 4 Use Actual Costs Incurred and Recorded in Accomplishing the Work Performed 16, 17, 18, 21 19, 20 Accounting Considerations
Principle 5 Objectively Assess Accomplishments of the Work Performance “Level 12, 22 EVM Analysis & Management Reports
Principle 6a
Analyze Significant Variances fomr the Plan 23, 25 24
Principle 6b
Prepare and Estimate at Completion based on Performance to-data and Workd to be Performed 27
Principle 7 Use EVM information in the Company’s Management Processes 26

Recommendations for Enhancement to the Intent Guide

The 7 Principles Intent Guide was issued in December 2011. In June 2012 the requirements for the Integrated Program Management Report (IPMR) was issued; this will replace the Contract Performance Report (CPR) for contracts issued after June 2012. When a revision to the Intent Guide is issued, the IPMR should be included.

The Intent Guide is a “what to do” document and contains little on “how to do it”. Internal procedural documents should be required to define how a company will implement the Guide requirements.

Principle 6a requires that the cost and schedule variances be calculated at least on a cumulative basis and only recommends calculation of the current month. The current month calculation should be a requirement since both the CPR and the IPMR require current month reporting.

Summary

The “7 Principles of Tier 2 System Implementation Intent Guide” requires the basic elements of earned value and the documentation necessary to demonstrate that earned value is being adequately implemented on Tier 2 programs. H&A personnel understand the requirements and are able to “size” those requirements to meet company and customer needs. Click to request a PDF copy of the Intent Guide.

Humphreys & Associates (H&A) has been providing Earned Value Management training and implementation services for over 35 years. H&A provides self-paced online, classroom and private training courses, as well as training tailored to specific industry needs, and can assist in all aspects of Earned Value Management Implementation.

For more information about EVM training or support, or with questions about your company’s requirements, please contact the Humphreys & Associates corporate office.

 

 

7 Principles of Earned Value Management Tier 2 System Implementation | EVM Analysis Read Post »

Scroll to Top