This post is from the CollabNet VersionOne blog and has not been updated since the original publish date.
Industry Analysts Share Greatest Challenges Facing Enterprise DevOps Initiatives
With technology changing rapidly, organizations must evolve their software delivery practices continuously to stay competitive and meet customer expectations.
Businesses have new challenges to solve and strategic goals to meet each year, and DevOps has emerged to ensure that software supports their success. We noted substantial progress last year in the maturing of DevOps and the value it can deliver to organizations of all types.
In 2016, we saw DevOps evolve significantly and transform many of the world’s most successful organizations.
DevOps is no longer the specialty of “unicorns” or companies like Netflix and Amazon. DevOps offers opportunity for everyone, and during the past few years we’ve noticed a rapid uptick in the number of customers wanting to use CollabNet not only for Agile initiatives, but for DevOps as well—all to create better quality products faster than the competition.
Now in 2017 we are facing a turning point. The number of point tools available for various stages in the DevOps lifecycle is astounding, and the need for platforms to reconcile these tools is more evident. Also, many believe the DevOps movement and its concepts will increasingly become embedded as industry best practices. Others have predicted that great consolidation will occur in the market this year. Again, the difference one year can make is enormous.
This is the second post in our three-part blog series in which we turn to some of the leading industry analysts to learn more about where we’ve been, where we’re headed, and how to prepare for the future.
In our first post, we asked Altaz Valani from InfoTech, Stephen Hendrick from AD Research, Edwin Yuen from ESG, and Clive Longbottom from Quorcica to tell us about the greatest ALM and DevOps successes in 2016.
Today, we share what the same analysts have to say when looking at what’s to come this year.
What are going to be the major organizational/environmental or social challenges for enterprises expanding Agile initiatives into DevOps in 2017?
“2016 was a year that was filled with incidents of security breaches. As this is now a board-level issue, we will see continued emphasis on security as it relates to secure ALM and secure DevOps.”
Also, “With many traditional companies now positioning themselves as software companies, this will place significant pressure toward greater collaboration as traditional silos continue to break down. We will see more openness and collaboration across teams enabled through ALM tools. These ALM tools will continue to mature and provide opportunities for pipeline optimization from the portfolio level down to the project and task level.”
- Altaz Valani, Senior Research Director, Application Development Practice at InfoTech Research Group
“Cultural momentum and resistance to change are the biggest challenges to DevOps in 2017. This has been the biggest challenge to Agile since its origin. Stakeholder support, patience, and use of Agile project management and release management tools are the best way to drive higher levels of success with Agile and DevOps.”
- Stephen Hendrick, AD Research
“First, there is still that shift from conceptual to operational movement for organizations. DevOps needs to be more than Agile ‘v2,’ and organizations still need to focus on implementing rapid application development principles throughout the application development process.
“Second, as more and more companies adopt Agile and DevOps, there will need to be a balance in working with more traditional style developers into the newer development models, while still integrating those developers who are not only well versed in Agile and DevOps, but essentially require it because they have never worked otherwise. Thus, it’s not just a shift from one model to another but how to bring everyone together.”
- Edwin Yuen, Analyst at ESG
“Ensuring that the pace of change matches that demanded/needed by the business itself. IT must not lag or push – its job is to respond as required while maintaining an eye on what is happening in the technology world so that it can advise the business on what could be beneficial as soon as possible.
“Also, to maintain full process audit logs through the complete Agile/DevOps steps – and this has to include all the runtime environment as well. The likelihood of a need to demonstrate exactly what was offered to a customer at some time in the past will not be best served by a comment back from IT along the lines of ‘no idea – that would have been 300 code changes ago.’
“Also, impact of further automation leading to more straight-through processing and the further possible/probable removal of human beings from the chain – how are organizations and society going to deal with how IT removes people from their jobs?”
- Clive Longbottom, Founder and Analyst at Quocirca
Thanks for the insights Clive, Edwin, Stephen, and Altaz! Sounds like we have many exciting changes ahead of us as well as opportunities to foster collaboration, empathy, and innovation in our teams.
Cheers to a new day for DevOps, a renewed push for integration and automation, and continued success of all during the DevOps journey in 2017!