HabГ©rler - REMMONT.COM

[DAVIDEa]

Devops vision - Kabrinskiy Eduard


<h1>Devops vision</h1>
<p>[youtube]</p>
Devops vision <a href="http://remmont.com">Local news today</a> Devops vision
<h1>The Mission of a DevOps Team</h1>
<h2>July 16, 2015</h2>
<p>The mission of a DevOps team is to eliminate itself.</p>
<p style="clear: both"> <img style="float: left; margin: 0 10px 5px 0;" src="http://caseywest.com/images/for-posts/d ... s-team.jpg" />Image source. </p>
<p>DevOps is a practice, not a role. It's like agility. <em>Does your company have an agile team?</em> From Dave Thomas's agility redux:</p>
<blockquote><p><ul>
<li>You aren?t an agile programmer?you?re a programmer who programs with agility.</li>
<li>You don?t work on an agile team?your team exhibits agility.</li>
<li>You don?t use agile tools?you use tools that enhance your agility.</li>
</ul>
</p></blockquote>
<p>The same applies to the practice of DevOps. I suggest:</p>
<p><ul>
<li>You aren't a DevOps programmer?you're a programmer who automates deployment and operations.</li>
<li>You don't work on a DevOps team?your team runs the applications you build.</li>
<li>You don't use DevOps tools?you use tools that enhance your ability to ship business value.</li>
</ul>
</p>
<p>If your company has created a dedicated "DevOps team" it signals one of two likely scenarios:</p>
<p><ol>
<li>Things are already on fire and you're trying to catch up because you're late, or</li>
<li>You haven't realized that DevOps is a practice, like "agile", and your implementation of the concepts may be faulty.</li>
</ol>
</p>
<p>I have built DevOps teams (responding to scenario #1, everything is on fire) and the goal of that team is always to pay the up-front investment in modernizing the software delivery pipeline. Once the investment is paid thier role is to empower engineers to run the software they create themselves, and to enable operators to avoid fires in production and get a good night's sleep. Once that equilibrium is reached it's time to move on to work which genuinely creates business value.</p>
<p>If your organization has a long-lived "DevOps team" and the idea is they'll always be around, how is that different from "throwing it over the wall?" In this case it's just a second wall to an intermediary team between IT and engineering, and it isn't really a good long-term strategy. It can, however, get you over the initial changes required to embrace the DevOps ideal of "you built it, you run it."</p>
<p>It isn't a negative that DevOps teams are created. The rationale for their existence is often quite positive, just that the implementation isn't quite as polished and inline with the intent of the DevOps movement. It should be seen as a short-term tactic and you need to have a long-term strategy. Your DevOps team will never generate business value directly, so your sustained investment isn't wise.</p>
<p>The reduction of cycle time is, without question, a strategic advantage. Your dedicated DevOps team can get you from waterfall to agility much faster, and reduce cycle time drastically, which is a significant improvement in the short term. As the health of your architecture improves, and isn't materially affected by modification (deployment), the value gained by sustained investment in a DevOps team goes down. <strong>This is good.</strong></p>
<p>A recent report by Nancy Gohring of FierceDevOps suggests a new approach to solidifying the gap between engineering and IT: adding business people to its DevOps teams. (This reporting is not confirmed by Netflix, the company cited as its example.)</p>
<p>If you have a DevOps team their focus should be the reduction of operational costs over time, to the point where the [software deployment pipeline] is automated and the engineering and operations teams are well educated. A well automated pipeline enables engineering teams to bring their business value to customers: shipping. Educating both engineering and operations on <em>how</em> to automate and manage your architecture empowers them to do it themselves, which distributes knowledge and reduces your bus factor risk.</p>
<p>At this point you've achieved the success of enabling and empowering <em>everyone</em> in your product delivery organization to practice DevOps. Like the practice of agility, DevOps should be a consistent undertone as engineering delivers business value with low operational overhead.</p>
<p>Don't focus on operating your business. Focus on building it.</p>
<h2>Devops vision</h2>

<h3>Devops vision</h3>
<p>[youtube]</p>
Devops vision <a href="http://remmont.com">News highlights</a> Devops vision
<h4>Devops vision</h4>
The mission of a DevOps team is to eliminate itself.
<h5>Devops vision</h5>
Devops vision <a href="http://remmont.com">Devops vision</a> Devops vision
SOURCE: <h6>Devops vision</h6> <a href="https://dev-ops.engineer/">Devops vision</a> Devops vision
#tags#[replace: -,-Devops vision] Devops vision#tags#
https://ssylki.info/?who=auto-traders.remmont.com https://ssylki.info/?who=remmont.com/wa ... tt-careers https://ssylki.info/?who=auto-salvage.remmont.com https://ssylki.info/?who=insure.remmont.com https://ssylki.info/?who=bad-credit.remmont.com