8.2: Unmet Expectations
Identify Where EA Program Expectations Are Not Being Met Other Information:
Through their respective reports and review activities, the EAESC, the CIO, and the Chief Architect will be able to identify
what, if any, EA program expectations are not being met. For example, if risk management has been effectively implemented,
program risk lists should be regularly generated that assign a risk level based on impact and probability, define risk mitigation
strategies, report on progress in implementing these strategies, and whether the progress being made is successfully addressing
the risk item. Also, periodic configuration audits should be conducted to ensure that EA configuration items are being defined,
controlled, and reported. The EAESC, CIO, and Chief Architect can also rely on independent reviews by the quality assurance
function or a verification and validation agent to advise them of deviations from expectations. These deviations may be program
management plan-related, such as omission of work tasks, delays in the completion of work tasks, or additional costs to complete
work tasks; or they may be management function-related, such as not following change control procedures, not adhering to the
selected EA framework, or not engaging SMEs and domain owners within business and technical areas.
Indicator(s):
|
