Anyone implementing DevOps
Click here to access the DevOps templates
Achieve project success by successfully implementing DevOps in your organization.
DevOps is a term given to the joint ownership by development and operations of the entire life cycle. It spans the end to end delivery pipeline, maximizes the predictability, efficiency, security, and maintainability of operational processes supported by automation.
C.A.L.M.S. is an acronym for the conceptual framework for the integration of the development and operations teams:
- Culture – Own the change to drive collaboration and communication
- Automation – Take manual steps out of your value chain
- Lean – Use lean principles to enable higher cycle frequency
- Metrics – Measure everything and use data to refine cycles
- Sharing – Share experiences, successful or not, to enable others to learn
DevOps works by improving the quality and reliability of the Development output and the agility of Operations. Automation, standardization and collaboration are the cornerstones of this effort.
Click image to enlarge
|DevOps Maturity Model||The DevOps C.A.L.M.S. Maturity Model allows a company to compare itself against a clearly defined benchmark. This model defines each level of maturity and helps with the journey of to the next level as part of the roll-out of DevOps in a company.|
|Methodology||Decide on the development methodology your team will use. Generally for DevOps, this is Agile. Agile and DevOps are similar, but Agile represents a change in thinking, whereas DevOps actually implements organizational cultural change.|
|Continuous Integration (CI)||Implementing the practice, in software engineering, of merging all working copies to a shared mainline several times a day.|
|Continuous Deployment (CD)||A software engineering approach where teams produce software one releasable feature at a time. To achieve CD you need a simple and repeatable deployment process.|
|Continuous Delivery (CD)||As soon as a feature or feature set has been completed, it can be automatically rolled into production.|
Here are the key benefits of the RequirementONE DevOps C.A.L.M.S. Solution.
DevOps is a movement that is still evolving, meaning that there are no standards to follow, or known implementation methodologies. By working through this list, best practice advice from across the sector is presented in a format that allows you to make the decisions for your organization, and kick start your DevOps project.
Models for best practice approaches can be selected from the Solution Store and customized to make them appropriate for your organization. This reduces the risk of errors and kick starts your project
A Single Point of Truth
A central online repository stores each requirement as a record. Updates, comments and meta-data are controlled and tracked individually. This means no open questions about the agreed upon project requirements, or who made which change when.
A Collaborative Platform
The multi-user environment allows administrators control over which users have access to which project components. This means that information is accessible to those who need it in real time, fully secure and auditable.
In-line analytics highlight gaps in coverage, traceability of changes and status of implementation efforts
Typical Use Cases
Here is a typical, but not exhaustive, list of roles and associated use cases that would interact with this solution.
These apps and templates are used for the solution.
* Scrum is the most common way to introduce Agile into organizations due to it's simplicity and flexibility. Review the Agile (Scrum) templates here.
- Select an existing, or create a new project
- Click on the Solution Store, and select the DevOps C.A.L.M.S. templates listed above
- Once you have the templates, follow the Implementing DevOps C.A.L.M.S. plan.
This is a starting point for DevOps C.A.L.M.S. rollout. Customize this solution to meet your specific DevOps needs.
Questions or Comments?
Respond to this post if you want to comment on the template or ask the author a question.