This post provides simple principles and examples for CTOs to understand and implement DevOps in their companies. It covers the meaning of DevOps, responsibilities of DevOps Engineers, choosing the right tools, and setting useful goals.
Table of contents
Who this article is forUnderstand the desired resultDevOps has a simple meaningChoose a balance: Enabler, Doer, or AutomatorKnow what things you should enable, do, or automateChoose the right toolsSet useful goalsEnablers: Choose the Tools-to-Knowledge BalanceDoers: Have a good reason to do itAutomators: Have a good reason to automate itCreate available DevOps CapacityThere are 3 types of DevOps capacityWhen to focus on what: Common DilemmasBONUS: An example setup for a CTO approaching ProductionAnother Bonus: DevOps Dictionary for Human Beings7 Comments
Sort: