DevOps frameworks

Scrum, Kanban, ITIL 4 change enablement and CALMS answer different questions. Most teams combine them: one to plan the work, another to govern the change.

Scrum and Kanban for the work

Scrum organizes work into fixed-length sprints with a prioritized backlog and regular reviews. Kanban visualizes the flow on a board and limits work in progress so items finish instead of piling up. Both make the work visible, which is the first condition for improving it.

ITIL 4 for the change

ITIL 4 calls it change enablement: classifying each change by risk and giving it the right level of authorization. Standard changes are pre-approved, normal changes are assessed, and emergency changes follow a fast path that is still recorded.

Combining them without bureaucracy

  • Plan and track the work with Scrum or Kanban.
  • Govern only the changes whose risk justifies it.
  • Keep approvals and evidence on the same record as the work.
  • Review the flow with data, not with status meetings.

How DevGob applies it

DevGob ships Scrum and Agile processes for the work, and a Deployment flow with Normal, Standard and Emergency change types and two committee gates for the change — configurable per workspace.

Read it in the documentation

Related topics

DevOps principles DevOps joins development and operations around one goal: delivering valuable changes quickly and safely, with fast feedback at every step. Change management in DevOps Change management decides which changes need authorization, who gives it and what evidence is kept — without slowing down the changes that don't. DevOps tools A DevOps toolchain covers planning, source control, CI/CD, testing, release governance and monitoring. What matters is how well the pieces connect.

DevOps with governance, on one record

DevGob plans the work and governs every change on its way to production: backlog, sprints, committee authorizations, install evidence and an audit trail.

Request a workspace Documentation