Our Agile series continues with the beginners guide into DevOps world: when Agile meets the Operation

In the ever-changing world of IT, it is sometimes difficult to define certain terms, just like DevOps, and the experts themselves argue on what the precise definitions should be. But they agree on one important thing: If we have to pin point the two revolutionary things that happened to the world of modern IT, they are without a doubt, mobile technologies and the agile development[1].

First things first: the definition. The word DevOps is a linguistic blend of development and operations,referring to a specific methodology of software development. It is based on communication, collaboration and integration between software developers and IT operations personnel: a way of organizing a team work.

Let’s take a closer look at this methodology and discover why companies that use DevOps are more agile, more reliable and more successful.

Inside the DevOps World

DevOps team? DevOps toolchains!

As we mentioned before, DevOps is a methodology, or even better, a philosophy emerged from a close encounter between Agile approach and Operation. But is there such thing as DevOps team? The original concept was born as a solution for a frequent problem that developers, operations and business managers encountered during their co-working: in two separate stages, developers create code and operations run it. This approach often resulted in numerous issues, bugs or even failures, in other words, this model impedes business progress[2].

Furthermore, these two types of professionals have quite different mindsets: developers are often very agile, flexible and fast, “change” is their middle name, while the ops are the “enemies of the change”, as their main duty is to keep stability and reliability of the project. So how could these two different mindsets reconcile? As recently explained Ben Rossi, from information-age.com,

The mismatch between the attitudes of developers and operations creates what is known as the wall of confusion. The aim of DevOps is to break this wall down.

Indeed, DevOps is that bridge that connects developers and operations, allowing them to communicate, share information, knowledge and tools. It also takes advantage of agile methodology in order to break down complex processes into clusters and microservices. But above all, DevOps is about learning about each other’s workflows and tools, and actively participate during the entire lifecycle of the project. It’s not a team, nor a person, it’s a toolchain that empowers both sides with shared responsibility for delivering software that answers business needs and goals[3].

Corporate side: DevOps practices and organizational performance

The recent report by PuppetLabs, 2014 State of DevOps, give a precious look into the DevOps adoption and its results within the IT organization. The report shows the significant impact that DevOps practices have on the profitability and productivity of a company, as summed up in these main conclusions:

  • Companies with high-performing IT organizations are twice as likely to exceed their profitability, market share and productivity goals.
  • IT performance improves with DevOps maturity, and strongly correlates with well-known DevOps practices.
  • Culture matters. The cultural practices of DevOps are predictive of organizational performance.
  • Job satisfaction is the No. 1 predictor of performance against organizational goals.


Neomobile embraces DevOps practices

As one of the fastest growing digital companies globally, Neomobile’s Tech team is the core of all business projects. Our mobile monetization platform, based on with carrier billing, has direct integration with mobile operators worldwide, focused on last generation API. In order to make it function perfectly the tech team is embracing all the methodologies that help operational effectiveness, including DevOps.


If you share the same passion for technology, than Neomobile tech team is the right place for you!

Check out the latest job positions – Work with us!


1] http://www.zdnet.com/the-secret-of-devops-success-its-not-about-the-technology-7000033000/

[2] http://puppetlabs.com/blog/devops-team-no-devops-toolchain-yes

[3] Idem.