Dr. Elizabeth (Betsy) Clark is President of Software Metrics, Inc., a Virginia-based consulting company she co-founded in 1983. Dr. Clark is a primary contributor to Practical Software Measurement (PSM). Dr. Clark was also a principle contributor to the Software Engineering Institute’s (SEI) core measures. Dr. Clark is a Research Associate at the Center for Systems and Software Engineering at USC. She collaborated with Dr. Barry Boehm and Dr. Chris Abts to develop and calibrate the COCOTS model. She is a consultant to the Institute for Defense Analyses and the Software Engineering Institute. She is also a primary contributor to SCRAM. Dr. Clark received her B.A. from Stanford University and her Ph.D. in Cognitive Psychology from UC, Berkeley.
Journal Articles
An Overview of the Schedule Compliance Risk Assessment Methodology (SCRAM)
Schedule slippage is an unfortunate reality for many large development programs. The Australian Defence Materiel Organisation Schedule Compliance Risk Assessment Methodology (SCRAM) provides a framework for identifying and communicating the root causes of schedule slippage and recommendations for going forward to Program and Executive-level management. It is based on a repeatable process that uses a root cause analysis of schedule slippage model to locate factors that impact program schedule along with a “health check” of the documented schedule, assessing its preparation and probability distribution of completion dates. SCRAM can be used at the commencement of a program to validate a proposed schedule and identify potential risks, during program execution as a “health check”, or as a diagnostic tool to identify root causes when schedule slippage occurs. To date, SCRAM has been applied to a number of major development acquisition programs in Australia and the United States. According to one documented report, seventy-eight percent of US Department of Defense Programs have experienced some form of schedule slippage [1]. Schedule slippage is a symptom of any number of problems or causes occurring on a project.
View Article
Leave a Comment
You must be logged in to post a comment.