3.8 KiB
name, description
| name | description |
|---|---|
| operating-capabilities | The capability catalogue: what an operating organisation may need to be able to do, in our own words, with the industry frameworks each entry draws on. Use when choosing the Capabilities of an operating model and writing the Checks on them. |
The capability catalogue
assets/catalogue.yaml lists the Capabilities an operating model is built from. assets/sources.yaml is the register of the frameworks they cite.
How to use it
- Your task's context lists the entries code found to apply to this operating spec, under
capabilities_proposed. Start from those. - Take every proposed entry, or say in your Deliverable why one does not apply. Add any other entry the solution needs.
- A Capability names its entry by
catalogue. One the catalogue does not have iscustom, with areason: use it only when no entry fits, never to rename one. - Give each Capability the Items it covers and the Operational requirements it serves. Every Item must be covered by at least one Capability, and every Operational requirement served by at least one.
- An entry's
typical_checksare where to start when writing Checks. Rewrite each for this solution: name the Item, and put the customer's own numbers in.
What the sources are for
A source says where an idea comes from. Cite it in a Deliverable as the catalogue does, by framework and by the name of the part. Never quote a framework's text and never say an operating model is certified against, or compliant with, a framework: the catalogue draws on them and promises nothing about them.
The register's status says whether a person has checked the references. While it is unverified, say so wherever a source is cited to a customer.
People and teams
Two frameworks shape who does the work, not only what it is:
- Team Topologies (
team-topologies). An operating model for a platform may group its Roles into teams, each of one of four kinds:stream_aligned,platform,enablingorcomplicated_subsystem. Two teams work together in one of three modes:collaboration,x_as_a_serviceorfacilitating. A collaboration is a stage for discovering something together, not a standing arrangement, so it says when it ends. - Platform as a product (
platform-as-a-product). A platform is run for the teams that build on it, as a product they choose to use: someone owns its roadmap and orders the backlog by what slows those teams down, adoption is earned by a supported default path, and their satisfaction is measured.
For a platform foundation, the catalogue proposes platform-product-management, self-service-and-golden-paths and enablement from these.
Measuring at three layers
delivery-and-developer-experience-measurement draws on three frameworks at once, because each measures a different layer and none stands in for another:
| Layer | Framework | What it tells you |
|---|---|---|
| Outcome | dora-metrics |
How fast and how safely changes reach production: lagging. |
| Guardrail | space-framework |
Whether productivity is sustainable across several dimensions, including wellbeing. |
| Leading signal | devex-framework |
The friction, feedback loops and cognitive load teams meet: what to improve next. |
Never write a Check that measures only one layer and calls it productivity.
Every one of these is a means. In the operating model each is a Measure tied to a business outcome the customer stated: deployment frequency to "new products reach customers sooner", developer satisfaction to "we keep the engineers we hire", time to restore to "payments are never down for long". A measure that serves no stated outcome is not measured.
Two things are called DORA. eu-dora is the European regulation on operational resilience. dora-metrics is the research programme's four delivery measures. Name each in full.