Viewing as , ,
Vendor access
This part is for Aigna staff
Vendors see their own installation and the device reference they need to build it: device types, setup guides and models. Everything else stays with Aigna.
Go to your installationKeia Method· Level 3 · How it fits · 4.5
Agile, DevOps and SRE
Ways to deliver change in small steps with fast feedback, and to run services by measured reliability.
- How Keia relates
- Companion: standing rules and the learning loop borrow their habits
- Which version
- The Agile Manifesto (2001); the Scrum Guide (November 2020); DORA's five software delivery metrics (dora.dev, 2026); Google's Site Reliability Engineering book. Keia's standing rules, its change model and its learning loop sit alongside these; Keia does not deliver software.
How the ideas map
Each Keia idea, the practice it sits beside, and what Keia adds.
| Keia idea | Agile, DevOps and SRE practice | What Keia adds |
|---|---|---|
| Start from the building | SRE: service level objectives | Each service has an owner and a target; its map runs from the internet circuit to the device, lit by health |
| Capture, don't ask | SRE: eliminating toil; monitoring | Alerts arrive filled in, so nobody retypes them; a fix that keeps recurring becomes a standing rule instead of repeated manual work |
| Answer first | DORA: change fail rate, failed deployment recovery time | Pages open with within target or past target; alerts that led to an action are counted against alerts raised |
| Own it, hand it on | DORA: streamlining change approval | DORA found that heavyweight external approval did not lower change failures. A standing rule is approved once by its owner, runs within caps, is read back after every write, and halts on failures |
| Learn as you go | Scrum: the Sprint Retrospective. SRE: blameless postmortems | A lesson is captured where the work closes and proposed into the setup guide. Nothing scores or ranks a person |
Use your normal process here
- Software delivery: builds, tests, pipelines and deployments of code
- Backlogs, sprint planning and a team's cadence
- Error budget policies for software releases
- On-call rotations and paging
- Measuring software delivery with DORA's metrics
Words side by side
| Keia says | They say |
|---|---|
| Standing rule | Automated runbook; a pre-approved change |
| Unable to complete, rolled back | Failed deployment; rollback |
| Routine work a standing rule does | Toil, when a person does it by hand |
| Lesson; captured fix | Postmortem action item; retrospective improvement |
| Within target | Service level objective (SLO) met |
Sources
Official source. Agile Manifesto; Scrum Guide; DORA; Google: SRE books
Checked 30 September 2026.
Try it in the demo
Opens as Declan, who owns the network and comms rooms. Everyone in the demo is made up; nothing you do leaves this browser.
- Open Standing rules: each names its owner, its caps and what it can put back.
- Open the PoE rule: its conditions, what it reads, what it writes, and how it is read back.