A transparent, self-governing management model for DevOps teams of any size.
As a DevOps team grows, it splits into fixed sub-teams and rebuilds the silos DevOps exists to break. Open Kitchen prevents that.
The team is organized around technical concerns. Each concern has one group of engineers. Every engineer is in several groups, and membership rotates, so no group becomes a silo. Each group writes its own recipe (how it works), publishes its work weekly, and is judged by everyone it affects.
Like an open kitchen, all work is visible.
| File | Contents |
|---|---|
| MODEL.md | The model |
| MEASURING.md | Measuring and reporting value |
| ADOPTING.md | Getting started |
| FAQ.md | Questions and open challenges |
| templates/ | Ready-to-copy templates |
| standards/ | A sample DevOps manifesto |