What Are the Key Tool Requirements in the DevOps Capability Maturity Model?

Background Introduction

Tool platforms are a crucial foundation for developing DevOps capabilities. The China Academy of Information and Communications Technology (CAICT) Digital Governance references the China Banking and Insurance Regulatory Commission's guidance on digital transformation , emphasizing agile technology management, rapid response development‑operations systems, and the adoption of integrated DevOps tools.

The DevOps Capability Maturity Model – Part 8: System and Tool Technical Requirements (referred to as the “DevOps System and Tool Standard”) defines the technical requirements for systems and tools used throughout the end‑to‑end software delivery lifecycle, including project and development management, application design and development, continuous delivery, test management, automated testing, and technical operations.

System and Tool Standard Overview

For each tool module, the standard distinguishes basic functions (mandatory) and advanced functions (recommended). Basic functions represent the capabilities a system/tool must have; advanced functions represent desirable capabilities.

Project and Development Management

Project Management

Project management tools should support member management, role and permission control, customizable project scope, project planning and milestone management, and change management. Recommended capabilities include communication matrix management, cost management, and procurement management.

Work Item Management

Work item management tools should support creation, modification, deletion, query, visualization, priority setting, assignee assignment, due date configuration, and reminders. Recommended features include customizable workflows, custom fields, review/approval processes, and commenting.

Plan Management

Plan management tools should support plan templates, creation, modification, deletion, query, and visual view templates. Recommended capabilities include linking plans to other resources such as code branches, pipelines, and documentation.

Document and Knowledge Management

Document Management

Document management tools should support custom directory structures, multiple upload methods, batch download, online preview of common formats, and preferably recycle bin, online editing, collaborative editing, and content search.

Knowledge Management

Knowledge management tools should support creation, modification, deletion, query, version control, and collaborative editing of knowledge items, as well as association, export, and multi‑dimensional indexing.

Team Collaboration

Team collaboration tools should support instant messaging, address book management, and team calendar management. Recommended features include directory service integration and operation log recording.

Statistics and Metrics

Statistics tools should measure progress, internal quality, external quality, delivery lead time, and defect resolution time, and present metrics via burn‑down charts, control charts, etc.

Project Portfolio Management

Portfolio management tools should allow setting portfolio owners, displaying progress and health, defining milestones, and assigning responsibilities.

Tool Landscape

Many mature open‑source and commercial tools exist for project and development management, such as JIRA, Asana, Gitee, PingCode, Worktile, Trello, Redmine, ONES, etc. Organizations should evaluate tools based on their IT management capabilities, objectives, and needs.

Contact Information

Standard and evaluation contacts: Liu (Phone: 15650786171, Email: [email protected]) Bai (Phone: 15910769206, Email: [email protected])