DevOps Implementation
Implementing a good DevOps
process will benefit any organization to a great extent. This includes
planning, developing, integration and automation. There are a few product areas
that can immediately benefit from some integration and automation tasks that
will reduce the manual work involved, increase the responsiveness of the support
team and optimize the resources used.
A typical DevOps implementation
will integrate and automate the different process with tools appropriate to the
customer.
DevOps Engineer need to engage
with the customer and can perform below-listed steps that will enable him to
implement DevOps in any organization.
v Finalize with the
management the objectives for a DevOps implementation.
v Document (if not
existing earlier) existing processes and systems.
v Create a baseline
measurement of the current DevOps tools and capability.
v Uncover opportunities
for improvement.
v Identify the most
impactful areas to the business.
v Document ideal end-state for teams.
v Generate and present a
roadmap to implement/improve DevOps process using relevant platforms and tools.
v Prototype implementation
to improve one area of improvement.
Understanding the current
situation
DevOps engineer will need to engage
in conversation with the respective teams in the organization and asses the current
DevOps capabilities and the tools used. This is done with the help of a
questionnaire that will be shared with the stakeholders. A properly filled up
questionnaire will give a good understanding of the current setup at the
customer organization.
Finalizing the DevOps objectives
DevOps engineer with the help of
stakeholders will finalize the DevOps objectives of the implementation and also
an appropriate timeline for achieving those objectives.
Documentation of
existing processes
The current processes, tools
& systems used by the customer will be documented if no such document
exists already with the customer.
Baseline measurement
Before starting the project,
some measurements to indicate the current DevOps tools and capability will be
noted down. Some examples of these measurements would be the Number of releases in
a year; Average time to fix a defect and so on. This measurement will be
compared after the engagement is completed.
Opportunities for
improvement
During the analysis of the
current process and tools, there will be some areas that will require improvement
in terms of process or technology. This will be incorporated into the final
presentation.
Impactful areas
Each area of improvement will be
analyzed for business impact and the areas with high impact will be documented.
Ideal end-state
After all the analysis is done
and processed, the ideal end-state from a DevOps standpoint will be documented
and presented. This will include the process and tools that will fit the
customer requirement. Some of the processes would be: Code review process;
Versioning best practice; Infrastructure recommendation to use of private cloud; and so
on.
Roadmap
Finally, a roadmap that will
show the steps to implement a new DevOps process or to improve the existing
process and the list of tools that are recommended will be presented to the
customer.
Prototype
DevOps engineer then need to
show the benefit of the new DevOps process by prototyping and demonstrating one of
the areas identified for improvement.
Could you please post some blogs related to Security in DevSecOps
ReplyAs part of DevSecOps, what kind of Security rules to be followed and any free/licensed tool that are used in the organizations.
Thanks
Rajesh