Sources for the IT management comparison
Research record
- public-material snapshot date: August 3, 2026;
- SAF version: 0.7.0;
- full-study languages: Russian source and complete English translation;
- status: non-normative comparison;
- unit of analysis: concepts, relationships, lifecycle, roles, measures, and joint use with SAF;
- scale: direct, partial, composite, absent, or not applicable, plus high, medium, or low confidence.
Sources were checked against official public pages. Paid, restricted, and license-limited materials were not reconstructed from secondary summaries.
RITM
- Official RITM site — current positioning as the Rational IT Methodology.
- What RITM is — principles, model elements, and management areas.
- RITM public library — open and evolving body of material.
- itSMF Russia — RITM body of knowledge — the earlier name and stated development directions.
RITM has no stated stable methodology release number. The portal build number is not interpreted as a content version.
ITIL and ITSM
- PeopleCert — ITIL Foundation (Version 5) — public description of concepts, the four dimensions, ITIL Value System, lifecycle, and practices.
- PeopleCert — ITIL Version 5 explained — staged release and continued parallel availability of ITIL 4.
- PeopleCert — ITIL Service (Version 5) — service relationships, service levels, resilience, and improvement.
ITSM has no single normative owner. The general characterization of the field is derived from the intersection of official ITIL, ISO/IEC 20000, and FitSM materials and is marked as analytical synthesis.
ISO/IEC 20000
- ISO — ISO/IEC 20000-1:2018 — current third edition, 2023 confirmation, and Amendment 1:2024.
- ISO/IEC JTC 1/SC 40 — Practical Guide — public overview of the standard's purpose.
The SAF page is not an interpretation of certification requirements and does not replace the licensed standard text.
FitSM
- FitSM — standard — purpose of lightweight ITSM and composition of the family.
- FitSM — downloads — current version 3.0 core documents and FitSM-6 materials.
COBIT
- ISACA — COBIT resources — public description of COBIT 2019, publications, and focus areas.
- ISACA — COBIT 2019 Governance & Management Objectives — purpose of the Core Model and 40 objectives.
Detailed COBIT tables, objectives, and diagrams are not reproduced.
IT4IT
- The Open Group — IT4IT Standard, Version 3.0.1 — current edition incorporating Technical Corrigendum 1 for the 3.0 line.
- The Open Group — IT4IT catalog.
- The Open Group — IT4IT overview.
The official reference architecture and supplied ArchiMate model are not copied.
SRE
The body of knowledge is treated as an evolving engineering practice, not a versioned conformity model.
DevOps
- DORA — capabilities and 2025 research — empirical capabilities and outcomes; DORA is not treated as a general DevOps metamodel.
- Google Cloud — DevOps — movement, speed, reliability, and shared ownership.
- Microsoft Learn — DevOps overview — planning, development, delivery, and operation.
- AWS — What is DevOps — culture, practices, tools, and lifecycle ownership.
- ISACA — COBIT Focus Area: DevOps — governance projection of DevOps.
Only recurring common ground is included in the conclusions. One vendor's position is not presented as a universal definition.
Copyright and marks
TOGAF®, ArchiMate®, and related marks belong to The Open Group. IT4IT™ is a mark of The Open Group. ITIL® is used as a mark of its owner, PeopleCert. COBIT® is a mark of ISACA. ISO and ISO/IEC standard designations are used only to identify sources. RITM, FitSM, SRE, DORA, DevOps, and organization names may be protected by their respective owners.
SAF does not claim affiliation, endorsement, certification, conformance, or compatibility with any listed organization or approach.
Limitations and update policy
- The RITM public library and the SRE, DORA, and DevOps bodies of material change without a shared release cycle, so a snapshot date is mandatory.
- ITIL Version 5 is being introduced in stages; new public materials may refine the terminology.
- ISO, COBIT, and IT4IT have licensing restrictions; this analysis uses only permitted public descriptions and paraphrase.
- Absence of a public concept does not prove its absence from restricted material or a particular implementation.
- Any source update requires rechecking the mapping type, confidence, and conclusions, not merely changing a version number.