facebook-pixel

Marc Hornbeek

About Me

Marc Hornbeek, known as “DevOps_the_Gray” and industry events speaker, is a DevOps Consultant at  Trace3. A seasoned DevOps consultant, adviser, educator, mentor, and author, he has performed assessments for over 60 organizations. Awarded IEEE Outstanding Engineer, 2016, Western USA, he is a Senior IEEE member for 42 years. He is the author of the  Continuous Delivery Architect certificate course and DevOps Test Engineering certificate course for DevOpsInstitute.com and many publications.

Defining DevOps: How Do You Know When You Have Achieved DevOps?

How do you know when you have achieved DevOps? and you are likely to get different answers. A practical answer to how do you know when you have DevOps depends on having a definition. While defining DevOps itself has been elusive, an enterprise definition is needed for alignment and progress measurement. Considering that DevOps needs continuous flow to accomplish business goals, it can be said you have DevOps when you have implemented continuous flow for at least one model application.

Twenty-Seven-Factor Assessments Lead to Success With DevOps

Complexity can plague the success of DevOps within an organization. Complexity cannot be avoided, as DevOps is complex and will likely continue to be. However, the key to avoiding failure through your DevOps journey is to engage the complexity by using DevOps tenets to implement DevOps. Do not try to boil the ocean. Instead, at each leg in the journey, take inventory of where you are in terms of current goals, state, and best practices. Fine-tune your direction and build your solution using proven continuous delivery methods.

Nine Pillars of Continuous Security Best Practices

While DevOps offers immense value for software deployment, the adherence to best practices is essential to reduce risk and assure security. Each organization is different and has different security postures.  This blog enumerates best practices for security across nine pillars of DevOps: Leadership, Collaborative Culture, Design for DevOps, Continuous Integration, Continuous Testing, Continuous Monitoring, Elastic Infrastructure, Continuous Delivery/Deployment and Continuous Security. Examples of best practices for each pillar are listed. These practices can be used to assess an organization’s maturity within the journey to Continuous Security, often referred to as DevSecOps.

Go Big or Go Home: Total DevOps Guarantees Results

While DevOps implemented using the Total DevOps approach provides a strong foundation for long-term enterprise business improvements, it is important to understand DevOps is not an island. Enterprises implementing DevOps should be aware that DevOps interoperates with other IT systems and practices. Enterprises are well-advised to choose tool-agnostic IT partners that can provide solutions that best suit the needs of each unique enterprise and can integrate and evolve DevOps together with all their IT systems.

Nine Pillars of Containers Best Practices

While it is true you can easily “containerize” nearly any software quite quickly, this alone will not realize the benefits of an effective container deployment. Those who are serious about containers will do well to learn from others. In this article we list nine pillars of best practices for containers. While is it clear that containers offer immense value for software deployment, adhering to best practices is essential to realize their value.

Dev vs. Ops Needs for Large-Scale Version Control Systems

Distributed version control systems (DVCS) offer very fast, lightweight and local software change control capabilities that support many parallel code branches across large project code bases. These are compelling benefits for individual developers and development teams. At their heart, DVCS accomplish this by tracking software changes as a series of file system snapshots in local repositories instead of via management of individual file changes in a central database. The DVCS approach is ideal for individuals and small agile teams because it puts control directly in their hands without the need to transact all file changes.

Unnatural DevOps Delivers Supernatural Results

While DevOps is not natural, a supernatural result is achievable with the right cultural transformation supported by good tools that drive collaboration and automated flow between people and tools in the application delivery workflow. Implementing DevOps properly is challenging. DevOps depends on collaboration; smooth process flow from conception through deployment; and feedback between people, processes and technologies. It’s more natural for people and departments to hoard information and centralize control—traits that are contrary to DevOps best practices. 

Design for DevOps – Best Practices

In every case, a designer faces tough challenges and is expected to balance conflicting goals. Designers are expected to rapidly drive down the work backlog, yet produce quality products that avoid costly rejections and rollbacks. In addition, there is pressure to increase the percentage of effort spent on creative content over corrective content and do so with limited time and resources. The following best practices improve the design experience and products of design in a way that is streamlined for the DevOps pipeline.

The Harvard Innovation Lab

Made in Boston @

The Harvard Innovation Lab

350

Matching Providers

Matching providers 2
comments powered by Disqus.