IT Principles and IT Guidelines

posted 2.7.2017

IT Principles are defined to secure realization of company's goals and objectives - they define "how" (see exemplary list of principles). IT Principles can be understood as "Information Technology constitution" approved by the decision makers. As this is a constitution (law) - exceptions and violations are not allowed.

Besides of Principles, Key IT Guidelines should be defined in order to achieve the benefits related to Information Technologies, e.g. integration guidelines are to decrease the cost and effort of integration. In justified situations, ie. when other benefits are valued over IT benefits these guidelines might be violated. E.g. integration guidelines might be omitted to quickly integrate with business partner. In such cases a dispensation should be granted (and then tracked).

Why:

Principles represent company-wide requirements concerning the use of information technologies. They form the foundation for making decisions about information technologies at all levels of the organization. In particular, in the projects, during analysis phase, when there is a lot of specific decisions taken – Principles allow early filtering of unacceptable solutions (from the company-wide benefit point of view).

Principles compliance during development and evolution of IT architecture components (mainly in projects) is an effective way to ensure a consistent and measurable level of quality and compliance of IT architecture to the business goals of the company.

Read more about: