DevOps topics
DevOps: principles, practices and tools
What DevOps is, how teams put it into practice and how to keep every change to production under control — explained without jargon, with the practices that apply whatever tools you use.
Articles
DevOps principles
DevOps joins development and operations around one goal: delivering valuable changes quickly and safely, with fast feedback at every step.
Read the guide
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.
Read the guide
DevOps tools
A DevOps toolchain covers planning, source control, CI/CD, testing, release governance and monitoring. What matters is how well the pieces connect.
Read the guide
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.
Read the guide
Tutorials
DevOps automation
Automate first what is repetitive, error-prone and frequent: builds, tests, deployments and the links between the work and the code.
Read the guide
Continuous testing
Continuous testing checks every change as early as possible and keeps the results as evidence for whoever has to authorize the release.
Read the guide
DevSecOps: security in the pipeline
DevSecOps builds security into every stage of delivery: scanning code and dependencies, limiting access and keeping an audit trail of every change.
Read the guide
Observability
Observability uses logs, metrics and traces to understand what a system is doing — and, after a release, whether the change caused the problem.
Read the guide
Feature flags
Feature flags separate deploying code from releasing it: a change ships switched off and is turned on, or back off, without a new deployment.
Read the guide
Continuous delivery
Continuous delivery keeps every change ready to release: built, tested and deployable at the push of a button, in small and frequent batches.
Read the guide
Database change management
Changes to production data need their own control: a reviewed script, a backup, separate business and technical authorization and an execution window.
Read the guide
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.