NDIA

Video Release – Assessing Schedule Risk Using Deltek’s Acumen Risk 6.1 | Part 2 of 2

, , , , , , , , , , ,

The conclusion of our review of the foundational elements of performing a schedule risk assessment (SRA) using Acumen Risk 6.1

0:17 – Risk Exposure Chart
1:03 – Tornado Chart
2:14 – Parting Thoughts

Read the blog post at:

Assessing Schedule Risk Using Deltek’s Acumen Risk 6.1 | Part 2 of 2

Video Release – Assessing Schedule Risk Using Deltek’s Acumen Risk 6.1 | Part 2 of 2 Read Post »

Video Release – Assessing Schedule Risk Using Deltek’s Acumen Risk 6.1 | Part 1 of 2

, , , , , , , , , , ,

 

How confident are you that your project will finish on time? Review the foundational elements of performing a schedule risk assessment (SRA) using Acumen Risk 6.1

2:22 – Schedule Health Diagnostics
4:55 – Duration Uncertainty
6:35 – Risk Events
8:20 – Simulation Process
 
Read the blog post at:

Assessing Schedule Risk Using Deltek’s Acumen Risk 6.1 | Part 1 of 2

Video Release – Assessing Schedule Risk Using Deltek’s Acumen Risk 6.1 | Part 1 of 2 Read Post »

Assessing Schedule Risk Using Deltek’s Acumen Risk 6.1 | Part 1 of 2

, , , , , , , , , , ,

Why Perform Schedule Risk Assessments? EVMS and Agile implementations within the same company or on the same project.

Before a project is ready to be baselined, a typical question the customer asks the project manager is, “How confident are you that the project will finish on time?”

This is a more difficult question than you might think.  In competitive environments, guessing is not an option.  The probability of success on a project must be quantified.  The risks that impact the odds for success must also be quantified.  If the risk is managed, the probability of completing the project on time and under budget is improved.

Customers are not blind to the importance of risk management.  This is evidenced by recent changes in government contracting requirements that call for formal risk assessments of project schedules.  Even if risk management were not a contractual requirement, it would be irresponsible for any project manager to ignore the need for risk management and proceed without identifying and assessing the project’s risks.

Schedule risk exists in every project.  This risk can be quantified, analyzed, and mitigated, or it can be ignored.  However, ignoring schedule risk does not make it go away.  Fortunately, there are advanced software tools, such as Deltek’s Acumen Risk, that can help model the expected impacts of risk in the schedule. Then, the answer to “how confident are you that the project will finish on time?” can be answered with quantifiable information.

In the following sections, a few of the foundational elements of performing a schedule risk assessment (SRA) using Acumen Risk 6.1 will be discussed.  The software was designed with the understanding that not everyone is an expert in schedule risk analysis.  The software provides beginners with an easy to follow path to perform in-depth schedule risk analysis as well as advanced features for experienced risk experts.

Along with quick start guides and help documentation, the menu structure is laid out like a schedule maturity timeline.  From left to right, the menu selections take one from the start-up steps of importing the schedule, to analyzing the schedule, assessing schedule risk, accelerating the schedule, and advanced customization features.

Deltek_Acumen-Top-Level_MenusDeltek Acumen – Top-Level Menus

 

Schedule Health Diagnostics

Before delving into schedule risk assessments, let’s take one minor detour from risk into schedule diagnostics.

Would you trust a broken watch to tell you the correct time?  The same goes for a schedule risk assessment.  A broken schedule network cannot be trusted to yield reliable, and therefore actionable, SRA results.

The National Defense Industrial Association (NDIA) Integrated Program Management Division (IPMD) Planning & Scheduling Excellence Guide (PASEG), is widely regarded as one of the premier references on scheduling best practices.  The PASEG was created by a joint team of both government and industry scheduling experts, thus it has no particular point of view to promote or defend.  One of the scheduling best practices the PASEG discusses is that the integrated master schedule (IMS) should be validated before any SRA is performed.  “Validated” means that the tasks, logic, durations, constraints, and lags in the IMS should be analyzed and corrected as necessary.

Acumen Fuse provides a complete set of schedule diagnostics.  When I first clicked on the “Diagnostics” tab, I saw an initial set of metrics.

EVMS: Acumen Fuse Schedule diagnostics

Each one of these metrics was applied to the project’s timeline that which makes it easy to see both where and when the issues occur.  What I did not notice at first was that these metrics were just one subset; I was only looking at the “Schedule Quality” subset of the diagnostics.  There were similar subsets in the areas of Logic, Duration, Constraints, Float, and the DCMA 14-point Schedule Assessment, just to name a few.  All of these diagnostic tests can be modified to reflect your company or customer’s standards.

Before leaving the topic of schedule health, there are a few words of caution.  No matter how useful a schedule analysis tool may be, there is no substitute for the task managers taking ownership of the IMS and ensuring that it is in good working order.  For example, analysis software can be used to check to determine if a task has a predecessor and a successor, but only someone familiar with the effort can determine if a task has the “correct” predecessor and successor.  Analysis software is becoming more and more sophisticated, but people still control the success or failure of the project.

Duration Uncertainty

Once a sound schedule has been developed, the next foundational elements of an SRA are the duration uncertainty estimates.  There are two widely accepted methods of assigning duration uncertainty.

The preferred and more precise method is to obtain three-point duration estimates (best case, worst case, and most likely) from the task owners.  At a minimum, this should be performed on all critical and near-critical tasks (and driving and near-driving tasks supporting significant events).  For larger schedule networks, it may not be reasonable to gather this type of information for every task.  If custom three-point estimates are not available, templated duration uncertainty could be applied based on the type of work, the task owner, historical performance, or any other applicable task characteristic.

Acumen Risk handles both methods very easily.  Custom three-point estimates can be entered for each task in days (or hours), or as a percentage of the current remaining duration of the task.  Standard duration uncertainty templates are easily applied to a task by selecting the appropriate risk level on the calibration bar.  To streamline the process, by setting the calibration at any summary level, the uncertainty template is cascaded down to all the “children” tasks.

Description. Calibration.

Risk Events

One thing traditional Critical Path Method (CPM) networks do poorly is model unexpected results.  For example, if there is a 90% success rate on fatigue testing, the IMS will generally be constructed to assume the test will be successful, with no disruption to downstream tasks.

EVMS: Critical Path Method

But what happens if the test fails?  While unlikely, there is still a very real possibility that the results will be unfavorable.  If the test does return unfavorable results, there will likely be a significant delay while re-work is performed in the areas of design, build and test.  A traditional CPM network can model a successful test or an unsuccessful test, but not both.  This is not a problem with a schedule risk assessment.  Information from the project’s risk register can be used to model the likelihood of a test failure, as well as the consequence, or delay to downstream tasks resulting from that failure.

EVMS: CPM Risk Events Consequence

Is this an acceptable risk?  An SRA can quantify the risk and provide information on the likelihood of successful deliveries.  Acumen does not stop there though.  One of its newest features is to organize and track all risk events within its built-in risk register, as well as to track the steps being taken to help mitigate that risk.  Or, if your organization already maintains an external risk register in Excel, it can be imported into Acumen to eliminate the duplicate tracking of risk events.  Whether the risk register is imported from Excel or built from scratch within Acumen, a single risk event can then be mapped to one or more activities, or a single activity can be associated with one or more risk events.

EVMS: risk registers 

 

Simulation ProcessEVMS: Simulation Process

A typical SRA uses Monte Carlo techniques to simulate hundreds or thousands of potential project outcomes using the risks and uncertainties that have been supplied.

For most users, simply accepting the default settings and pushing the “Run Risk Analysis” button would be sufficient.  But if terms like “Convergence”, “Correlation Coefficient”, “Central Limits Theorem” and “Seed Value” are part of your normal working environment, Acumen provides a variety of settings that can be customized to tune the SRA to best model your project.

No matter which approach you take, the Acumen toolset provides a quick and easy simulation process.

 

 

 

 

 

 

 

 

 

 

What to Expect in Part 2

Part 2 of this blog will delve into the interpretation of SRA results.

 

Yancy Qualls, PSP

Engagement Director, Schedule Subject Matter Expert (SME)

Humphreys & Associates, Inc.

Assessing Schedule Risk Using Deltek’s Acumen Risk 6.1 | Part 1 of 2 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 »

Using the Same Rate for BCWS and BCWP

, , , , , ,
Using the Same Rate for Budgeted Cost for Work Scheduled (BCWS) and Budgeted Cost for Work Performed (BCWP)
There is often an EVMS project managers debate regarding which rates to use for common budget costing EVMS data elements. For Actual Cost of Work Performed (ACWP), it is fairly obvious as the most recently approved actual rates are applied. A planning rate is generally used for BCWS and BCWP, but many in the EVM project management industry use incorrect rate application for the BCWP calculation. In some cases EVM contractors use a weighted average rate; the percent complete in hours multiplied by the dollarized BAC to derive the BCWP in dollars. This method is noncompliant with the EIA-748 Guideline 22 which states that if work is planned on a measured basis, then the BCWP must be calculated on a measured basis using the same rates and values. In other words, the rate and methods used to calculate BCWS and BCWP must be the same. As shown in Example #1, it can be seen that work planned in hours (BCWS) was performed as scheduled (BCWP) each month. Each hour was planned at a rate of $100/hour until the end of the calendar year when the rate increased to $105/hour. In this example, the rates used to calculate BCWS and BCWP are the same.
EVMS: BCWS & BCWP rate calculation example table #1
EVMS: BCWS & BCWP rate calculation example table #1

Example #2 below illustrates a very common scenario. In this example work that was planned in November and December was not completed until the next year. In January, the rate increased from $100 to $105. What should the BCWP in dollars be for both January and February?

EVMS: BCWS & BCWP rate calculation example table #2
EVMS: BCWS & BCWP rate calculation example table #2

For both January and February, the original 10 hours planned was earned at $105/hour equaling $1,050. The work that was planned in November and December, but completed late in January and February, was earned at its planned rate of $100/hour resulting in $1,000 of BCWP.  The sum ($1,050 + $1,000) equals the BCWP of $2,050 in each month. See the Example #3 graphic below:

EVMS: BCWS & BCWP rate calculation example table #3
EVMS: BCWS & BCWP rate calculation example table #3

Even though the rate was escalated in the new year, the BCWP that should have been earned in the prior year is calculated using the rate that was originally planned. The same approach would be logical if the work planned at $105 per hour were performed ahead of schedule in let us say, December of the prior year. It would be earned at $105 per hour even though it was performed in a time frame where the planning rate is $100 per hour. In some instances, business systems are programmed to earn as a percent of the entire Budget at Completion (BAC). This could result in an inaccurate BCWP dollar value. As an example, let us assume 10 hours are earned in September. If those 10 hours were 1/8 of the total BAC, then the BCWP dollars associated with this 10 hours would be $102.50 per hour and the contractor would be earning too much for those 10 hours. They must earn at the planned $100 per hour! Thus the rate used for BCWP is the same as for BCWS and is compliant with Guideline 22; one earns in the same manner as they plan to earn.

In summary, EVM concepts require that in order for the work to be complete, cumulative values of BCWS and BCWP must equal the BAC.  So, from a common-sense standpoint, if BCWP is earned at a different rate than that used for planning the BCWS, the Control Account (or even the Contract) cannot be closed properly.  Examples:

  • If BCWP earns at a lower rate, the BCWP would be, say, 98% of the BAC when the actual work is done.
  • Likewise, if BCWP earns at a higher rate, the BCWP would be, say, 105% of the BAC when the actual work is concluded.

Both of these scenarios violate the EVM concepts.

Using the Same Rate for BCWS and BCWP Read Post »

Scroll to Top