SCRAM - Schedule Confidence Risk Assessment Methodology
SCRAM is a proven methodology for identifying issues and risks to program schedules.
Quantifies the impact of identified schedule risk
Focuses risk mitigation efforts
Promotes better scheduling practices
A world-first methodology, with interest from many quarters
Schedule is almost always the primary concern of project stakeholders and the Schedule Confidence Risk Assessment Methodology (SCRAM) is a powerful tool to identify and remediate root causes of project schedule slippage.
SCRAM can be used to:
Determine and quantify schedule compliance risk
Assess and analyse schedule feasibility
Validate tendered schedules in bids
Identify the root cause of project schedule slippage
Ascertain a project’s ‘health’ status
Focus project risk mitigation effort
SCRAM uses the Root Cause of Schedule Slippage (RCASS) model to analyse and identify schedule slippage drivers and systematically identifies the fundamental root cause.
SCRAM has been developed over a number of years evolving from reviews of projects in trouble and is used to assist with remediation of major projects of concern or Interest.
SCRAM is used to understand the schedule impact of problems that may occur in the future and to deal with the risk. It uses Schedule Risk Analysis, a process that uses statistical techniques to quantify schedule risk based on technical, programmatic and other risks in a project and software parametric modelling that uses actual performance to date to forecast software completion.
Schedule Risk Analysis simulates what may happen if the schedule does not go according to plan and the results provide a picture of the potential impact of risk on schedule.
Following a SCRAM Review, projects should use the results to develop and implement action plans to remove root causes of schedule slippage and reduce risks and ensure that the risks don't become reality.
It may be necessary to revise the schedule and SCRAM Reviews should be repeated to ensure actions to address root causes and risks are successful. Finally, schedule performance should be monitored and controlled using appropriate metrics.
There can be multiple causes of schedule slippage which include:
Optimistic, unrealistic estimates
Conflicting views from stakeholders
Evolving or unstable requirements
Poor contractor performance
Use of immature technology
Dependencies not realized
Poor monitoring of workloads
Inadequate staffing and lower than expected productivity
Poorly constructed schedules
Program managers are flooded with information, making it difficult to distinguish between symptoms and root causes of schedule slippage. To declutter and organise the massive amounts of information, SCRAM Assessors utilise the RCASS model.
The seven key SCRAM Review Principles are:
Corroboration of Evidence
Sharing Results, Openness and Transparency
For more information on SCRAM and to download resources visit the SCRAM website http://www.scramsite.org
Commercial: Australia, Asia, Africa
Director - RedBay Consulting
Commercial: Americas and Europe
Elizabeth (Betsy) Clark
President - Software Metrics Inc.