“Just fell in love with @Rundeck to let non-ops people run @ansible playbooks.”-CTO, Digital Agency
"But... how?" is an immediate response we often hear when presenting the idea of moving to a Self-Service Operations model that allows the standardization and delegation of operations tasks to people outside of traditional ops roles. This is usually followed by a statement like "the benefits make sense and the end-state is appealing, but I'm having difficulty seeing how we get from here to there."
We've learned that this uncertainty is usually an artifact of the historical belief that automated operations procedures are a monolithic task. As people separate their thinking about automated operations procedures into distinct elements, the belief dissipates, and the path to Self-Service Operations becomes clearer. These elements are: the ability to define a procedure, the ability to execute that procedure, and the governance around that procedure. Once separated, you can start to see how each element can be distributed to the teams and roles in your organization where it most improves the flow of work or utilization of labor.
This Wednesday, 26 July, Rundeck will be featured at a "mega-meetup" that is the combination of several local Singapore meetups. This meetup is being help in conjunction with the RSA conference being held at the Marina Bay Sands conference center.
Rundeck's Damon Edwards will also be speaking during RSA at DevOps.com's DevSecOps mini-conference on Tuesday July 25.
The following are the details and how to get free admission to both events:
Self-Service Operations is a design pattern that helps Operations teams decrease support costs while improving agility and responsiveness. Self-Service Operations enables you to safely shift operations activity to where your workforce can be best utilized. This includes moving the ability to take action, by pushing a button or calling an API, closer to the problem or party in need.
Employing Self-Service operations clearly benefits Operations teams, while also boosting the productivity of the teams that they serve and improving overall business efficiency. In high-performing companies that have already applied this design pattern, we've observed that the benefits accrued by each constituent group (Operations and the groups served by Operations) reinforce each other and compound over time.
Calculating a return on investment for Self-Service Operations will always depend on a company's unique environment. However, we've found the following methods of measuring ROI to be effective for most organizations: