Does an Informal Approach to DevOps work Best?

The DevOps approach to an IT department’s organizational structure continues to make inroads throughout the technology industry. As companies strive to reach a continuous delivery model for both new software and code enhancements, DevOps seems like a wise choice for most. Increased competition requires businesses to embrace a variety of innovations when it comes to software development.

One recent industry study questions whether an informal approach to implementing the methodology actually works better than a more sharply defined process. Here is a closer look at what their study discovered. Perhaps the survey’s findings make sense for your team’s approach to DevOps or even Agile?

A Paradoxical DevOps Survey Finding

Hewlett Packard Enterprise’s Digital Research Team surveyed a wide range of technology enterprises on their process maturity, a concept essentially the same as the Capability Maturity Model first developed at Carnegie Mellon University’s Software Engineering Institute. John Jeremiah, a technology evangelist for HPE, wrote about the survey for TechBeacon.

The survey queried over 400 technology professionals at larger enterprises about their approach to DevOps. The ultimate goal of the study involved determining what processes led to success in implementing this new organizational structure. Finding out the maturity level of the respondents’ DevOps deployment was an important differentiator in the survey.

These four maturity levels included research/evaluation, pilot project, partial implementation, and widespread implementation. Surprisingly, the study didn’t show a correlation between the DevOps maturity level and a more efficient software delivery process. Diving deeper reveals a few answers that may help your own organization’s approach to DevOps.

Getting High Quality Code into Production Faster – with Agile

The survey noted those who took a more informal approach to DevOps – with many still in the research stage of process maturity – enjoyed faster release cycles with fewer code defects. These findings almost seem counterintuitive. Why are they able to write and test better software than those companies more experienced with DevOps?

The probable answer lies within one word: Agile. A vast majority of the survey respondents still researching and evaluating DevOps were already very experienced in Agile, especially compared to those companies higher on the process maturity level. Focusing on the strong communication and collaboration typical of an Agile shop is more important than the structures and processes found within a mature DevOps implementation.

In short, as we commented earlier in this very blog – Agile and DevOps make perfect partners. The HPE study notes that an informal approach to DevOps, focusing on a collaborative Agile culture, plays a key role in making the software development process more efficient. The study revealed those companies first exploring DevOps already used some of its typical tools and processes because of Agile. These include ChatOps, containers, automation, and more.

In fact, companies researching DevOps with the hopes of achieving continuous delivery would do well to “go Agile” before restructuring their IT organization. Reaching DevOps “maturity” by itself is no guarantee of efficient software development. As Jeremiah summarizes the study finding, “DevOps is not a destination; it’s a journey.”

Become a regular reader of the Betica Blog for additional insights on the innovative world of software development. Thanks for checking it out!

News from the World of Software Development – March 2017

Welcome to this month’s software development and QA news digest. As 2017 enters its third month, the application engineering world continues to evolve at a rapid pace. If you are interested in February’s digest, simply click on this link.

Hopefully, you are able to leverage these insights to improve or inform your organization’s software engineering process.

Software Engineering Trends going Mainstream

Earlier this month, The Next Web published a story from the software intelligence company, Raygun, looking at three software development trends essentially becoming standard practice. We covered some of these same directional shifts in our 2017 industry trends article, and it is interesting to see them widely adopted.

The growth of ChatOps to enhance communication amongst a development team is one trend Raygun noted. ChatOps even allows software engineers and QA personnel to kick off builds and automated tests from a chatbot interface, while the entire team stays in the loop. The use of bots works well for companies already embracing DevOps and a continuous deployment model.

Speaking of continuous deployment, it is another one of the trends highlighted in the Raygun article. An increasingly competitive business world places the onus on companies to build and maintain applications faster than ever before. Following a continuous delivery model allows firms to deploy new code several times a day.

The increased use of software intelligence was the third trend discussed by Raygun, which isn’t a surprise, considering the company’s main line of business. Leveraging this form of automated intelligence hastens the discovery of problems or issues before the customer.

“Software intelligence gives you the ability to automatically detect when a user’s experience was poor and how you can improve it, with full diagnostic details being provided for every individual user error, crash or performance issue,” the article mentioned. This new era of application performance monitoring is one worth watching by anyone responsible for public-facing applications.

The Principles of Agile Software Development

Late March saw the appearance of a Forbes article in our news feed detailing the daily principles of Agile software development. While this is more of an evergreen topic than “news” per se, anyone new to Agile would benefit from studying these concepts. Scott Stiner, the CEO of UM Technologies, a software firm focusing on innovative user experience (UX) design, authored the article.

Stiner highlights the fact that traditional software engineering methodologies – most notably the Waterfall – lack the iteration compatible with the modern business world. The high cost of finding defects too late in the development process isn’t a risk many organizations want to take. This, combined with the faster speed of business noted earlier, is a major reason many software shops have embraced Agile over the last decade.

Early delivery of prototypes and strong customer interaction remain a major focus of Agile. Changes to requirements are welcome; not considered to be scope creep as with older methodologies. Analyze the rest of these Agile principles to see if a change in how you write applications makes sense for your organization.

Keep coming back to the Betica Blog for additional news and information regarding the wide world of software development. As always – thanks for reading!

Improving the QA Process at an Agile Office

Companies of all sizes continue to embrace the Agile methodology with the hopes of making their software development process more efficient and subsequently more productive. Agile emphasizes collaboration and communication and it is able to react to changes better than older methodologies, like the Waterfall. It is a perfect match for today’s fast-paced, competitive business world.

A faster software engineering process, however, doesn’t mean companies should forego testing and quality assurance. Unfortunately, it seems businesses are struggling with software QA within an Agile framework, according to a recent survey of development shops. Let’s take a closer look at the study’s findings with the hopes of improving the QA role at Agile shops.

Testing Tool Provider, Zephyr, looks at QA in the Business World

Zephyr, a company making applications to support software testing, annually releases a study focused the QA role within the business community. Called “How the World Tests,” it is available as a free download from their website. Managers in the software development and QA role need to check out the full study with its findings and predictions for the coming year.

Hamesh Chawla, vice president of engineering at Zephyr, commented on the purpose of their study. “‘How the World Tests’ allows the entire testing community to examine our progress over the last year. IT teams want to speed up deployment of new software to meet demand. Companies should increase employee education investments in order to fine-tune the most efficient automated tests that work for any software they develop,” said Chawla.

Quality assurance remains a vital part of the SDLC no matter the choice of methodology. Even so, we are going to focus on one area within the survey — the difficulties Agile shops are experiencing with QA on software projects. SD Times also covered this topic in a recent article.

The Major Problems of Software Testing and Agile

The Zephyr study noted three major problems development teams were experiencing when it comes to testing with Agile. They are the lack of automation tools, constantly changing requirements, and not enough time for thorough testing. Companies understand automation is important in helping QA keep up with the rapid pace of an Agile project, but only 45 percent of the survey respondents felt their organization had the competency to employ automated testing.

Chawla feels companies need to invest in automation tools and the training to leverage them properly within the Agile process. Of course, he works at a testing tool company, but that fact doesn’t lessen the impact of his statement. Software development teams also use other recent innovations, like containers and virtualization, to make the overall process faster.

Businesses also need to invest more dollars in employee development to ensure a better understanding of Agile and everyone’s role within the framework. Involving QA personnel at every step of the SDLC is also important – a traditional complaint of software testers for decades. The reengineering of testing processes to better fit within the Agile structure is another key point of improvement from the survey.

Ultimately, organizations need to understand that Agile doesn’t just mean “faster.” A well-considered process that properly includes the QA role is a requirement to ensure successful product delivery.

When you need additional insights on the world of software development, you know where to turn: The Betica Blog. As always, thanks for reading!