https://github.com/ghostinthewires/Team-Handbook-Template

An employee / team handbook template
https://github.com/ghostinthewires/Team-Handbook-Template

devops devops-team devops-tools devopsteam handbook process sre team-devops template

Last synced: 26 days ago
JSON representation

An employee / team handbook template

• Host: GitHub
• URL: https://github.com/ghostinthewires/Team-Handbook-Template
• Owner: ghostinthewires
• Archived: true
• Created: 2018-08-23T10:01:50.000Z (over 6 years ago)
• Default Branch: master
• Last Pushed: 2018-10-05T13:35:23.000Z (about 6 years ago)
• Last Synced: 2024-08-03T16:09:43.119Z (4 months ago)
• Topics: devops, devops-team, devops-tools, devopsteam, handbook, process, sre, team-devops, template
• Language: PowerShell
• Size: 1.45 MB
• Stars: 20
• Watchers: 2
• Forks: 8
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

• awesome-systools - Team-Handbook-Template

README

        
# Team-Handbook-Template

As I started growing my DevOps team this year, I looked for a starter-kit of values and best practices. A lot of great work is being done to discuss cultural problems and their solutions, but it’s coming from a lot of different voices around the web and very little is written in the form of an easy to use Team Handbook.

I wanted to put what I've learned into practice, so I decided to write my own handbook and open source it.

This repository contains all of the values & practices that we use here. It represents many hours of research, lots of thoughtful debates, and some serious introspection. It’s certainly not perfect, but I think it’s an exciting place to start.

Feel free to fork this repository and use any or all of these policies, and to modify them in whatever way makes sense for your company. I hope that by publishing them, other companies can benefit from my research and improve their own teams culture.

All feedback and suggestions (especially in the form of pull requests) are very appreciated. I’ve gotten several different perspectives to help arrive at these policies, but I am certainly missing many more and making mistakes as a result. This is a work in progress that I hope will get better with more time and more contributors.