COBIT® Compliance Oriented Architecture

What are “Best Practices”? Definition: A “Best Practice” is the best identified approach to a situation based upon observation from effective organizations in similar business circumstances. Descriptive NOT Prescriptive It applies anywhere: IT Service Management Existing staff with existing skills can do it Can be maintained by staff/vendor Safe – not pioneering Why does Best Practice add value? IT departments are shifting from a technology-driven approach to an alignment to business needs, and ultimately the cost efficient on-demand model. Businesses depend more and more on technology to promote and deliver their products to market. The ethos behind the development of ITIL is the recognition that organisations are becoming increasingly dependent on IT in order to satisfy their corporate aims and meet their business needs. IT has to deliver effective solutions/services Depending on the contest, customers can be the clients for companies providing IT services as product, or the IT department which provides an IT service to the company itself. QUALITY: Meeting (customer’s) expectations (Fit for purpose). SERVICE: Anything the customers want, when they wanted, at the time they wanted, at the cost they find acceptable and at the quality they agreed. Improve the return on IT investment - put the processes in place that improve utilisation of resources and ultimately their effectiveness and reduce duplication of effort.

Why should you use a Best Practice Enables a process driven approach Improves quality of the delivered IT services Streamlines communication between users and IT Aligns IT with the current and future needs of business Reduces long-term cost of service provisioning Gives people a common language to use Lowers the TCO

COBIT IT-Process Framework

Management Guidelines Components IT governance guideline Generic IT process guideline For each of the 34 IT processes one maturity model 5 to 7 KGIs 8 to 10 CSFs 6 to 8 KPIs As described earlier, two generic guidelines were developed. For each of COBIT’s high-level control objectives, a number of KGIs, CSFs and KPIs were defined, as indicated. The resulting guidelines are generic, not industry specific and organisations need to consider their application and extension based on their strategic needs, resource availability and cultural factors. The basic concepts presented in the framework of the Management Guidelines provide a basis for adapting them to the needs of individual organisations.

Overview Management Guidelines Presentation In closing, this illustrates one more time how the Management Guidelines integrate and present the new and existing concepts and functionality of COBIT, at the high-level control objective level. Goals support business objectives and are measured by KGIs. The IT enabler provides information with the criteria needed to support the business goal, considers CSFs that leverage specific IT resources and is measured by KPIs. Together with the Maturity Models, the KGIs, CSFs and KPIs result in a toolset that will provide management with new options in directing, controlling and managing IT.