Community guides for software creators. Check it out…
The goal of the ProdOps Guides is to provide teams, companies and organizations a framework to understand how software impacts business needs.
Guides:
- Accuracy:
- Did we build what our customer wanted?
- Did we align our requirements with company goals?
- Utilization:
- Did we leverage our developers to the best of our abilities?
- Did we scope the work in a way that allows small, iterative releases?
- Did we keep our team small enough to allow for effective collaboration?
- Precision:
- Did the product perform to expected standards?
- Did we minimize our technical debt?
- Did we define tests before implementation began?
- Efficiency:
- Did we create a flexible environment?
- Did we create a scalable environment?
- Did we create a secure environment?
Put your values to work - @webdog (in Paris)
We've shared our vision and priorities for this project in our roadmap.
Our goal is for this project to reflect community best practices, so we'd love your input! Got a question or an idea? Check out our contributing guidelines for ways to offer feedback and contribute.
Content is released under CC-BY-4.0, which gives you permission to use content for almost any purpose but does not grant you any trademark permissions, so long as you note the license and give credit, such as follows:
Content based on github.com/github/open-source-guide used under the CC-BY-4.0 license.
Code, including source files and code samples if any in the content, is released under CC0-1.0.
This means you can use the code and content in this repository except for GitHub trademarks in your own projects.
When you contribute to this repository you are doing so under the above licenses.
Screenshots in the guide are used according to various permissions.
The initial release of the guide was authored by @leefaus, @coryvj, and @kingmichaelj.
Thanks to @bkeepers for helping me along this journey.