IS 19313 : 2025 Software and Systems Engineering - DevOps - Principles and Practices
New Standard from Last Update.
1 SCOPE
This standard provides principles, practices and maturity model for implementing DevOps framework to deliver secure and quality software and increase the speed to market software with frequent/on demand releases.
The standard covers the following practices:
a) Continuous planning;
b) Configuration management;
c) Continuous integration;
d) Continuous testing;
e) Continuous delivery;
f) Continuous deployment;
g) Continuous monitoring; and
h) Continuous experimentation.
This DevOps standard is applicable to
a) Software development projects including enhancements and operations;
b) Product based teams with development, operations, and support;
c) Infrastructure projects and support;
d) DevOps enablement and platform teams;
e) This standard is applicable to Indian organizations that are aiming to adopt DevOps framework/practices. Any deviations from this standard will be identified and documented by the organization; and
f) The practices defined in this standard are applicable for a single DevOps project, as well as for an organization performing multiple DevOps projects. These practices are applicable throughout the lifecycle of software systems, products and services.
2 CONFORMANCE
2.1 Intended Usage
This standard is meant for use by DevOps Sponsors, Practitioners, and stakeholders for both acquirer (or customer) and supplier organizations.
This standard is written to be applicable to all types of IT projects, irrespective of the technology and domain/industry vertical.
2.2 Full Conformance
Full conformance is achieved by demonstrating that all the requirements of all the practices have been satisfied using the outcomes as evidence.
2.3 Tailored Conformance
An organization should document the deviations expected from the practices with rationale and obtain sign-off before use. Tailored conformance is achieved by demonstrating that requirements for the practices along with the documented expected deviations, have been satisfied using the outcomes as evidence.
If certain practice requirements for a level are not feasible due to technical limitations (such as for legacy applications or COTS products) or due to organizational strategy, such tailoring and rationale need to be documented by the organization. Conformance will be established against this tailored scope.
3 REFERENCES
The standards given below contain provisions which, through reference in this text, constitute provision of this standard. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this standard are encouraged to investigate the possibility of applying the most recent edition of these standards:
| IS No. | Title |
| IS/ISO/IEC 2382 : 2015 | Information technology - Vocabulary (first revision) |
| ISO/IEC/IEEE 24765 : 2017 | Systems and software engineering - Vocabulary |
For dated references, only the edition cited applies.
For undated references, the latest edition of the referenced document (including any amendments) applies.