What is the State of Agile adoption today?

By Linky van der Merwe

The 14th annual State of Agile report has been published by Digital.ai, formerly known as CollabNet VersionOne.  The report documents the experiences of more than 1,100 IT and business professionals across a range of industries and roles worldwide. With 40,000 participants contributing over 14 years, the State of Agile report is the longest running and most widely cited Agile survey in the world and provides global enterprises with comprehensive data to benchmark and guide their Agile practices.

Key findings

Notable findings from the 14th annual State of Agile report, completed in December 2019, include:

  • 60 percent of respondents have increased speed to market
  • Risk and compliance continue to trend upward, as the value of identifying and measuring technical risk prior to deployment increased by 54 percent and the importance of automated audit compliance and governance across control points increased by 10 percent over last year.
  • A significant shift in Agile techniques occurred, as product road-mapping increased nine percent while release planning decreased 11 percent. Drivers for this change may include a general increase in continuous integration/continuous deployment and better-defined program increment planning.
  • The Scaled Agile Framework (SAFe®) continues to be the most popular scaling method cited by respondents, increasing 5 percent over last year and outpacing the number two choice, Scrum@Scale, by 19 percent.
  • 55 percent are planning to implement Value Stream Management (VSM) a combination of people, process, and technology that maps, optimizes, visualizes, measures, and governs business value flow from idea through development and into production. 
14th annual State of Agile Report

Interesting demographic analysis is showing that companies with more than 20,000 people were more likely to be practicing Agile for at least five years. While companies with less than 1,000 people continue to mature quickly and are increasingly embracing a broader view of business agility by applying Agile principles to areas of the business outside development, IT, and operations.

How COVID-19 affected Agile adoption

In mid-May 2020, Digital.ai conducted a brief supplemental survey of respondents to learn how the COVID-19 pandemic has affected their Agile adoption. The findings reveal:

  • 55% say their company plans to increase the use of Agile in the next 12-14 months. This is an increase of 13 percent over the original survey completed just five months ago.
  • 43% of organizations say their momentum for Agile adoption has increased over the past 90 days, with 15 percent saying it has increased significantly.
  • 33% say they increased or expanded Agile adoption in the last 90 days to help manage distributed teams.

To find out what the survey reveals about Agile methods and practices, Agile benefits, scaling Agile, Agile Project Management tools, success and metrics as well as Devops and Value Stream Management, please download the 14thState of Agile Report here.

Virtual Project Consulting

Please subscribe to Virtual Project Consulting not to miss future articles, tips and success stories!

The Challenges Faced by DevOps Today

By Ashley Lipman

With the rise in Agile adoption, the need for a streamlined process around the software development life cycle, through development and testing to production is paramount.  The capabilities that make up DevOps are provided by people, defined practices and automation tools, according to the DevOps for Dummies. (Source: DevOps for Dummies by Sanjeev Sharma, Bernie Coyne)

DevOps Reference Architecture
Source: DevOps for Dummies

While shifting to a DevOps approach is ideal for agile team to deliver value to customer faster, it can cause problems within a project development team. In fact, it’s been known to cause a few problems during the production implementation.

Here are some of the challenges faced by DevOps teams today.

Clearly Defined Roles and Permissions

Not having clearly defined roles and permissions for a DevOps teams can cause many problems.

When it comes down to it, developers and operations teams have different roles that sometimes overlap. It’s important to address these overlaps so that everyone knows not only what they’re responsible for, but what they aren’t permitted to do. For example, developers shouldn’t be able to access the same logs as sysadmins (source: https://papertrailapp.com/log-management).

Roles will allow DevOps teams to utilize applications that will encourage access rights management that promote effectiveness and compliance.

Choosing the Right Projects

While starting to implement DevOps, it’s important to take a gradual, strategic approach. Rather than trying to transfer all new projects to the new management system, choosing a few projects and analyzing the benefits and challenges is key. From there, refining the implementation process and expanding will help make DevOps successful.

That being said, not all projects are meant for a DevOps approach. Many businesses are faced with challenges when it comes to change management. While one of those challenges is letting go of the old way, another is often identifying when the old approach works better for a specific project.

Attention to Detail and Testing

One of the main benefits of DevOps is the ability to finish projects quicker through a continuous feedback loop. However, quicker isn’t always better, especially during the early days. When aiming to move more efficiently, it’s critical that DevOps teams don’t neglect the testing process. Quality assurance testing to ensure that everything is bug-free is one of the most important steps in development, and the DevOps approach doesn’t always put this task in the limelight.

When releasing an app with bugs, it can cause a bad user experience. This can cause a blame game with the development and operations teams, creating a negative team dynamic that will impact future projects.

Legacy Infrastructure and Tools

DevOps challenges - legacy infrastructure

Focusing too much on the tools and not enough on the team dynamic is a unique challenge that many organizations face when switching to a DevOps culture. However, not putting enough attention into the infrastructure and tools can also be detrimental. 

Using legacy infrastructure while trying to modernize standard operating procedures can be a significant limiting factor, even if the current infrastructure has been useful for years. The businesses that have the most success with DevOps are those that switch to a micro-services approach, implementing automation and innovating their old applications. 

Of course, making these changes can be a monumental task, and can often lead to a “chicken or the egg” conundrum when trying to determine which practices versus which infrastructure should be changed first. Managing all of these changes without getting distracted by the wide array of tools meant to assist with DevOps can be time-consuming and costly.

Successful DevOps

Creating a successful DevOps culture isn’t an overnight process. It can take months of creating a culture of positive communication and cohesion between teams, and even longer to take a sustainable approach to scaling. 

However, by focusing on the team itself, having the right foundation in place, and testing rigorously, DevOps can change the face of a business for the better.

Virtual Project Consulting

Please subscribe to Virtual Project Consulting not to miss future articles, tips and success stories!