Last week we shared several interesting reports on trends in the industry and tools to use to take advantage of them. This week, Forrester issued an intriguing report on high-performing DevOps organizations, what commonalities they share and what low performing organizations have in common. Commissioned by Tricentis, you can download the report here, gratis.
The report finds the 20 most important Agile and DevOps quality metrics that separate DevOps/Agile Experts from their less advanced peers. Top of the list:
- Experts are transforming software testing into Continuous Testing by adopting five core practices, such as automating end-to-end functional testing and integrating testers into cross-functional teams.
- They are almost twice as likely to consider automating the software quality process to be a “critical business differentiator” (53% vs. 27%).
- They are significantly more likely (by 23 percentage points) to have high levels of automation for key testing and QA processes (test case design, functional test automation, test data management, etc.).
Moreover, the report finds that understanding business risk is the most important determining factor of DevOps and Agile maturity; that Experts focus primarily on contextual metrics (e.g., requirements coverage) vs. “counting” metrics (e.g., number of tests); and Experts are more likely to measure the user experience across an end-to-end transaction while others rely on application-specific or team-specific metrics.
While many CXOs and high-level decision makers vastly overestimate the maturity of their firms’ Agile and DevOps practices, according to Forrester, at Flux7 we believe it’s important to have an Enterprise DevOps Framework for adoption and ongoing success.
When it comes to facilitating DevOps process, many teams, Flux7 included, rely on Slack for communications. This past week Atlassian announced that it is setting its own communication platform, Stride, to the side in favor of a strategic partnership with Slack. Both companies said that they will focus on building better integrations with Atlassian deepening its existing integrations between Slack and Jira Cloud, Bitbucket Cloud, and Trello, as well as creating new integrations with other products.
In other news, as part of the lead up to the release of Terraform 0.12, HashiCorp are publishing a series of previews: this week they shared improvements to conditional operators and introduced conditionally omitted arguments. The news caught our attention as Terraform has supported basic conditionals for two years, but conditionals have had major known limitations. In Terraform 0.12, these limitations have been lifted and conditionals work as expected in all cases. Terraform 0.12 also introduces the null value for conditionally omitting a value.
These few bits of AWS news caught the eyes of our DevOps team:
- Amazon announced that its Elastic Load Balancing now supports redirects and fixed responses for Application Load Balancer. With this news, Application Load Balancer now supports two new actions: redirect and fixed-response. Operators can configure these actions as part of the content-based routing rules, offloading the functionality to the load balancer, thus simplifying deployments while benefiting from the scale, the availability, and the reliability of Elastic Load Balancing.
- This AWS blog post on “How to migrate your on-premises domain to AWS Managed Microsoft AD using ADMT”. In it author Danny Jenkins notes he is often asked how to easily migrate on-premises Active Directory domains to AWS -- and be free of the operational management of the AD infrastructure. In the article he explains how operators can now use the Active Directory Migration Toolkit (ADMT) along with the Password Export Service (PES) to migrate self-managed AD to AWS Directory Service for Microsoft Active Directory, also known as AWS Managed Microsoft AD. (Relatedly, we recently shared how to use Azure AD to manage user authentication to access the AWS console. You can read that blog here.)
- Our experts also enjoyed this blog on AWS Config Best Practices in which Sid Gupta shares best practices on how to use AWS Config as a tool for enabling governance across the enterprise. We are proponents of AWS Config ourselves, as it can play a central role in helping establish and ensure AWS risk and compliance efforts, keeping systems in a known, good state. For more details, you can download our AWS Compliance Tutorial, A Visual Guide to Configuring Top AWS Managed Config Rules.
DevOps Adoption Series
The Flux7 AWS consulting team continues its DevOps blog series on DevOps adoption, which started with a discussion of what motivates organizations to begin an IT modernization project. We last featured the DevOps Adoption Case Study of an enterprise media group and how it developed its AWS Cloud Migration Path. Subscribe to our DevOps blog to make sure you get the whole series.