An operations methodology for teams whose work doesn't fit sprint boundaries.
The SysOps Framework replaces the single sprint cadence with three simultaneous cycles (daily, weekly, monthly) that match how operations work actually happens. It is a book, a methodology reference, and a set of downloadable templates - all in one repo.
If you are evaluating the project from the repository rather than the rendered site, use this order:
- Read Chapter 1 - The Challenge to check whether the problem matches your team.
- Read Chapter 3 - Framework Structure to understand the daily / weekly / monthly operating model.
- Use Getting Started for a 30-day pilot.
- Copy the templates from
templates/only after you know which cycle or practice they support.
The repository is intentionally both a book and an operating kit: the chapters explain the model; the templates make it usable.
Teams of highly skilled individual contributors sharing a team name but running separate projects, systems, and pagers. If Scrum/Kanban/SRE don't quite fit your ops mix, this is for you. See the full audience description for details.
Prerequisites: Go, Node.js, and Hugo extended edition.
git clone https://github.com/g3rhard/sysops-framework
cd sysops-framework
# Fetch the Docsy theme and its dependencies
git submodule update --init --recursive
# Install npm packages (required by Docsy for PostCSS, etc.)
npm install
# Start the dev server
hugo serverOpen http://localhost:1313/sysops-framework/.
The fully rendered site is published at g3rhard.cc/sysops-framework.
PDF and EPUB versions are built automatically from the latest tagged release:
- Releases page
- All templates are in the
templates/directory - PIR, change control, on-call policy, SLA, and more
| Artifact | Source | Trigger |
|---|---|---|
| GitHub Pages site | content/ + Hugo |
Push to main |
| PDF / EPUB | content/ → Pandoc + lualatex |
Tagged release (v*) |
content/docs/contains the book and rendered documentation.templates/contains reusable operational artifacts.scripts/diagrams/generates visual assets used by the site.- Keep vendor/tool recommendations dated and easy to refresh; durable concepts belong in chapters, fast-aging tool choices belong in tables or notes.
When contributing, prefer small documentation PRs that improve one reader journey at a time: primer, adoption, reference, or templates.
- Chapter 1 - The Challenge
- Chapter 6 - 12 Management Practices
- Implementation roadmap
- Glossary
- Appendices / templates
MIT - see LICENSE.